Website review, no card needed
akrailroad.com website review
Visit site (opens in a new tab)Reviewed 18 October 202643 issues · 94 checks
This review found 43 issues worth fixing on akrailroad.com, 13 of them high impact, across 94 checks. The most urgent: use efficient cache lifetimes. 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
81B- #40,754 of 121,500 reviewed websitesbeats 61%
- #27,139 of 68,739 online storesbeats 54%
- #181 of 889 BigCommerce storesbeats 74%
Closest competitors among BigCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.5 s |
| May 2, 2026 | 1.5 s |
| May 9, 2026 | 1.5 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 93 ms |
| May 2, 2026 | 93 ms |
| May 9, 2026 | 93 ms |
| May 16, 2026 | 101 ms |
| May 23, 2026 | 93 ms |
| May 30, 2026 | 94 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 91 ms |
| Jun 20, 2026 | 92 ms |
| Jun 27, 2026 | 91 ms |
| Jul 4, 2026 | 92 ms |
| Jul 11, 2026 | 88 ms |
| Jul 18, 2026 | 89 ms |
| Jul 25, 2026 | 92 ms |
| Aug 1, 2026 | 89 ms |
| Aug 8, 2026 | 89 ms |
| Aug 15, 2026 | 86 ms |
| Aug 22, 2026 | 86 ms |
| Aug 29, 2026 | 94 ms |
| Sep 5, 2026 | 92 ms |
| Sep 12, 2026 | 96 ms |
| Sep 19, 2026 | 95 ms |
| Sep 26, 2026 | 83 ms |
| Oct 3, 2026 | 80 ms |
| Oct 10, 2026 | 76 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
Use efficient cache lifetimes
3.8 s · 4.4 MB38 files are served with short cache lifetimes, so returning visitors download them again (4.4 MB).
Reduce unused JavaScript
5.4 s · 848 KiBAbout 848 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.4 s faster on a phone.
Improve image delivery
1.4 s · 1.2 MB11 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Reduce unused CSS
2.2 s · 299 KiBAbout 299 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.2 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (POWr, powrcdn.com and Google Tag Manager and others), adding 10.6 MB and 903 ms of main-thread time.
powrcdn.com adds 280 ms
280 mspowrcdn.com costs a phone 280 ms of main-thread work and 8.3 MB 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.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 61). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
POWr adds 287 ms
287 msPOWr costs a phone 287 ms of main-thread work and 138 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.
Bigcommerce adds 115 ms
115 msBigcommerce costs a phone 115 ms of main-thread work and 1.7 MB 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.
Google Tag Manager adds 166 ms
166 msGoogle Tag Manager costs a phone 166 ms of main-thread work and 337 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 115 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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 JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 799 ms of it running JavaScript. That is comfortably low.
Server response: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 10.9 s
10.9 sThe first text or image appears after 10.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 19.3 s
19.3 sYour largest element takes 19.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 24.5 s
24.5 sThe page becomes fully interactive after 24.5 s. Good is under 3.8 s.
Speed Index: 13.7 s
13.7 sVisually, the page fills in at 13.7 s (Speed Index). Good is under 3.4 s.
21 images without width and height
21 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 113 ms
113 msReal visitors wait 113 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.
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.
Real-user TTFB: 747 ms
747 msReal visitors wait 747 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 93 ms to 76 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 77 ms
77 msScripts block the page for only 77 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: 11.7 MB in 103 requests
11.7 MBYour homepage downloads 11.7 MB in 103 requests on a phone: images 9.6 MB (27), scripts 1.5 MB (33) and stylesheets 449 KiB (19). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
MicrosoftTeams-image_12.png 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).
8 images below the first screen load straight away
8 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
73 KiB2 images are downloaded at several times the size a phone draws them, for example updated-map.png at 1,047 px wide, shown at 341 px. Resized copies would save about 73 KiB.
About 3.3 g of CO₂ per visit
3.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.32 g of CO₂e: 398.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
ARIA commands must have an accessible name (1 element)
ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (29 elements)
All page content should be contained by landmarks: 29 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail 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. (3 elements).
2 checks passed
Every image has alt text
All 19 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (22 characters)
Your title is only 22 characters: “A&K Railroad Materials”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (23 characters)
Your meta description is only 23 characters: “We Provide What Matters”. 70 to 160 characters is enough to sell the click.
2 H1 headlines
There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://akrailroad.com/sitemap.xml, so Google discovers your pages only by following links.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
86 internal links, 2 external
The homepage links to 86 pages on akrailroad.com and 2 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://akrailroad.com/.
robots.txt in place
robots.txt is in place.
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://akrailroad.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 (459 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages without a meta description
https://akrailroad.com/about, https://akrailroad.com/about/history, https://akrailroad.com/about/sustainability, https://akrailroad.com/about/values, https://akrailroad.com/services/-1 and https://akrailroad.com/services/continuous-welded-rail-cwr and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
13 links to non-canonical URLs
Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://akrailroad.com/about/history, whose canonical is https://akrailroad.com/history. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 67 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.
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 15 pages that loaded have a <title>.
Best practices
4 third-party cookies
4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“webkitRequestAnimationFrame is vendor-specific. Please use the standard requestAnimationFrame inste…”).
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 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
25 of 27 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.
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 350 words of copy
The homepage carries about 350 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “REQUEST QUOTE” and “SHOP PRODUCTS”.
7 calls to action
The homepage has 7 calls to action, for example “Quote”, “Request a Quote” and “All Contact Us”.
2 short forms
2 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 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
26 other companies contacted
Loading the homepage contacts 26 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 akrailroad.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- BigCommerce
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on akrailroad.com, including 16 speed issues, 7 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.