Website review, no card needed
skroptoppie.com website review
Visit site (opens in a new tab)Reviewed 21 November 202628 issues · 82 checks
This review found 28 issues worth fixing on skroptoppie.com, 11 of them high impact, across 82 checks. The most urgent: render-blocking requests. 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
77C- #69,607 of 125,621 reviewed websitesbeats 39%
- #44,808 of 70,221 online storesbeats 31%
- #1,113 of 2,950 WooCommerce storesbeats 57%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.1 s |
| Jun 13, 2026 | 4.1 s |
| Jun 27, 2026 | 4.3 s |
| Jul 11, 2026 | 4.1 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 4.0 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.5 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 5.1 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.8 s |
| Oct 10, 2026 | 4.2 s |
| Oct 17, 2026 | 3.7 s |
| Oct 24, 2026 | 3.4 s |
| Oct 31, 2026 | 3.1 s |
| Nov 7, 2026 | 3.0 s |
| Nov 14, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 85 ms |
| Jun 13, 2026 | 92 ms |
| Jun 27, 2026 | 89 ms |
| Jul 11, 2026 | 89 ms |
| Jul 18, 2026 | 88 ms |
| Jul 25, 2026 | 87 ms |
| Aug 1, 2026 | 87 ms |
| Aug 8, 2026 | 87 ms |
| Aug 15, 2026 | 87 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 87 ms |
| Sep 5, 2026 | 86 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 87 ms |
| Sep 26, 2026 | 91 ms |
| Oct 3, 2026 | 92 ms |
| Oct 10, 2026 | 85 ms |
| Oct 17, 2026 | 86 ms |
| Oct 24, 2026 | 80 ms |
| Oct 31, 2026 | 78 ms |
| Nov 7, 2026 | 78 ms |
| Nov 14, 2026 | 73 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.5 s
1.1 s
1.6 s
2.2 s
2.7 s
3.2 s
3.8 s
4.3 s
Speed
Render-blocking requests
1.9 s36 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
600 ms · 238 KiB17 files are served with short cache lifetimes, so returning visitors download them again (238 KiB).
Reduce unused JavaScript
600 ms · 170 KiBAbout 170 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Unpkg and others), adding 612 KiB and 444 ms of main-thread time.
Reduce unused CSS
150 ms · 45 KiBAbout 45 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.
Legacy JavaScript
150 ms · 33 KiBPolyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 151 ms. During a long task the page ignores taps.
Improve image delivery
91 KiB2 images could be 91 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 648 ms of it running JavaScript. That is comfortably low.
Server response: 33 ms
33 msYour server sent the HTML in 33 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.
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.5 s
2.5 sReal visitors wait 2.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (3.2 s).
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Time to Interactive: 6.9 s
6.9 sThe page becomes fully interactive after 6.9 s. Good is under 3.8 s.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user INP: 74 ms
74 msReal visitors wait 74 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 85 ms to 73 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 112 ms
112 msScripts block the page for only 112 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 4.1 MB in 149 requests
4.1 MBYour homepage downloads 4.1 MB in 149 requests on a phone: images 3.2 MB (64), scripts 725 KiB (45) and stylesheets 105 KiB (33). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (59 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.16 g of CO₂e: 139.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
46 images without alt text
46 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.
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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4, h3 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
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. 1 more need a person to judge. 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 (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Skroptoppie Scrubs – Stylish Medical Scrubs, Apparel & Accessories”.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No robots.txt
There is no robots.txt at skroptoppie.com/robots.txt, the first file search crawlers ask for.
95 internal links, 14 external
The homepage links to 95 pages on skroptoppie.com and 14 external pages.
4 checks passed
One H1 headline
Your main headline reads: “SkropToppie & Core Scrubs”.
Structured data in place
Structured data found: ClothingStore, Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://skroptoppie.com/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (911 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://skroptoppie.com/llms.txt (120 KiB, 312 links), a plain-text guide to the site for AI tools.
Other pages
8 linked pages are broken
Your homepage links to https://skroptoppie.com/shop/jewellery/gold, https://skroptoppie.com/shop/jewellery/silver, https://skroptoppie.com/shop/accessories, https://skroptoppie.com/product/badge-reels, https://skroptoppie.com/shop/pins and https://skroptoppie.com/shop/shoe-charms and 2 others, which answer with an error. Visitors hit a dead end and search engines drop them.
6 pages without a meta description
https://skroptoppie.com/shop/patterned-scrub-tops, https://skroptoppie.com/product/stride-jacket, https://skroptoppie.com/shop/normal-scrub-caps, https://skroptoppie.com/shop/big-scrub-caps, https://skroptoppie.com/shop/buffs and https://skroptoppie.com/shop/jewellery have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages slow to respond
https://skroptoppie.com/shop/patterned-scrub-tops, https://skroptoppie.com/product/stride-jacket, https://skroptoppie.com/shop/normal-scrub-caps, https://skroptoppie.com/shop/big-scrub-caps and https://skroptoppie.com/shop/buffs took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 52 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 6 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
2 checks passed
Tap targets are thumb-sized
6 of 7 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Only about 219 words
The homepage has only about 219 words of visible text; thin pages give Google and first-time buyers little to go on.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
7 checks passed
20 calls to action
The homepage has 20 calls to action, for example “Shop”, “Shop Submenu” and “Contact”.
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 27 testimonial or review blocks and 42 trust badges.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
14 other companies contacted
Loading the homepage contacts 14 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 skroptoppie.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Hosting
- Hostinger
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on skroptoppie.com, including 12 speed issues, 4 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.