novypom.com website review

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

4 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.7 s faster on a phone.

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

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

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

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

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

1 long task block the main thread while loading, the longest for 57 ms. During a long task the page ignores taps.

2 third-party services load with your homepage (Google Fonts and auburnforest.com), adding 131 KiB and 1 ms of main-thread time.

9 KiB could be saved by minifying CSS.

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

6 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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.

homePageH.png weighs 536 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.1 MB in 77 requests on a phone: images 1.3 MB (6), fonts 293 KiB (11) and scripts 276 KiB (32). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example homePageH.png at 1,500 px wide, shown at 183 px. Resized copies would save about 464 KiB.

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

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

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

All page content should be contained by landmarks: 17 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: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

There are 3 <h1> headlines (“Accelerate and secure the execution of your proce…”, “With Novy POM, speed up and make your invoice man…” and “Evaluate the benefits and automation potential of…”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 40 pages on novypom.com and 5 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://novypom.com/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.

https://novypom.com/en/home and / all use the title “Novy POM : purchase & order management”. Search engines can't tell which page to show for a search, so each competes with the others.

https://novypom.com/en/solution-2/faq, https://novypom.com/en/legal-notices, https://novypom.com/en/privacy-policy and https://novypom.com/en/terms-of-use have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://novypom.com/en/home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://novypom.com/en/solution-2, https://novypom.com/en/solution-2/our-vision, https://novypom.com/en/solution-2/the-benefits, https://novypom.com/en/solution-2/faq, https://novypom.com/en/the-features and https://novypom.com/en/about and 4 others took over 3 s to send their HTML from our server.

We fetched 14 pages linked from your homepage and read each the way a search engine does.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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