novedge.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Hubspot and others), adding 1.8 MB and 1.1 s of main-thread time.

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

Google Tag Manager costs a phone 701 ms of main-thread work and 1,007 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.

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

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

10 images could be 284 KiB 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.

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

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

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

Shopify costs a phone 176 ms of main-thread work and 531 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.

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

Polyfills for old browsers add 41 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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.

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

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

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

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

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

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

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

Your homepage downloads 3.1 MB in 217 requests on a phone: scripts 1.7 MB (66), other files 836 KiB (109) and images 461 KiB (30). Under 2 MB keeps phones on slow connections fast.

rhino-widget-super_1600x.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example ChatIcon.png at 1,024 px wide, shown at 56 px. Resized copies would save about 178 KiB.

1 image (34 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.89 g of CO₂e: 106.4 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.

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

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

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

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

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

Your title is 67 characters, so Google will cut it off around 60: “NOVEDGE : The Largest Selection of 3D Design Software and Solutions”.

There are 3 <h1> headlines (“Search the Largest Selection of Design Software”, “Popular Products” and “Recent Blog Posts”). One clear main headline is easier for people and search engines.

Structured data found (Organization, Store and WebSite) but with 3 problems, for example “Organization: missing name”.

4 links have no real href, so search engines can't follow them.

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

The homepage links to 179 pages on novedge.com and 14 external pages.

https://novedge.com/collections/allproducts declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://novedge.com/collections/allproducts all use the title “NOVEDGE : The Largest Selection of 3D Design Software and Solutions”. Search engines can't tell which page to show for a search, so each competes with the others.

https://novedge.com/collections/products-on-promotion, https://novedge.com/collections/bundles, https://novedge.com/collections/civil-engineering, https://novedge.com/collections/hardware-products, https://novedge.com/collections/interior-design and https://novedge.com/collections/jewelry-design have no meta description, so Google writes the search snippet from whatever text it finds.

https://novedge.com/collections/bundles has no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “Unexpected end of input”.

1 image is displayed at the wrong aspect ratio, so it looks 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.

Social proof on the homepage: 246 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 656 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 3 mores (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 19 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 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.