miswag.net website review

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

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

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

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

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

5 third-party services load with your homepage (rudderstack.com, miswag.net and cloudfront.net and others), adding 1.4 MB and 0 ms of main-thread time.

miswag.me costs a phone 0 ms of main-thread work and 1.2 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

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

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

For real visitors the layout shifts by 0.38 (75th percentile). Good is under 0.1.

Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

The layout shifts by 0.139 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Scripts block taps and scrolling for 234 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.

Your homepage downloads 2.2 MB in 244 requests on a phone: images 1.4 MB (100), scripts 625 KiB (131) and fonts 109 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

No XML sitemap at https://miswag.com/sitemap.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 168 pages on miswag.net and 11 external pages.

There is no https://miswag.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://miswag.com/en and / all use the title “Miswag — Online Shopping in Iraq”. Search engines can't tell which page to show for a search, so each competes with the others.

https://miswag.com/en/preset/bf26-main-preset, https://miswag.com/en/preset/freedelivery-bf26, https://miswag.com/en/preset/electronics-main-bf26, https://miswag.com/en/preset/beauty-perfume-bf26, https://miswag.com/en/preset/homeappliances-bf26 and https://miswag.com/en/preset/fashion-watch-acs-bf26 and 3 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 /, whose canonical is https://miswag.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://miswag.com/en/preset/bf26-main-preset, https://miswag.com/en/preset/freedelivery-bf26, https://miswag.com/en/preset/electronics-main-bf26, https://miswag.com/en/preset/beauty-perfume-bf26, https://miswag.com/en/preset/homeappliances-bf26 and https://miswag.com/en/preset/fashion-watch-acs-bf26 and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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 1,014 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.