Website review, no card needed
24hr-safety.com website review
Visit site (opens in a new tab)Reviewed 20 October 202629 issues · 78 checks
This review found 29 issues worth fixing on 24hr-safety.com, 11 of them high impact, across 78 checks. The most urgent: render-blocking 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 104 ms |
| May 9, 2026 | 94 ms |
| May 16, 2026 | 94 ms |
| May 23, 2026 | 104 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 110 ms |
| Jun 13, 2026 | 108 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 118 ms |
| Jul 18, 2026 | 105 ms |
| Jul 25, 2026 | 121 ms |
| Aug 1, 2026 | 116 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 94 ms |
| Aug 22, 2026 | 79 ms |
| Aug 29, 2026 | 74 ms |
| Sep 5, 2026 | 71 ms |
| Sep 12, 2026 | 84 ms |
| Sep 19, 2026 | 101 ms |
| Sep 26, 2026 | 88 ms |
| Oct 3, 2026 | 79 ms |
| Oct 10, 2026 | 71 ms |
| Oct 17, 2026 | 82 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
Render-blocking requests
1.9 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Reduce unused JavaScript
1.1 s · 164 KiBAbout 164 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Improve image delivery
900 ms · 1.4 MB11 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62 (desktop: 84). 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 Tag Manager, WordPress and Google Analytics and others), adding 1.2 MB and 312 ms of main-thread time.
WordPress adds 118 ms
118 msWordPress costs a phone 118 ms of main-thread work and 827 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.
Use efficient cache lifetimes
200 ms · 31 KiB4 files are served with short cache lifetimes, so returning visitors download them again (31 KiB).
Reduce unused CSS
150 ms · 59 KiBAbout 59 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.
Legacy JavaScript
100 ms · 42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 108 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).
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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 589 ms of it running JavaScript. That is comfortably low.
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.
Real-user FCP: 3.2 s
3.2 sReal visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.8 s
2.8 sReal visitors wait 2.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 14.4 s
14.4 sYour largest element takes 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “24Hr Safety is a leader in the industrial safety sector, dr…”.
Time to Interactive: 14.9 s
14.9 sThe page becomes fully interactive after 14.9 s. Good is under 3.8 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 45% slower for real visitors
+45%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 104 ms to 82 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 97 ms
97 msScripts block the page for only 97 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: 16.4 MB in 120 requests
16.4 MBYour homepage downloads 16.4 MB in 120 requests on a phone: media 13.3 MB (6), images 2.2 MB (53) and scripts 605 KiB (33). Under 2 MB keeps phones on slow connections fast.
7 images below the first screen load straight away
7 images further down the page (201 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.7 g of CO₂ per visit
4.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.66 g of CO₂e: 558.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 48 images in the HTML carry an alt attribute.
27 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 27 passed and 6 failed. 2 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.
7 internal links, 20 external
The homepage links to 7 pages on 24hr-safety.com and 20 external pages.
7 checks passed
Meta description: 104 characters
Your meta description is 104 characters: “Shop at 24Hr Safety for high-quality safety equipment. We have everything you need to protect your team.”.
Title: 61 characters
Your title is a healthy 61 characters: “Industrial Safety Equipment, Rentals & Services - 24Hr Safety”.
Canonical URL set
The canonical URL is https://24hr-safety.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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://24hr-safety.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing 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.
No llms.txt
There is no https://24hr-safety.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 (446 words), so crawlers that don't run JavaScript still read it.
Other pages
3 internal pages checked
We fetched 3 pages linked from your homepage and read each the way a search engine does.
7 checks passed
Linked pages load
All 3 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 3 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 3 pages that loaded have a <title>.
Best practices
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”.
5 distorted images
5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
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.
Thin social proof
Social proof on the homepage: 46 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 319 words of copy
The homepage carries about 319 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “SHOP NOW”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 8 phone links and 0 email links.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
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 24hr-safety.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
- 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 29 issues on 24hr-safety.com, including 16 speed issues, 1 SEO issue 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.