Website review, no card needed
inviz.tv website review
Visit site (opens in a new tab)Reviewed 10 November 202629 issues · 74 checks
This review found 29 issues worth fixing on inviz.tv, 7 of them high impact, across 74 checks. The most urgent: page weight: 16.1 MB in 192 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
91A- #1,326 of 102,811 reviewed websitesbeats 98%
- #594 of 57,181 online storesbeats 98%
- #568 of 52,022 Shopify storesbeats 98%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 5.6 s |
| May 30, 2026 | 5.6 s |
| Jun 6, 2026 | 5.0 s |
| Jun 13, 2026 | 5.2 s |
| Jun 20, 2026 | 5.5 s |
| Jun 27, 2026 | 5.4 s |
| Jul 4, 2026 | 5.4 s |
| Jul 11, 2026 | 4.9 s |
| Jul 18, 2026 | 4.5 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 4.0 s |
| Aug 22, 2026 | 4.5 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 5.3 s |
| Sep 12, 2026 | 5.5 s |
| Sep 19, 2026 | 5.4 s |
| Sep 26, 2026 | 4.9 s |
| Oct 3, 2026 | 4.8 s |
| Oct 10, 2026 | 4.7 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 4.9 s |
| Oct 31, 2026 | 4.8 s |
| Nov 7, 2026 | 4.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 112 ms |
| May 30, 2026 | 109 ms |
| Jun 6, 2026 | 119 ms |
| Jun 13, 2026 | 119 ms |
| Jun 20, 2026 | 128 ms |
| Jun 27, 2026 | 148 ms |
| Jul 4, 2026 | 141 ms |
| Jul 11, 2026 | 138 ms |
| Aug 15, 2026 | 117 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 153 ms |
| Sep 5, 2026 | 159 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
Speed
Improve image delivery
881 KiB18 images could be 881 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
499 KiBAbout 499 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
466 KiB11 files are served with short cache lifetimes, so returning visitors download them again (466 KiB).
Render-blocking requests
300 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
2,265 HTML elements
The page has 2,265 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
bitmovin.com adds 137 ms
137 msbitmovin.com costs a phone 137 ms of main-thread work and 599 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 (bitmovin.com, Klaviyo and Google CDN and others), adding 985 KiB and 308 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 164 ms. During a long task the page ignores taps.
Reduce unused CSS
38 KiBAbout 38 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need.
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.
3 checks passed
Mobile performance score: 90
90/100Your mobile performance score is 90. That is in Google's “good” band (90 and up).
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 484 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 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.
Real-user FCP: 5.6 s
5.6 sReal visitors see the first content after 5.6 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 10.1 s
10.1 sThe page becomes fully interactive after 10.1 s. Good is under 3.8 s.
Tap response (INP) got 41% slower for real visitors
+41%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 112 ms to 159 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
5 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 5.6 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.5 s
2.5 sYour largest element renders in 2.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Bundle Your Content.”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 57 ms
57 msScripts block the page for only 57 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 16.1 MB in 192 requests
16.1 MBYour homepage downloads 16.1 MB in 192 requests on a phone: media 13.1 MB (1), scripts 1.1 MB (67) and images 1.1 MB (24). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
18 KiB3 images are downloaded at several times the size a phone draws them, for example SKIBIDI_LOGO-16.png at 389 px wide, shown at 124 px. Resized copies would save about 18 KiB.
About 4.6 g of CO₂ per visit
4.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.57 g of CO₂e: 548.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h1 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (5 characters)
Your title is only 5 characters: “INVIZ”. Between 30 and 65 characters leaves room to say what you do and for whom.
19 links crawlers can't follow
19 links have no real href, so search engines can't follow them.
18 internal links, 6 external
The homepage links to 18 pages on inviz.tv and 6 external pages.
7 checks passed
Meta description: 130 characters
Your meta description is 130 characters: “INVIZ is an entertainment and shopping marketplace that bundles Creators’ biggest content events with exclusive merchan…”.
One H1 headline
Your main headline reads: “INVIZ”.
Canonical URL set
The canonical URL is https://inviz.tv/.
Structured data in place
Structured data found: BreadcrumbList, 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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://inviz.tv/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (968 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://inviz.tv/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://inviz.tv/policies/privacy-policy has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://inviz.tv/pages/contact has no <h1> headline, so visitors and search engines get no clear main topic.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
2 pages of 9 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 2 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
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.
About 347 words of copy
The homepage carries about 347 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more” and “SCHEDULE A DEMO”.
7 calls to action
The homepage has 7 calls to action, for example “Contact”, “SCHEDULE A DEMO” and “CONTACT”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
21 other companies contacted
Loading the homepage contacts 21 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 inviz.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · Accessibly App · printful.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
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Bengaluru
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 inviz.tv, including 12 speed issues, 2 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.