Website review, no card needed

allsafety.com logo

allsafety.com website review

Visit site (opens in a new tab)Reviewed 19 October 202632 issues · 80 checks

This review found 32 issues worth fixing on allsafety.com, 10 of them high impact, across 80 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
729 ms614 msApr 25Oct 10654 ms
Show as table
DateReal-visitor load time (LCP)
Apr 25, 2026636 ms
May 2, 2026644 ms
May 9, 2026643 ms
May 16, 2026627 ms
May 23, 2026629 ms
May 30, 2026630 ms
Jun 6, 2026632 ms
Jun 13, 2026635 ms
Jun 20, 2026683 ms
Jun 27, 2026690 ms
Jul 4, 2026710 ms
Jul 11, 2026716 ms
Jul 18, 2026698 ms
Jul 25, 2026662 ms
Aug 1, 2026674 ms
Aug 8, 2026673 ms
Aug 15, 2026674 ms
Aug 22, 2026694 ms
Aug 29, 2026700 ms
Sep 5, 2026703 ms
Sep 12, 2026692 ms
Sep 19, 2026701 ms
Sep 26, 2026679 ms
Oct 3, 2026658 ms
Oct 10, 2026654 ms
Real-visitor tap response (INP)75th percentile, phones
175 ms132 msApr 25Oct 10155 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026145 ms
May 2, 2026145 ms
May 9, 2026152 ms
May 16, 2026156 ms
May 23, 2026162 ms
May 30, 2026162 ms
Jun 6, 2026153 ms
Jun 13, 2026148 ms
Jun 20, 2026155 ms
Jun 27, 2026152 ms
Jul 4, 2026154 ms
Jul 11, 2026151 ms
Jul 18, 2026137 ms
Jul 25, 2026137 ms
Aug 1, 2026137 ms
Aug 8, 2026141 ms
Aug 15, 2026149 ms
Aug 22, 2026154 ms
Aug 29, 2026160 ms
Sep 5, 2026160 ms
Sep 12, 2026162 ms
Sep 19, 2026170 ms
Sep 26, 2026162 ms
Oct 3, 2026163 ms
Oct 10, 2026155 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

Full-page screenshot of allsafety.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. allsafety.com at 0.5 s0.5 s
  2. allsafety.com at 0.9 s0.9 s
  3. allsafety.com at 1.4 s1.4 s
  4. allsafety.com at 1.9 s1.9 s
  5. allsafety.com at 2.3 s2.3 s
  6. allsafety.com at 2.8 s2.8 s
  7. allsafety.com at 3.3 s3.3 s
  8. allsafety.com at 3.7 s3.7 s

Speed

9 to fix56
  • Render-blocking requests

    2.5 s

    14 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.

  • Reduce unused JavaScript

    750 ms · 730 KiB

    About 730 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Clarity and others), adding 1.4 MB and 1.1 s of main-thread time.

  • Improve image delivery

    250 ms · 781 KiB

    14 images could be 781 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56 (desktop: 82). Pages that score under 90 lose visitors before the first paint.

  • Google CDN adds 547 ms

    547 ms

    Google CDN costs a phone 547 ms of main-thread work and 458 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 Tag Manager adds 436 ms

    436 ms

    Google Tag Manager costs a phone 436 ms of main-thread work and 671 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.

  • Reduce unused CSS

    300 ms · 31 KiB

    About 31 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.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 250 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    44 KiB

    2 files are served with short cache lifetimes, so returning visitors download them again (44 KiB).

  • Legacy JavaScript

    33 KiB

    Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 82 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 1.2 s of it running JavaScript. That is comfortably low.

  • Server response: 46 ms

    46 ms

    Your server sent the HTML in 46 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix67
  • 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: 7.3 s

    7.3 s

    Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ALL SAFETY ALTIJD EEN VEILIGE WERKOMGEVING”.

  • Time to Interactive: 14.6 s

    14.6 s

    The page becomes fully interactive after 14.6 s. Good is under 3.8 s.

  • First Contentful Paint: 3.3 s

    3.3 s

    The first text or image appears after 3.3 s on a phone. Good is under 1.8 s.

  • Real-user INP: 219 ms

    219 ms

    Real visitors wait 219 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Speed Index: 5.4 s

    5.4 s

    Visually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 397 ms

    397 ms

    Scripts block taps and scrolling for 397 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) got 10% slower for real visitors

    +10%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 145 ms to 155 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 0.6 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 1.0 s

    1.0 s

    Real visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.9 s

    0.9 s

    Real visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 367 ms

    367 ms

    Real visitors wait 367 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 5.1 MB in 94 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 94 requests on a phone: images 3.6 MB (48), scripts 1.4 MB (19) and stylesheets 56 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 6 images below the first screen load straight away

    6 images further down the page (150 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (31 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 1.4 g of CO₂ per visit

    1.44 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.44 g of CO₂e: 173.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 9089
  • 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.

  • 11 tap targets too small

    11 tap targets are too small or too close together to hit reliably with a finger.

  • Interactive controls must not be nested (10 elements)

    Interactive controls must not be nested: 10 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (52 elements)

    All page content should be contained by landmarks: 52 elements on the page fail this check, rated moderate by axe-core.

  • 9 form fields without a label

    9 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 7 links without text

    7 visible links have no text or label, so screen readers cannot say where they go.

  • 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.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 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. (3 elements).

2 checks passed
  • Every image has alt text

    All 16 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

3 to fixGoogle 9290
  • 2 H1 headlines

    There are 2 <h1> headlines (“ALL SAFETY” and “ALTIJD EEN VEILIGEWERKOMGEVING”). 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.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 134 internal links, 11 external

    The homepage links to 134 pages on allsafety.com and 11 external pages.

6 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “All Safety is uw specialist voor veiligheidsproducten, werkkleding en ademhalingsoplossingen. Bekijk onze verhuur, leve…”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Veiligheidsproducten, werkkleding en adembescherming | All Safety”.

  • Canonical URL set

    The canonical URL is https://www.allsafety.com/.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

  • 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://www.allsafety.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.allsafety.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.

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, sameAs (social profiles) and contact details; logo and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,398 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 90 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 7785
  • 3 small tap targets

    3 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 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 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 725 words of copy

    The homepage carries about 725 words of visible text.

5 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact”.

  • 3 short forms

    3 short forms (4 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 10 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (measured from a US location before any click).

  • 22 other companies contacted

    Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 allsafety.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
Analytics
Google Tag Manager

Company

Founded
1977
Headquarters
Hoogvliet

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on allsafety.com, including 16 speed issues, 3 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25