novology.com website review

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

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

19 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

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

8 third-party services load with your homepage (epsilondelta.co, Clarity and Optanon and others), adding 650 KiB and 805 ms of main-thread time.

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

About 139 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

epsilondelta.co costs a phone 393 ms of main-thread work and 39 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.

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

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

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

15 KiB could be saved by minifying CSS.

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

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.

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 522 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Your largest element takes 12.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

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

Your homepage downloads 60.4 MB in 436 requests on a phone: media 49.3 MB (21), images 8.9 MB (98) and other files 1.1 MB (229). Under 2 MB keeps phones on slow connections fast.

11 images are downloaded at several times the size a phone draws them, for example Pigmentation_570d171f-06e5-4163-994f-9110bbd3a01b.webp at 500 px wide, shown at 80 px. Resized copies would save about 1.3 MB.

15 images (2.1 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.

14 images further down the page (734 KiB) 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 17.12 g of CO₂e: 2054.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

24 elements hidden from screen readers can still receive keyboard focus.

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

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

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

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

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

The homepage links to 217 pages on novology.com and 20 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

https://www.novology.com/collections/all is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.novology.com/collections/all and https://www.novology.com/collections/pro-lift use the same meta description. A description written for each page earns more clicks.

https://www.novology.com/pages/terms-and-condition has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.novology.com/.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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

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

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

Before a visitor clicks anything, the page loads Microsoft Clarity (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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