idscan.net website review

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

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

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

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

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

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

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

A phone's processor spends 2.9 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, Hubspot and jQuery CDN and others), adding 437 KiB and 454 ms of main-thread time.

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

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

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

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.

5 KiB could be saved by minifying JavaScript.

Your largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ID fraud prevention at scale”.

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

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

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

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

Your homepage downloads 2.2 MB in 111 requests on a phone: images 910 KiB (12), scripts 597 KiB (37) and fonts 422 KiB (3). Under 2 MB keeps phones on slow connections fast.

1 image (140 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.

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

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

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

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

ARIA role should be appropriate for the element: 14 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h4, h3 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (2 elements).

There are 2 <h1> headlines (“ID fraud prevention at scale” and “Scanning IDs, authenticating documents, and verif…”). One clear main headline is easier for people and search engines.

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

The homepage links to 190 pages on idscan.net and 15 external pages.

/notification-data-security-incident is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/veriscan-age-verification-visitor-management-software, /id-scanning, /remote-id-validation-2, /age-verification-software and /id-fraud-prevention-software have no <h1> headline, so visitors and search engines get no clear main topic.

/veriscan-age-verification-visitor-management-software has 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 15 pages linked from your homepage (of 88 found) and read each the way a search engine does.

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97186594&Ver=2&mid=b0e3cc52-a4f4-47c8-852b-752ab86c3cd5&bo=1&sid=0f254e10cf0d11f1aba72b07dc72a508&vid=0f254840cf0d11f1b22fb5150f370782&vids=1&msclkid=N&pid=em%3D07d9be.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Mixed content”).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

2 links go through two or more redirects, for example https://idscan.net/product/unitech-pa768-id-and-passport-scanner-handheld-visitor-management-bundle/.

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

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

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

idscan.net is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

idscan.net'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.

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 890 words of visible text.

DMARC is set to p=none, so mail pretending to be idscan.net is still delivered. Reports are on, so moving to quarantine is the next step.

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.

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

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

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