Website review, no card needed

dropsafe.com logo

dropsafe.com website review

Visit site (opens in a new tab)Reviewed 9 November 202626 issues · 101 checks

This review found 26 issues worth fixing on dropsafe.com, 3 of them high impact, across 101 checks. The most urgent: fails Core Web Vitals for real visitors. 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
3.0 s2.1 sMay 23Nov 72.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.9 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.7 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.8 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.8 s
Sep 26, 20262.7 s
Oct 3, 20262.5 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Nov 7, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
253 ms165 msMay 23Nov 7223 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026185 ms
May 30, 2026181 ms
Jun 6, 2026176 ms
Jun 13, 2026184 ms
Jun 20, 2026196 ms
Jun 27, 2026206 ms
Jul 4, 2026214 ms
Jul 11, 2026211 ms
Jul 18, 2026199 ms
Jul 25, 2026192 ms
Aug 1, 2026175 ms
Aug 8, 2026186 ms
Aug 15, 2026199 ms
Aug 22, 2026212 ms
Aug 29, 2026226 ms
Sep 5, 2026229 ms
Sep 12, 2026235 ms
Sep 19, 2026235 ms
Sep 26, 2026243 ms
Oct 3, 2026233 ms
Oct 10, 2026220 ms
Oct 17, 2026206 ms
Oct 24, 2026191 ms
Oct 31, 2026204 ms
Nov 7, 2026223 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 dropsafe.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dropsafe.com at 0.4 s0.4 s
  2. dropsafe.com at 0.8 s0.8 s
  3. dropsafe.com at 1.1 s1.1 s
  4. dropsafe.com at 1.5 s1.5 s
  5. dropsafe.com at 1.9 s1.9 s
  6. dropsafe.com at 2.3 s2.3 s
  7. dropsafe.com at 2.6 s2.6 s
  8. dropsafe.com at 3.0 s3.0 s

dropsafe.com does not allow embedding, so this is Google's rendering of the page.

Speed

5 to fix83
  • Mobile performance score: 83

    83/100

    Your mobile performance score is 83. 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, Clarity and Shopify and others), adding 857 KiB and 791 ms of main-thread time.

  • Render-blocking requests

    650 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

  • Google Tag Manager adds 572 ms

    572 ms

    Google Tag Manager costs a phone 572 ms of main-thread work and 672 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 JavaScript

    442 KiB

    About 442 KiB of JavaScript is downloaded but never used on this page.

  • 8 long tasks on the main thread

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

  • Improve image delivery

    90 KiB

    6 images could be 90 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Use efficient cache lifetimes

    31 KiB

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

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

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 10 ms

    10 ms

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

Core Web Vitals

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

  • Time to Interactive: 11.5 s

    11.5 s

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

  • Real-user INP: 223 ms

    223 ms

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

    Your largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Global leader in dropped object prevention”.

  • Total Blocking Time: 368 ms

    368 ms

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

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

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

    +17%

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

6 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 20% faster for real visitors

    -20%

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

  • Speed Index: 2.9 s

    2.9 s

    Visually, the page fills in at 2.9 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.012

    0.012

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 195 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 195 requests on a phone: scripts 983 KiB (53), other files 807 KiB (123) and images 245 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (120 KiB) are 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 0.6 g of CO₂ per visit

    0.60 g

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

2 checks passed
  • 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

3 to fixGoogle 10097
  • All page content should be contained by landmarks (4 elements)

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

  • 32 links without text

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

  • 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 11 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9294
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 120 internal links, 6 external

    The homepage links to 120 pages on dropsafe.com and 6 external pages.

7 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Dropsafe is the global leader in Dropped Object prevention, helping businesses to mitigate the risks they pose to peopl…”.

  • One H1 headline

    Your main headline reads: “Global leader in dropped object prevention”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Dropsafe - Global Leader in Drops Prevention & Safety”.

  • Canonical URL set

    The canonical URL is https://dropsafe.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://dropsafe.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 15 pages without an H1

    /pages/b2b-customer-register, /collections, /products/dropsafe-barrier, /products/dropsafe-nets, /products/dropsafe-helideck-perimeter-safety-net and /products/dropsafe-slings and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 pages with very little text

    /pages/b2b-customer-register, /collections, /products/dropsafe-barrier, /products/dropsafe-nets, /products/dropsafe-helideck-perimeter-safety-net and /products/dropsafe-slings and 7 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

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

  • 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

2 to fixGoogle 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=97044734&Ver=2&mid=ec66b7e8-0dda-4d0b-931b-f55c24d54b45&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Dropsafe%20-%20Global%20Leader%20in%20Drops%20Preventio.

  • 32 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • 1 link through redirect chains

    1 link go through two or more redirects, for example https://dropsafe-endeavour.myshopify.com/collections/dropsafe-barricade.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (dropsafe.com).

  • Valid certificate (57 days left)

    The certificate from Let's Encrypt · YE1 verifies for dropsafe.com and is valid for another 57 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://dropsafe.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 44 links work

    All 44 links checked from your homepage (40 internal, 4 external) answered without errors.

Domain and trust

  • No CAA record

    dropsafe.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    dropsafe.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 24 years old

    24 years

    dropsafe.com was registered in Jul 2002 through 101domain GRS Limited. An established domain carries more trust with email providers and search engines.

  • Registered until Jul 2027

    dropsafe.com is registered until Jul 2027.

Content and conversion

2 to fix88
  • 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: 1 testimonial or review block. 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 297 words of copy

    The homepage carries about 297 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: “Learn more” and “Register your company”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Register your company”, “Shop” and “Contact”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

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

Email authentication

85
  • Email authentication score: 85/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:spf.protection.outlook.com include:servers.mcsv.net ~all”.

  • DKIM signing found

    A DKIM key is published (selector “k1”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Ads and 2 mores (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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 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.

  • 20 other companies contacted

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

Apps on your store

Your storefront loads 4 apps. Each one is code from another company running for your shoppers.

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

Pandectes Gdpr · Powerful Form Builder · Gdpr Cookie Consent · Courses

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

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on dropsafe.com, including 13 speed issues, 2 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

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