inshared.nl website review

Your mobile performance score is 97. That is in Google's “good” band (90 and up).

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

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

Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

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

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

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

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

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

The page is fully interactive after 2.5 s.

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

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

Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “De Autoverzekering van InShared is als beste getest!”.

Scripts block the page for only 15 ms while loading. Good is under 200 ms.

Your homepage downloads 369 KiB in 86 requests on a phone: scripts 112 KiB (36), other files 106 KiB (41) and stylesheets 46 KiB (1). That is a lean page.

Every sizeable image is WebP, AVIF or SVG.

Images below the first screen wait until the visitor scrolls to them.

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

All 20 images in the HTML carry an alt attribute.

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

Your meta description is 156 characters: “Een eerlijke autoverzekering, woonverzekering, reisverzekering, fietsverzekering of andere verzekeringen. Lage premie, …”.

Your main headline reads: “De Autoverzekering van InShared is als beste getest!”.

Your title is a healthy 58 characters: “Online verzekeringen afsluiten | InShared - We all benefit”.

The canonical URL is https://www.inshared.nl/.

Structured data found: InsuranceAgency and WebPage.

Open Graph tags are complete, so shared links show a title, description and image.

robots.txt is in place and points crawlers to your sitemap.

Your XML sitemap is reachable at https://www.inshared.nl/sitemap-index.xml.

Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

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

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

All 15 pages we checked loaded without an error.

No page we checked hands its ranking to a different URL.

All 14 pages that loaded have a meta description.

Every page we checked has its own title.

Each page we checked has a main headline.

None of the pages we checked carries a noindex tag.

All 14 pages that loaded have a <title>.

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

21 of 21 tappable elements near the top are at least 24 px.

The page declares a mobile viewport.

The homepage is served over HTTPS (inshared.nl).

The certificate from Sectigo Limited · Sectigo Public Server Authentication CA OV R36 verifies for inshared.nl and is valid for another 172 days.

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

Strict-Transport-Security is set, so browsers always use https.

http://inshared.nl redirects to the secure version.

All 49 links checked from your homepage (40 internal, 9 external) answered without errors; 6 did not answer within 5 s.

inshared.nl was registered in Jun 2008 through Hostnet B.V.. An established domain carries more trust with email providers and search engines.

inshared.nl's DNS answers are signed (DNSSEC), so they can't be forged on the way to visitors.

The homepage has 2 calls to action, for example “Zo neemt u contact met ons op Contact” and “Contact”.

A short form (1 field at most) is right on the homepage.

Social proof on the homepage: 122 testimonial or review blocks and 1 trust badge.

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

Your phone number is on the homepage as a tap-to-call link.

Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

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

An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 ip4:82.199.69.221 ip4:82.199.69.231 ip4:149.72.24.16 include:spf.protection.outlook.com include:sendgrid.net inc…”.

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

No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).