Website review, no card needed
theroadrat.com website review
Visit site (opens in a new tab)Reviewed 16 November 202637 issues · 78 checks
This review found 37 issues worth fixing on theroadrat.com, 8 of them high impact, across 78 checks. The most urgent: page weight: 37.5 MB in 102 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
82B- #32,578 of 114,941 reviewed websitesbeats 66%
- #22,037 of 66,342 online storesbeats 60%
- #21,331 of 60,683 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.7 s |
| Nov 14, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 98 ms |
| Jun 6, 2026 | 98 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 98 ms |
| Jun 27, 2026 | 99 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 110 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 107 ms |
| Aug 8, 2026 | 104 ms |
| Aug 15, 2026 | 110 ms |
| Aug 22, 2026 | 120 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 131 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 131 ms |
| Oct 3, 2026 | 136 ms |
| Oct 10, 2026 | 141 ms |
| Oct 17, 2026 | 142 ms |
| Oct 24, 2026 | 142 ms |
| Oct 31, 2026 | 137 ms |
| Nov 7, 2026 | 134 ms |
| Nov 14, 2026 | 131 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
1.4 MB15 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and omnisnippet1.com and others), adding 1.3 MB and 511 ms of main-thread time.
Reduce unused JavaScript
150 ms · 452 KiBAbout 452 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
296 KiB6 files are served with short cache lifetimes, so returning visitors download them again (296 KiB).
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 13 ms
13 msShopify costs a phone 13 ms of main-thread work and 551 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.
Legacy JavaScript
250 ms · 40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 10 KiBAbout 10 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.
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.
1 checks passed
Server response: 134 ms
134 msYour server sent the HTML in 134 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: 14.6 s
14.6 sThe page becomes fully interactive after 14.6 s. Good is under 3.8 s.
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Road Rat Edition 24 ‘The Art of Engineering’ Discover m…”.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 35% slower for real visitors
+35%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 98 ms to 131 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 810 ms
810 msReal visitors wait 810 ms for your server to start answering (75th percentile). Good is under 800 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 119 ms
119 msReal visitors wait 119 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 137 ms
137 msScripts block the page for only 137 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 37.5 MB in 102 requests
37.5 MBYour homepage downloads 37.5 MB in 102 requests on a phone: media 33.5 MB (3), images 2.1 MB (31) and scripts 1.3 MB (32). Under 2 MB keeps phones on slow connections fast.
5 images below the first screen load straight away
5 images further down the page (528 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images far larger than shown
211 KiB4 images are downloaded at several times the size a phone draws them, for example Issue-23-flat-cover_810x.jpg at 810 px wide, shown at 204 px. Resized copies would save about 211 KiB.
1 image in older formats
1 image (197 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 10.6 g of CO₂ per visit
10.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 10.62 g of CO₂e: 1274.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (268 characters)
Your meta description is 268 characters; Google truncates after about 160, so the end of your pitch is cut.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
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.
32 internal links, 3 external
The homepage links to 32 pages on theroadrat.com and 3 external pages.
4 checks passed
Title: 44 characters
Your title is a healthy 44 characters: “The Road Rat Magazine | Car Culture in Print”.
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://theroadrat.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://theroadrat.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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 (303 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages share 2 titles
/, https://theroadrat.com/shop, https://theroadrat.com/shop/subscription and https://theroadrat.com/newsletter all use the title “The Road Rat Magazine | Car Culture in Print”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages share a meta description
https://theroadrat.com/shop/magazine, https://theroadrat.com/shop/magazine/edition-24 and https://theroadrat.com/magazine use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://theroadrat.com/shop, https://theroadrat.com/about, https://theroadrat.com/shop/subscription, https://theroadrat.com/shop/stockists and https://theroadrat.com/newsletter have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://theroadrat.com/archive and https://theroadrat.com/shop/slipcases 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.
1 page slow to respond
https://theroadrat.com/magazine took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
6 small tap targets
6 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 284 words of copy
The homepage carries about 284 words of visible text.
2 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Shop”, “Subscribe” and “Join the newsletter”.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok 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, 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.
15 other companies contacted
Loading the homepage contacts 15 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 theroadrat.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Next.js
- E-commerce
- Shopify
- Hosting
- DigitalOcean
Company
- Headquarters
- San Francisco
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 theroadrat.com, including 15 speed issues, 6 SEO issues and 4 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.