Website review, no card needed
pepstores.com website review
Visit site (opens in a new tab)Reviewed 4 November 202641 issues · 83 checks
This review found 41 issues worth fixing on pepstores.com, 11 of them high impact, across 83 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for PEP
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
72C- #73,222 of 94,134 reviewed websitesbeats 19%
- #42,889 of 50,449 online storesbeats 12%
- #39,748 of 45,584 Shopify storesbeats 10%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 3.2 s |
| Oct 24, 2026 | 3.3 s |
| Oct 31, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 260 ms |
| May 23, 2026 | 262 ms |
| May 30, 2026 | 271 ms |
| Jun 6, 2026 | 274 ms |
| Jun 13, 2026 | 272 ms |
| Jun 20, 2026 | 254 ms |
| Jun 27, 2026 | 231 ms |
| Jul 4, 2026 | 209 ms |
| Jul 11, 2026 | 196 ms |
| Jul 18, 2026 | 196 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 199 ms |
| Aug 8, 2026 | 205 ms |
| Aug 15, 2026 | 212 ms |
| Aug 22, 2026 | 222 ms |
| Aug 29, 2026 | 234 ms |
| Sep 5, 2026 | 242 ms |
| Sep 12, 2026 | 247 ms |
| Sep 19, 2026 | 248 ms |
| Sep 26, 2026 | 243 ms |
| Oct 3, 2026 | 239 ms |
| Oct 10, 2026 | 238 ms |
| Oct 17, 2026 | 240 ms |
| Oct 24, 2026 | 249 ms |
| Oct 31, 2026 | 255 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,264 HTML elements
The page has 3,264 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 75
75/100Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Hotjar and others), adding 1.2 MB and 662 ms of main-thread time.
Google Tag Manager adds 436 ms
436 msGoogle Tag Manager costs a phone 436 ms of main-thread work and 500 KiB 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.
Reduce unused JavaScript
370 KiBAbout 370 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
300 ms · 69 KiBAbout 69 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Shopify adds 90 ms
90 msShopify costs a phone 90 ms of main-thread work and 450 KiB 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 203 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
39 KiB8 files are served with short cache lifetimes, so returning visitors download them again (39 KiB).
Legacy JavaScript
22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need.
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 19 ms
19 msYour server sent the HTML in 19 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.
Time to Interactive: 13.3 s
13.3 sThe page becomes fully interactive after 13.3 s. Good is under 3.8 s.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cellular”.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 259 ms
259 msReal visitors wait 259 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.21
0.21For real visitors the layout shifts by 0.21 (75th percentile). Good is under 0.1.
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 310 ms
310 msScripts block taps and scrolling for 310 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 260 ms to 255 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.9 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user TTFB: 648 ms
648 msReal visitors wait 648 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.061
0.061The layout barely moves while loading (CLS 0.061, good is under 0.1).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 4.6 MB in 397 requests
4.6 MBYour homepage downloads 4.6 MB in 397 requests on a phone: other files 2.4 MB (240), scripts 1.0 MB (65) and images 876 KiB (68). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Homepage_Banner_-_Mobile.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.3 g of CO₂ per visit
1.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.30 g of CO₂e: 156.1 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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (27 elements)
Alternative text of images should not be repeated as text: 27 elements on the page fail this check, rated minor by axe-core.
7 form fields without a label
7 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 71 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 4 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Clothing, Footwear, Homeware | Mobile | Financial Services – PEP Store”.
5 links crawlers can't follow
5 links have no real href, so search engines can't follow them.
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.
One H1 headline
Your <h1> is empty.
774 internal links, 8 external
The homepage links to 774 pages on pepstores.com and 8 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.pepstores.com/.
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://www.pepstores.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,534 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.pepstores.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.pepstores.com/collections/paxi-bags, which answers with an error. Visitors hit a dead end and search engines drop it.
7 pages without a title
https://www.pepstores.com/collections/shop-womenswear-online, https://www.pepstores.com/collections/shop-menswear-online, https://www.pepstores.com/collections/shop-baby-products-online, https://www.pepstores.com/collections/shop-kids-products-online, https://www.pepstores.com/collections/shop-tweens-products-online and https://www.pepstores.com/collections/shop-beauty-products-online and 1 other have no <title>, so Google invents the link text in results.
6 pages without a meta description
https://www.pepstores.com/pages/find-a-store, https://www.pepstores.com/pages/shop-online, https://www.pepstores.com/collections/shop-womenswear-online, https://www.pepstores.com/collections/shop-menswear-online, https://www.pepstores.com/collections/shop-cellular-online and https://www.pepstores.com/pages/women have no meta description, so Google writes the search snippet from whatever text it finds.
7 links to non-canonical URLs
Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://www.pepstores.com/collections/available-online, whose canonical is https://www.pepstores.com/pages/home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
14 pages without an H1
https://www.pepstores.com/pages/find-a-store, https://www.pepstores.com/pages/shop-online, https://www.pepstores.com/collections/available-online, https://www.pepstores.com/collections/shop-womenswear-online, https://www.pepstores.com/collections/shop-menswear-online and https://www.pepstores.com/collections/shop-baby-products-online and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.pepstores.com/collections/back-to-school and https://www.pepstores.com/collections/shop-cellular-online have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 198 found) and read each the way a search engine does.
2 checks passed
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.
Best practices
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.
Requests the notification permission on page load
Requests the notification permission on page load.
2 checks passed
Tap targets are thumb-sized
107 of 108 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.
Only about 234 words
The homepage has only about 234 words of visible text; thin pages give Google and first-time buyers little to go on.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Cellular” and “Shop Kids younger boys swimwear”.
36 calls to action
The homepage has 36 calls to action, for example “Shop Online”, “Shop School Online” and “Shop Home Online”.
8 short forms
8 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 3 mores (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.
18 cookies set on arrival
18Opening the homepage sets 18 cookies (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.
32 other companies contacted
Loading the homepage contacts 32 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 pepstores.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Founded
- 1965
- Headquarters
- Parow
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on pepstores.com, including 18 speed issues, 5 SEO issues and 3 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.