Website review, no card needed

istyle.iq logo

istyle.iq website review

Visit site (opens in a new tab)Reviewed 7 November 202629 issues · 83 checks

This review found 29 issues worth fixing on istyle.iq, 9 of them high impact, across 83 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.3 s1.4 sMay 16Oct 312.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20263.6 s
Jun 20, 20263.7 s
Jun 27, 20263.6 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.7 s
Jul 25, 20263.9 s
Aug 1, 20264.0 s
Aug 8, 20263.9 s
Aug 15, 20263.8 s
Aug 22, 20263.6 s
Aug 29, 20263.0 s
Sep 5, 20263.0 s
Sep 12, 20263.0 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.2 s
Oct 10, 20263.3 s
Oct 17, 20263.1 s
Oct 24, 20262.9 s
Oct 31, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
331 ms214 msMay 16Oct 31244 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026227 ms
May 23, 2026229 ms
May 30, 2026238 ms
Jun 6, 2026251 ms
Jun 13, 2026285 ms
Jun 20, 2026292 ms
Jun 27, 2026287 ms
Jul 4, 2026287 ms
Jul 11, 2026288 ms
Jul 18, 2026299 ms
Jul 25, 2026313 ms
Aug 1, 2026317 ms
Aug 8, 2026317 ms
Aug 15, 2026315 ms
Aug 22, 2026308 ms
Aug 29, 2026288 ms
Sep 5, 2026279 ms
Sep 12, 2026275 ms
Sep 19, 2026270 ms
Sep 26, 2026271 ms
Oct 3, 2026269 ms
Oct 10, 2026269 ms
Oct 17, 2026269 ms
Oct 24, 2026253 ms
Oct 31, 2026244 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of istyle.iq (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. istyle.iq at 0.4 s0.4 s
  2. istyle.iq at 0.8 s0.8 s
  3. istyle.iq at 1.1 s1.1 s
  4. istyle.iq at 1.5 s1.5 s
  5. istyle.iq at 1.9 s1.9 s
  6. istyle.iq at 2.3 s2.3 s
  7. istyle.iq at 2.6 s2.6 s
  8. istyle.iq at 3.0 s3.0 s

Speed

6 to fix69
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 69

    69/100

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

  • Reduce unused JavaScript

    369 KiB

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

  • Reduce unused CSS

    300 ms · 39 KiB

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

  • 2,027 HTML elements

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

  • Google Tag Manager adds 163 ms

    163 ms

    Google Tag Manager costs a phone 163 ms of main-thread work and 333 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Adobe Tag Manager and Shopify and others), adding 705 KiB and 299 ms of main-thread time.

  • Use efficient cache lifetimes

    124 KiB

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

  • 4 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Improve image delivery

    11 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Legacy JavaScript

    4 KiB

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 778 ms of it running JavaScript. That is comfortably low.

  • Server response: 22 ms

    22 ms

    Your server sent the HTML in 22 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 7.2 s

    7.2 s

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

  • Time to Interactive: 15.0 s

    15.0 s

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

  • Real-user INP: 272 ms

    272 ms

    Real visitors wait 272 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Largest content (LCP) got 44% slower for real visitors

    +44%

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

  • Speed Index: 4.0 s

    4.0 s

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

  • Cumulative Layout Shift: 0.124

    0.124

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

6 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 595 ms

    595 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 82 ms

    82 ms

    Scripts block the page for only 82 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 3.0 MB in 244 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 244 requests on a phone: scripts 1.1 MB (62), other files 829 KiB (99) and fonts 556 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.84 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.84 g of CO₂e: 100.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9695
  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • 3 text elements with low contrast

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

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 44 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 3 links crawlers can't follow

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

  • 38 internal links, 25 external

    The homepage links to 38 pages on istyle.iq and 25 external pages.

8 checks passed
  • Meta description: 110 characters

    Your meta description is 110 characters: “ماك، iPhone، آيباد، وأفضل الإكسسوارات مع توصيل مجاني أو استلام من المتجر. iSTYLE، الشريك المميز لأبل في العراق”.

  • One H1 headline

    Your main headline reads: “iSTYLE شريك أبل المميز، العراق”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “iSTYLE شريك أبل المميز، العراق – iSTYLE Iraq”.

  • Canonical URL set

    The canonical URL is https://istyle.iq/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://istyle.iq/sitemap.xml.

AI search readiness

100
3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • llms.txt published

    The site publishes https://istyle.iq/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 10 pages without a meta description

    https://istyle.iq/pages/delivery-information, https://istyle.iq/pages/store-locator, https://istyle.iq/blogs/istyle-blogs, https://istyle.iq/pages/view-all-mac, https://istyle.iq/pages/view-all-iphone and https://istyle.iq/pages/view-all-ipad and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://istyle.iq/pages/delivery-information, whose canonical is https://istyle.iq/policies/terms-of-service. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages with very little text

    https://istyle.iq/pages/store-locator and https://istyle.iq/pages/view-all-tv-home have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 4688
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) SecurityError: Failed to execute 'open' on 'IDBFactory': access to the Indexed Database API is de…”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    44 of 50 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No call to action on the first screen

    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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

  • Only about 95 words

    The homepage has only about 95 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

3 checks passed
  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta 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.

  • 15 cookies set on arrival

    15

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

  • No consent tool detected

    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.

  • 26 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at istyle.iq, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

T Lab Ai Translate · Seowill Redirects · Bloggo Blog Search Bar · Back In Stock

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on istyle.iq, including 14 speed issues, 1 SEO issue and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25