Website review, no card needed
idealworld.tv website review
Visit site (opens in a new tab)Reviewed 17 November 202644 issues · 88 checks
This review found 44 issues worth fixing on idealworld.tv, 9 of them high impact, across 88 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
75C- #81,277 of 124,166 reviewed websitesbeats 30%
- #51,566 of 69,801 online storesbeats 22%
- #48,656 of 63,483 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 3.0 s |
| Nov 7, 2026 | 3.0 s |
| Nov 14, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 332 ms |
| Jun 6, 2026 | 382 ms |
| Jun 13, 2026 | 403 ms |
| Jun 20, 2026 | 412 ms |
| Jun 27, 2026 | 420 ms |
| Jul 4, 2026 | 430 ms |
| Jul 11, 2026 | 446 ms |
| Jul 18, 2026 | 462 ms |
| Jul 25, 2026 | 472 ms |
| Aug 1, 2026 | 479 ms |
| Aug 8, 2026 | 487 ms |
| Aug 15, 2026 | 488 ms |
| Aug 22, 2026 | 493 ms |
| Aug 29, 2026 | 491 ms |
| Sep 5, 2026 | 453 ms |
| Sep 12, 2026 | 412 ms |
| Sep 19, 2026 | 375 ms |
| Sep 26, 2026 | 361 ms |
| Oct 3, 2026 | 370 ms |
| Oct 10, 2026 | 386 ms |
| Oct 17, 2026 | 404 ms |
| Oct 24, 2026 | 407 ms |
| Oct 31, 2026 | 415 ms |
| Nov 7, 2026 | 421 ms |
| Nov 14, 2026 | 426 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
How it loaded on a phone
1.1 s
2.1 s
3.2 s
4.3 s
5.3 s
6.4 s
7.4 s
8.5 s
Speed
Render-blocking requests
1.3 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and PayPal and others), adding 1.5 MB and 949 ms of main-thread time.
Mobile performance score: 76
76/100Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 363 KiBAbout 363 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 355 KiB23 files are served with short cache lifetimes, so returning visitors download them again (355 KiB).
Shopify adds 352 ms
352 msShopify costs a phone 352 ms of main-thread work and 668 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.
Reduce unused CSS
300 ms · 65 KiBAbout 65 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.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 266 ms
266 msGoogle Tag Manager costs a phone 266 ms of main-thread work and 340 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.
PayPal adds 176 ms
176 msPayPal costs a phone 176 ms of main-thread work and 311 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.
1,582 HTML elements
The page has 1,582 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 175 ms. During a long task the page ignores taps.
Improve image delivery
63 KiB5 images could be 63 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
57 KiBPolyfills for old browsers add 57 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
21 KiB21 KiB could be saved by minifying JavaScript.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 57 ms
57 msYour server sent the HTML in 57 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 18.8 s
18.8 sThe page becomes fully interactive after 18.8 s. Good is under 3.8 s.
Largest Contentful Paint: 5.5 s
5.5 sYour largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Promotional image”.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 398 ms
398 msReal visitors wait 398 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 4.0 s
4.0 sVisually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 332 ms to 426 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Total Blocking Time: 158 ms
158 msScripts block the page for only 158 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 3.3 MB in 292 requests
3.3 MBYour homepage downloads 3.3 MB in 292 requests on a phone: scripts 2.0 MB (157), images 590 KiB (47) and other files 371 KiB (52). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
BF-13-11-HP-Banner-M.gif 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 in older formats
1 image (33 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.
About 0.9 g of CO₂ per visit
0.94 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.94 g of CO₂e: 113.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (4 elements)
Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (10 characters)
Your title is only 10 characters: “Idealworld”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
221 internal links, 1 external
The homepage links to 221 pages on idealworld.tv and 1 external page.
4 checks passed
One H1 headline
Your main headline reads: “Idealworld”.
Canonical URL set
The canonical URL is https://www.idealworld.tv/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.idealworld.tv/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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.
Text is in the HTML
Your server sends the page's text in the HTML (506 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.idealworld.tv/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
9 pages without a meta description
https://www.idealworld.tv/pages/rewards, https://www.idealworld.tv/pages/about-us, https://www.idealworld.tv/pages/terms-and-conditions, https://www.idealworld.tv/pages/livetv, https://www.idealworld.tv/pages/missed-auctions and https://www.idealworld.tv/collections/black-friday-deals and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
9 links to non-canonical URLs
Your homepage links to 9 pages by a URL that isn't their canonical one, for example https://www.idealworld.tv/pages/rewards, whose canonical is https://www.idealworld.tv/rewards. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
14 pages without an H1
https://www.idealworld.tv/pages/rewards, https://www.idealworld.tv/pages/delivery-information, https://www.idealworld.tv/pages/returns, https://www.idealworld.tv/pages/about-us, https://www.idealworld.tv/pages/privacy-policy and https://www.idealworld.tv/pages/faq and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages with very little text
https://www.idealworld.tv/pages/rewards, https://www.idealworld.tv/pages/delivery-information, https://www.idealworld.tv/pages/returns, https://www.idealworld.tv/pages/about-us, https://www.idealworld.tv/pages/terms-and-conditions and https://www.idealworld.tv/pages/privacy-policy and 9 others 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.
1 page slow to respond
https://www.idealworld.tv/collections/accessories-beauty took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 181 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
40 of 46 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 21 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 309 words of copy
The homepage carries about 309 words of visible text.
4 checks passed
12 calls to action
The homepage has 12 calls to action, for example “Shop All Beauty”, “Shop All Fashion” and “Shop All Home & Garden”.
11 short forms
11 short forms (4 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Klaviyo (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
15Opening the homepage sets 15 cookies, 1 of them by other companies (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.
13 other companies contacted
Loading the homepage contacts 13 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 idealworld.tv, 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 17 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Kaching Bundles · Yotpo Product Reviews · Yotpo Loyalty Rewards · Elevate Ab Testing · Attentive · Iw Prod Badge Manager · Klip Coupons · Iw Wishlist Prod · Rebuy Personalization Engine · Microsoft Clarity · Klaviyo Email Marketing Sms · Prefixbox · rebuyengine.com · bogos.io · cloudfront.net · magefan.top · creativecdn.com
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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Founded
- 2000
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on idealworld.tv, including 19 speed issues, 4 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.