3ngage.se website review

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

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

1 image could be 291 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

6 third-party services load with your homepage (piwik.pro, Hubspot and Google Tag Manager and others), adding 575 KiB and 262 ms of main-thread time.

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

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

47 KiB JavaScript is shipped twice across bundles.

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 page becomes fully interactive after 6.8 s. Good is under 3.8 s.

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

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

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 9.3 MB in 71 requests on a phone: media 8.4 MB (6), scripts 456 KiB (45) and images 328 KiB (4). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (307 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

1 image (307 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 2.63 g of CO₂e: 315.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

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

Your title is 75 characters, so Google will cut it off around 60: “3ngage - 3D Product & Machine Visualizations | Transform Your Sales Process”.

Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.

No XML sitemap at https://3ngage.se/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at 3ngage.se/robots.txt, the first file search crawlers ask for.

The homepage links to 40 pages on 3ngage.se and 3 external pages.

There is no /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 /posts all use the title “3ngage - 3D Product & Machine Visualizations | Transform Your Sales P…”. Search engines can't tell which page to show for a search, so each competes with the others.

/demos/husqvarna and /demos/simrad have no meta description, so Google writes the search snippet from whatever text it finds.

/entry_level_deal, /ai_product_expert and /bookdemo use the same meta description. A description written for each page earns more clicks.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

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.

3ngage.se 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.

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

DMARC is set to p=none, so mail pretending to be 3ngage.se 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 Tag Manager and HubSpot (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.

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

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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.