scanone.tech website review

About 215 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

14 images could be 4.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

18 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).

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

Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.

4 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts and others), adding 6.2 MB and 356 ms of main-thread time.

googleusercontent.com costs a phone 0 ms of main-thread work and 5.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.

Google CDN costs a phone 302 ms of main-thread work and 636 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.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Control who enters your site with secure facial matching, d…”. Most of its time is element render delay (2.3 s).

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 6.3 MB in 46 requests on a phone: images 5.4 MB (18), scripts 529 KiB (10) and stylesheets 226 KiB (5). Under 2 MB keeps phones on slow connections fast.

4 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example APXyLQfaNPHxQkIUKKuAoaUAClPbM6IcfdH_hO7qT90CrFc72o4MAEYxcMH3 at 1,280 px wide, shown at 257 px. Resized copies would save about 2.1 MB.

8 images (4.5 MB) 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.

10 images further down the page (4.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

34 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

14 images have no alt text, which hurts accessibility and image search.

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

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 7 characters: “ScanOne”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 2 <h1> headlines (“ScanOne For Secure Site Access” and “DO YOU KNOW WHO'S ON-SITE RIGHT NOW?”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://www.scanone.tech/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at scanone.tech/robots.txt, the first file search crawlers ask for.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 21 pages on scanone.tech and 3 external pages.

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.

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

/ and https://www.scanone.tech/home all use the title “ScanOne”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.scanone.tech/home, https://www.scanone.tech/solutions, https://www.scanone.tech/industries, https://www.scanone.tech/about, https://www.scanone.tech/faqs and https://www.scanone.tech/contact have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.scanone.tech/industries and https://www.scanone.tech/contact 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.

We fetched 6 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://play.google.com/log?format=json&hasfast=true&authuser=0' from origin 'https://www.scanone.t…”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 261 words of visible text.

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.

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