Website review, no card needed
ashcroft.com website review
Visit site (opens in a new tab)Reviewed 18 November 202631 issues · 87 checks
This review found 31 issues worth fixing on ashcroft.com, 13 of them high impact, across 87 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
83B- #27,001 of 117,584 reviewed websitesbeats 72%
- #17,851 of 66,923 online storesbeats 67%
- #306 of 2,700 WooCommerce storesbeats 85%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.7 s |
| Jun 13, 2026 | 4.5 s |
| Jun 20, 2026 | 4.3 s |
| Jun 27, 2026 | 4.1 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.1 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.9 s |
| Sep 12, 2026 | 4.0 s |
| Sep 19, 2026 | 4.1 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 3.8 s |
| Oct 24, 2026 | 3.8 s |
| Oct 31, 2026 | 3.6 s |
| Nov 7, 2026 | 3.7 s |
| Nov 14, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 232 ms |
| Jun 6, 2026 | 231 ms |
| Jun 13, 2026 | 221 ms |
| Jun 20, 2026 | 228 ms |
| Jun 27, 2026 | 218 ms |
| Jul 4, 2026 | 229 ms |
| Jul 11, 2026 | 236 ms |
| Jul 18, 2026 | 235 ms |
| Jul 25, 2026 | 235 ms |
| Aug 1, 2026 | 227 ms |
| Aug 8, 2026 | 227 ms |
| Aug 15, 2026 | 226 ms |
| Aug 22, 2026 | 216 ms |
| Aug 29, 2026 | 228 ms |
| Sep 5, 2026 | 227 ms |
| Sep 12, 2026 | 236 ms |
| Sep 19, 2026 | 249 ms |
| Sep 26, 2026 | 239 ms |
| Oct 3, 2026 | 242 ms |
| Oct 10, 2026 | 238 ms |
| Oct 17, 2026 | 238 ms |
| Oct 24, 2026 | 239 ms |
| Oct 31, 2026 | 235 ms |
| Nov 7, 2026 | 220 ms |
| Nov 14, 2026 | 212 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.2 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.
Use efficient cache lifetimes
2.0 s · 646 KiB22 files are served with short cache lifetimes, so returning visitors download them again (646 KiB).
Render-blocking requests
1.3 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.8 MB and 1.3 s of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 90 KiBAbout 90 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 437 ms
437 msGoogle Tag Manager costs a phone 437 ms of main-thread work and 850 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.
Google CDN adds 404 ms
404 msGoogle CDN costs a phone 404 ms of main-thread work and 1.1 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.
Improve image delivery
430 KiB2 images could be 430 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,562 HTML elements
The page has 1,562 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
200 ms · 50 KiBPolyfills for old browsers add 50 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 196 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).
Minify JavaScript
32 KiB32 KiB could be saved by minifying JavaScript.
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: 5 ms
5 msYour server sent the HTML in 5 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.
Largest Contentful Paint: 15.6 s
15.6 sYour largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Keep Your Business Running Safely with Reliable Pressure & …”.
Time to Interactive: 29.2 s
29.2 sThe page becomes fully interactive after 29.2 s. Good is under 3.8 s.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 936 ms
936 msReal visitors wait 936 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 577 ms
577 msScripts block taps and scrolling for 577 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 232 ms to 212 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 179 ms
179 msReal visitors wait 179 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.
Largest content (LCP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.8 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 173 requests
4.9 MBYour homepage downloads 4.9 MB in 173 requests on a phone: scripts 3.0 MB (64), images 758 KiB (27) and other files 525 KiB (51). Under 2 MB keeps phones on slow connections fast.
About 1.4 g of CO₂ per visit
1.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.38 g of CO₂e: 165.3 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
Required ARIA attributes must be provided (17 elements)
Required ARIA attributes must be provided: 17 elements on the page fail this check, rated critical by axe-core.
Interactive controls must not be nested (17 elements)
Interactive controls must not be nested: 17 elements on the page fail this check, rated serious by axe-core.
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
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.
ARIA role should be appropriate for the element (17 elements)
ARIA role should be appropriate for the element: 17 elements on the page fail this check, rated minor by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 24 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
188 internal links, 27 external
The homepage links to 188 pages on ashcroft.com and 27 external pages.
8 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Trust Ashcroft's Pressure instruments & Temperature Instruments for process industry or OEM applications. Avoid downtim…”.
One H1 headline
Your main headline reads: “Keep Your Business Running Safely with Reliable Pressure & Temperature Instruments”.
Title: 57 characters
Your title is a healthy 57 characters: “Pressure Instruments - Temperature Instruments | Ashcroft”.
Canonical URL set
The canonical URL is https://www.ashcroft.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.ashcroft.com/sitemap.xml.
AI search readiness
4 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: 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 (1,031 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.ashcroft.com/llms.txt (10 KiB, 66 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 62 found) and read each the way a search engine does.
7 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.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=259003087&tm=gtm002&Ver=2&mid=fb650ef8-5c1c-421e-be15-c7aa16cb0b9e&bo=1&sid=fe73dbc0e35c11f1ad010d5f89bbec55&vid=fe73dfe0e35c11f1b7195122f8f1b20c&vids=1&msclkid=N&pi=9.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 (Forbidden)”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
94 of 97 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
About 1,009 words of copy
The homepage carries about 1,009 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: “Contact” and “Get a Quote”.
13 calls to action
The homepage has 13 calls to action, for example “Contact”, “Get a Quote” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Hotjar, HubSpot and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
21 cookies set on arrival
21Opening the homepage sets 21 cookies, 4 of them by other companies (measured from a US location before any click).
46 other companies contacted
Loading the homepage contacts 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 ashcroft.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
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Cloudflare
Company
- Employees
- 369
- Founded
- 1852
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on ashcroft.com, including 19 speed 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.