Website review, no card needed
clarkrailworks.com website review
Visit site (opens in a new tab)Reviewed 10 November 202638 issues · 86 checks
This review found 38 issues worth fixing on clarkrailworks.com, 9 of them high impact, across 86 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
79C- #52,361 of 115,630 reviewed websitesbeats 49%
- #35,021 of 66,528 online storesbeats 41%
- #33,631 of 60,792 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 107 ms |
| May 30, 2026 | 109 ms |
| Jun 6, 2026 | 111 ms |
| Jun 13, 2026 | 110 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 113 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 110 ms |
| Jul 25, 2026 | 111 ms |
| Aug 1, 2026 | 111 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 115 ms |
| Aug 22, 2026 | 114 ms |
| Aug 29, 2026 | 114 ms |
| Sep 5, 2026 | 116 ms |
| Sep 12, 2026 | 114 ms |
| Sep 19, 2026 | 117 ms |
| Sep 26, 2026 | 117 ms |
| Oct 3, 2026 | 115 ms |
| Oct 10, 2026 | 114 ms |
| Oct 17, 2026 | 114 ms |
| Oct 24, 2026 | 115 ms |
| Oct 31, 2026 | 117 ms |
| Nov 7, 2026 | 118 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.6 s
1.2 s
1.7 s
2.3 s
2.9 s
3.5 s
4.0 s
4.6 s
Speed
Reduce unused JavaScript
1.6 s · 487 KiBAbout 487 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
3,346 HTML elements
The page has 3,346 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 57
57/100Your mobile performance score is 57. 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 (Google CDN, Shopify and Klarna and others), adding 1.3 MB and 575 ms of main-thread time.
Use efficient cache lifetimes
450 ms · 119 KiB26 files are served with short cache lifetimes, so returning visitors download them again (119 KiB).
Render-blocking requests
500 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Reduce unused CSS
300 ms · 68 KiBAbout 68 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.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 250 ms
250 msGoogle CDN costs a phone 250 ms of main-thread work and 330 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.
Shopify adds 103 ms
103 msShopify costs a phone 103 ms of main-thread work and 319 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.
LoyaltyLion adds 73 ms
73 msLoyaltyLion costs a phone 73 ms of main-thread work and 345 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 · 35 KiBPolyfills for old browsers add 35 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 182 ms. During a long task the page ignores taps.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Duplicated JavaScript
13 KiB13 KiB JavaScript is shipped twice across bundles.
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 JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 38 ms
38 msYour server sent the HTML in 38 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.8 s
9.8 sYour largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 14.0 s
14.0 sThe page becomes fully interactive after 14.0 s. Good is under 3.8 s.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.193
0.193The layout shifts by 0.193 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 220 ms
220 msScripts block taps and scrolling for 220 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 107 ms to 118 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 125 ms
125 msReal visitors wait 125 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 403 ms
403 msReal visitors wait 403 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 2.8 MB in 301 requests
2.8 MBYour homepage downloads 2.8 MB in 301 requests on a phone: scripts 1.5 MB (166), other files 783 KiB (104) and images 226 KiB (8). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.80 g of CO₂e: 96.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Unlabelled dropdowns
1 dropdown has no label.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
33 text elements with low contrast
33 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 87 images in the HTML carry an alt attribute.
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
25 links with vague text
25 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Meta description is long (287 characters)
Your meta description is 287 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (OfferCatalog, Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://clarkrailworks.com/search?q={search_term_string}")”.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
256 internal links, 8 external
The homepage links to 256 pages on clarkrailworks.com and 8 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Clark Railworks”.
Title: 52 characters
Your title is a healthy 52 characters: “Model Trains, locomotives, coaches and rolling stock”.
Canonical URL set
The canonical URL is https://clarkrailworks.com/.
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://clarkrailworks.com/sitemap.xml.
AI search readiness
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.
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.
llms.txt published
The site publishes https://clarkrailworks.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages share 3 titles
https://clarkrailworks.com/blogs/news/quad-art-coaches and https://clarkrailworks.com/collections/quad-arts all use the title “Quad Art Coaches - Clark Railworks”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://clarkrailworks.com/collections/all, https://clarkrailworks.com/collections/quad-arts, https://clarkrailworks.com/collections/wd-2-10-0-austerity, https://clarkrailworks.com/collections/lowmacs, https://clarkrailworks.com/blogs/news and https://clarkrailworks.com/pages/contact-us and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 118 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 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 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
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.
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 10 words
The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
5 checks passed
28 calls to action
The homepage has 28 calls to action, for example “Shop”, “Pre Order” and “Contact”.
29 short forms
29 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 4 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 clarkrailworks.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Inbox · Loyalty Rewards And Referrals · Klaviyo Email Marketing Sms · Google Youtube · metizapps.com · eight-cdn.com · chimpstatic.com · amazonaws.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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on clarkrailworks.com, including 17 speed issues, 4 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.