magecom.net website review

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

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

8 third-party services load with your homepage (Cookiebot, website-files.com and JSDelivr CDN and others), adding 25.9 MB and 602 ms of main-thread time.

website-files.com costs a phone 209 ms of main-thread work and 25.4 MB 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.

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

Your mobile performance score is 55 (desktop: 67). Pages that score under 90 lose visitors before the first paint.

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

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

Cookiebot costs a phone 280 ms of main-thread work and 163 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.

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

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

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

81 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.

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

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

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

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

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

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

Your homepage downloads 26.1 MB in 109 requests on a phone: media 23.9 MB (12), images 1.1 MB (32) and scripts 768 KiB (46). Under 2 MB keeps phones on slow connections fast.

686fbe8d2be8f7ae8475db7a_seo_points.gif weighs 562 KiB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example 686fbe8d2be8f7ae8475db7a_seo_points.gif at 512 px wide, shown at 50 px. Resized copies would save about 553 KiB.

689b12942af2554b2b5bd0b6_Bg.avif 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 (562 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 7.41 g of CO₂e: 888.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

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

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

12 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.

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

Structured data found (Organization) but with 1 problem, for example “Organization: sameAs is an empty list”.

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

The homepage links to 47 pages on magecom.net and 4 external pages.

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

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

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

Large scripts ship without source maps.

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

Your homepage shows a street address 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 link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 2,657 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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