Website review, no card needed
powerbylachlan.com website review
Visit site (opens in a new tab)Reviewed 10 November 202637 issues · 86 checks
This review found 37 issues worth fixing on powerbylachlan.com, 16 of them high impact, across 86 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74C- #76,697 of 108,868 reviewed websitesbeats 26%
- #48,393 of 61,767 online storesbeats 18%
- #45,577 of 56,365 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 146 ms |
| May 30, 2026 | 144 ms |
| Jun 6, 2026 | 140 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 138 ms |
| Jun 27, 2026 | 137 ms |
| Jul 4, 2026 | 136 ms |
| Jul 11, 2026 | 130 ms |
| Jul 18, 2026 | 131 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 149 ms |
| Aug 15, 2026 | 146 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 144 ms |
| Sep 12, 2026 | 147 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 156 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 160 ms |
| Oct 17, 2026 | 159 ms |
| Oct 24, 2026 | 155 ms |
| Oct 31, 2026 | 153 ms |
| Nov 7, 2026 | 158 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Improve image delivery
13.3 s · 5.1 MB38 images could be 5.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 13.3 s faster on a phone.
Main-thread work: 8.6 s
A phone's processor spends 8.6 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,713 HTML elements
The page has 4,713 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
7 third-party services on the page
7 third-party services load with your homepage (Shopify, Klaviyo and Facebook and others), adding 1.9 MB and 431 ms of main-thread time.
Reduce unused JavaScript
317 KiBAbout 317 KiB of JavaScript is downloaded but never used on this page.
Shopify adds 137 ms
137 msShopify costs a phone 137 ms of main-thread work and 1.6 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 275 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 57 KiBAbout 57 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
126 KiB8 files are served with short cache lifetimes, so returning visitors download them again (126 KiB).
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 21.2 s
21.2 sYour largest element takes 21.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 22.9 s
22.9 sThe page becomes fully interactive after 22.9 s. Good is under 3.8 s.
Speed Index: 8.6 s
8.6 sVisually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 600 ms
600 msScripts block taps and scrolling for 600 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 146 ms to 158 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 153 ms
153 msReal visitors wait 153 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 725 ms
725 msReal visitors wait 725 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.01
0.01The layout barely moves while loading (CLS 0.01, good is under 0.1).
Images and page weight
Page weight: 9.5 MB in 487 requests
9.5 MBYour homepage downloads 9.5 MB in 487 requests on a phone: images 7.5 MB (298), scripts 886 KiB (82) and other files 764 KiB (94). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
38 KiB1 image is downloaded at several times the size a phone draws it, for example pwr_supply-2026_pwr_tracksuit-img-shopify_0003_20260923-pwr_ at 349 px wide, shown at 66 px. Resized copies would save about 38 KiB.
About 2.7 g of CO₂ per visit
2.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.69 g of CO₂e: 322.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Scrollable region must have keyboard access (13 elements)
Scrollable region must have keyboard access: 13 elements on the page fail this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
21 images without alt text
21 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
25 links without text
25 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (10 characters)
Your title is only 10 characters: “PWR Supply”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (44 characters)
Your meta description is only 44 characters: “Where Creators and Competitors come to play.”. 70 to 160 characters is enough to sell the click.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
132 internal links, 7 external
The homepage links to 132 pages on powerbylachlan.com and 7 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://pwr.supply/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://pwr.supply/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,174 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://pwr.supply/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages share a meta description
https://pwr.supply/pages/newsletter, https://pwr.supply/blogs/discover, https://pwr.supply/collections/active, https://pwr.supply/pages/about, https://pwr.supply/pages/plus and https://pwr.supply/pages/support and 8 others use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://pwr.supply/pages/newsletter, https://pwr.supply/blogs/discover, https://pwr.supply/collections/active, https://pwr.supply/pages/about, https://pwr.supply/pages/plus and https://pwr.supply/pages/support and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
24 of 27 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 305 words of copy
The homepage carries about 305 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
15 calls to action
The homepage has 15 calls to action, for example “Shop”, “Shop Show menu” and “Track your order”.
7 short forms
7 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Meta Pixel.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Klaviyo, Meta Pixel and TikTok Pixel and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
17 other companies contacted
Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at powerbylachlan.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Restock Alert Engine · Yotpo Product Reviews · Bis · Forms · Boo Eu Withdrawal Button · klaviyo.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on powerbylachlan.com, including 16 speed issues, 4 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.