myipg.com website review

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

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

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

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

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

pop-convert.com costs a phone 260 ms of main-thread work and 162 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.

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

3 third-party services load with your homepage (pop-convert.com, Shopify and shop.app), adding 703 KiB and 458 ms of main-thread time.

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 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 320 requests on a phone: images 1.1 MB (44), other files 951 KiB (140) and scripts 725 KiB (92). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example prolens_sablon_4d186dbf-ef4a-4d9a-9778-f2c789e24eff.jpg at 342 px wide, shown at 113 px. Resized copies would save about 4 KiB.

2 images (133 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 0.88 g of CO₂e: 105.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

The homepage links to 225 pages on myipg.com and 6 external pages.

https://myipg.com/collections/apple, https://myipg.com/collections/samsung, https://myipg.com/collections/xiaomi-phone, https://myipg.com/collections/phone-more, https://myipg.com/collections/apple-watch and https://myipg.com/collections/garmin-watch and 8 others 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 https://myipg.com/collections/samsung-watch-1/%3E%3EMORE%3C%3C, whose canonical is https://myipg.com/collections/samsung-watch-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://myipg.com/pages/register-your-product has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 690 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and TikTok Pixel (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 12 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.