Website review, no card needed
routeone.co.uk website review
Visit site (opens in a new tab)Reviewed 6 November 202635 issues · 89 checks
This review found 35 issues worth fixing on routeone.co.uk, 13 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
84B- #22,159 of 124,357 reviewed websitesbeats 77%
- #14,255 of 69,863 online storesbeats 74%
- #13,823 of 63,534 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 129 ms |
| May 23, 2026 | 130 ms |
| May 30, 2026 | 133 ms |
| Jun 6, 2026 | 137 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 139 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 148 ms |
| Jul 18, 2026 | 149 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 146 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 147 ms |
| Aug 22, 2026 | 150 ms |
| Aug 29, 2026 | 149 ms |
| Sep 5, 2026 | 146 ms |
| Sep 12, 2026 | 142 ms |
| Sep 19, 2026 | 138 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 137 ms |
| Oct 10, 2026 | 135 ms |
| Oct 17, 2026 | 131 ms |
| Oct 24, 2026 | 129 ms |
| Oct 31, 2026 | 129 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.8 s
1.6 s
2.4 s
3.2 s
4.0 s
4.8 s
5.5 s
6.3 s
Speed
Reduce unused JavaScript
1.2 s · 733 KiBAbout 733 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
4,012 HTML elements
The page has 4,012 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Klevu Search, Klaviyo and minmaxify.com and others), adding 1.5 MB and 707 ms of main-thread time.
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Minify JavaScript
450 ms · 92 KiB92 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
150 ms · 282 KiB19 files are served with short cache lifetimes, so returning visitors download them again (282 KiB).
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Klaviyo adds 204 ms
204 msKlaviyo costs a phone 204 ms of main-thread work and 621 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 CSS
150 ms · 137 KiBAbout 137 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.
Improve image delivery
150 ms · 69 KiB3 images could be 69 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 161 ms. During a long task the page ignores taps.
Duplicated JavaScript
28 KiB28 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need.
Minify CSS
10 KiB10 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.
1 checks passed
Server response: 94 ms
94 msYour server sent the HTML in 94 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 18.4 s
18.4 sThe page becomes fully interactive after 18.4 s. Good is under 3.8 s.
Largest Contentful Paint: 6.5 s
6.5 sYour largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 129 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 138 ms
138 msReal visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 342 ms
342 msReal visitors wait 342 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 168 ms
168 msScripts block the page for only 168 ms while loading. Good is under 200 ms.
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.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 4.4 MB in 316 requests
4.4 MBYour homepage downloads 4.4 MB in 316 requests on a phone: scripts 2.0 MB (131), images 1.2 MB (52) and other files 796 KiB (113). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.24 g of CO₂e: 148.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
12 buttons without a name
12 buttons have no accessible name, so screen readers announce just “button”.
Required ARIA attributes must be provided (1 element)
Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
11 images without alt text
11 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.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails 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.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 9 failed. 3 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.
Structured data has 2 problems
Structured data found (BreadcrumbList, Organization and WebSite) but with 2 problems, for example “Organization: missing name”.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
379 internal links, 3 external
The homepage links to 379 pages on routeone.co.uk and 3 external pages.
6 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Shop skate shoes, streetwear & skateboards at Route One. Designed for skaters & made to last. The UK's #1 skate shop si…”.
Title: 59 characters
Your title is a healthy 59 characters: “Route One Skate Shop | Skate Shoes, Streetwear & Skateboard”.
Canonical URL set
The canonical URL is https://www.routeone.co.uk/.
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.routeone.co.uk/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, sameAs (social profiles), 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,446 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.routeone.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://www.routeone.co.uk/collections/nike-sb-heritage-vulc and https://www.routeone.co.uk/collections/new-balance-numeric-933 have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.routeone.co.uk/pages/delivery, https://www.routeone.co.uk/collections/latest, https://www.routeone.co.uk/collections/skate-shoes, https://www.routeone.co.uk/collections/nike-sb-dunk, https://www.routeone.co.uk/collections/nike-sb-heritage-vulc and https://www.routeone.co.uk/collections/nike-sb-force-58 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.routeone.co.uk/collections/new-balance-numeric-440, https://www.routeone.co.uk/collections/adidas-busenitz and https://www.routeone.co.uk/collections/vans-half-cab-skate-shoes took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 184 found) and read each the way a search engine does.
5 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.
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
1 broken image
1 image failed to load on a phone, for example https://firebasestorage.googleapis.com/v0/b/venn-prod-70222.appspot.com/o/static%2Fappstore-icon.png?alt=media&token=0b243992-925f-4c09-a068-183a30501851.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
64 of 74 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 16-field form
Your longest form asks for 16 fields (0 required). Every extra field lowers completion.
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.
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.
About 890 words of copy
The homepage carries about 890 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Butter Goods x Umbro SHOP BUTTER GOODS” and “SHOP BUTTER GOODS”.
40 calls to action
The homepage has 40 calls to action, for example “Shop Now”, “Find Your Local Skate Shop” and “Shop By Brand”.
Social proof on the page
Social proof on the homepage: a star rating and 11 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta 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.
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.
45 other companies contacted
Loading the homepage contacts 45 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 routeone.co.uk, 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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Venn Apps · Minmaxify Order Limits · Klaviyo Email Marketing Sms · Instafeed · Multifeeds · Selleasy · Event Promotion Bar · cloudfront.net · hextom.com · esc-apps-cdn.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
- Framework
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Bristol
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on routeone.co.uk, including 13 speed issues, 3 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.