nexusadvice.com website review

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

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

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

About 161 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 36 (desktop: 44). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

The page has 2,666 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

10 KiB could be saved by minifying JavaScript.

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

7 KiB could be saved by minifying CSS.

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.

1 third-party service load with your homepage (Google Fonts), adding 33 KiB and 0 ms of main-thread time.

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.

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

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

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

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

Your largest element takes 15.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (7.7 s).

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

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

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

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

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

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

Your homepage downloads 11.9 MB in 137 requests on a phone: media 9.4 MB (2), images 768 KiB (19) and scripts 697 KiB (50). Under 2 MB keeps phones on slow connections fast.

2 images (87 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.

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

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

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

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Your title is 69 characters, so Google will cut it off around 60: “Insurance Brokers in Dubai, UAE | Buy Online Insurance Policy | Nexus”.

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

Structured data found (BreadcrumbList, FAQPage, ImageObject and Organization) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("https://www.youtube.com/results?search_query=nexus in…”.

The homepage links to 113 pages on nexusadvice.com and 13 external pages.

https://www.nexusadvice.com/personal/advisory-is-listening has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.nexusadvice.com/personal/contact-us, https://www.nexusadvice.com/personal/our-providers, https://www.nexusadvice.com/careers, https://www.nexusadvice.com/blog, https://www.nexusadvice.com/corporate and https://www.nexusadvice.com/personal/advisory-is-listening have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.nexusadvice.com/personal/car-insurance, https://www.nexusadvice.com/personal/health-insurance, https://www.nexusadvice.com/personal/home-insurance, https://www.nexusadvice.com/personal/travel-insurance, https://www.nexusadvice.com/personal/contact-us and https://www.nexusadvice.com/who-we-are and 6 others took over 3 s to send their HTML from our server.

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

8 of 33 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”.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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 1,526 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, 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 4 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.