Website review, no card needed

mytvsuper.com logo

mytvsuper.com website review

Visit site (opens in a new tab)Reviewed 24 October 202653 issues · 93 checks

This review found 53 issues worth fixing on mytvsuper.com, 27 of them high impact, across 93 checks. The most urgent: use efficient cache lifetimes. 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.4 s2.7 sMay 2Oct 173.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.7 s
May 9, 20263.6 s
May 16, 20263.5 s
May 23, 20263.4 s
May 30, 20263.4 s
Jun 6, 20263.2 s
Jun 13, 20263.0 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20263.0 s
Jul 18, 20263.1 s
Jul 25, 20263.3 s
Aug 1, 20263.5 s
Aug 8, 20263.4 s
Aug 15, 20263.4 s
Aug 22, 20263.4 s
Aug 29, 20263.5 s
Sep 5, 20264.1 s
Sep 12, 20264.2 s
Sep 19, 20264.1 s
Sep 26, 20263.8 s
Oct 3, 20263.3 s
Oct 10, 20263.2 s
Oct 17, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
239 ms133 msMay 2Oct 17145 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026172 ms
May 9, 2026171 ms
May 16, 2026170 ms
May 23, 2026169 ms
May 30, 2026170 ms
Jun 6, 2026166 ms
Jun 13, 2026161 ms
Jun 20, 2026159 ms
Jun 27, 2026159 ms
Jul 4, 2026156 ms
Jul 11, 2026154 ms
Jul 18, 2026155 ms
Jul 25, 2026159 ms
Aug 1, 2026162 ms
Aug 8, 2026161 ms
Aug 15, 2026163 ms
Aug 22, 2026168 ms
Aug 29, 2026180 ms
Sep 5, 2026219 ms
Sep 12, 2026227 ms
Sep 19, 2026218 ms
Sep 26, 2026186 ms
Oct 3, 2026163 ms
Oct 10, 2026154 ms
Oct 17, 2026145 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 mytvsuper.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mytvsuper.com at 1.6 s1.6 s
  2. mytvsuper.com at 3.1 s3.1 s
  3. mytvsuper.com at 4.7 s4.7 s
  4. mytvsuper.com at 6.2 s6.2 s
  5. mytvsuper.com at 7.8 s7.8 s
  6. mytvsuper.com at 9.3 s9.3 s
  7. mytvsuper.com at 10.9 s10.9 s
  8. mytvsuper.com at 12.4 s12.4 s

Speed

14 to fix32
  • Use efficient cache lifetimes

    15.6 s · 6.5 MB

    173 files are served with short cache lifetimes, so returning visitors download them again (6.5 MB).

  • Reduce unused JavaScript

    11.1 s · 2.0 MB

    About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.1 s faster on a phone.

  • Improve image delivery

    9.0 s · 1.9 MB

    4 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.0 s faster on a phone.

  • Render-blocking requests

    6.2 s

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

  • Reduce unused CSS

    1.1 s · 73 KiB

    About 73 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 32

    32/100

    Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 8.0 MB and 1.7 s of main-thread time.

  • Google Tag Manager adds 945 ms

    945 ms

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

  • tvb.com adds 48 ms

    48 ms

    tvb.com costs a phone 48 ms of main-thread work and 5.6 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.

  • 20 long tasks on the main thread

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

  • Facebook adds 239 ms

    239 ms

    Facebook costs a phone 239 ms of main-thread work and 314 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.

  • Google/Doubleclick Ads adds 233 ms

    233 ms

    Google/Doubleclick Ads costs a phone 233 ms of main-thread work and 326 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.

  • 2,403 HTML elements

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

  • Legacy JavaScript

    150 ms · 53 KiB

    Polyfills for old browsers add 53 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Duplicated JavaScript

    150 ms · 10 KiB

    10 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • 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: 484 ms

    484 ms

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

Core Web Vitals

11 to fix0
  • 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 LCP: 8.0 s

    8.0 s

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

  • Real-user INP: 852 ms

    852 ms

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • First Contentful Paint: 12.2 s

    12.2 s

    The first text or image appears after 12.2 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 99.3 s

    99.3 s

    Your largest element takes 99.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “這一秒過火 (33集原裝雙語版)”.

  • Speed Index: 29.9 s

    29.9 s

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

  • Time to Interactive: 101.2 s

    101.2 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

    Scripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.

  • Real-user CLS: 0.18

    0.18

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

3 checks passed
  • Tap response (INP) got 13% faster for real visitors

    -13%

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • Cumulative Layout Shift: 0.056

    0.056

    The layout barely moves while loading (CLS 0.056, good is under 0.1).

Images and page weight

3 to fix50
  • Page weight: 23.8 MB in 427 requests

    23.8 MB

    Your homepage downloads 23.8 MB in 427 requests on a phone: images 12.6 MB (197), fonts 5.1 MB (19) and scripts 4.5 MB (93). Under 2 MB keeps phones on slow connections fast.

  • 40 images in older formats

    40 images (2.7 MB) 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.

  • 6 images far larger than shown

    159 KiB

    6 images are downloaded at several times the size a phone draws them, for example 1786007604898877_146867.jpeg at 324 px wide, shown at 92 px. Resized copies would save about 159 KiB.

  • 3 images below the first screen load straight away

    3 images further down the page (112 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.7 g of CO₂ per visit

    6.73 g

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

Accessibility

8 to fixGoogle 8388
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 7 tap targets too small

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

  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

  • [role="img"] and [role="image"] elements must have alternative text (1 element)

    [role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • Page should contain a level-one heading (1 element)

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

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

  • 3 links without text

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

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

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

2 to fixGoogle 10083
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (18 characters)

    Your title is only 18 characters: “myTV SUPER: 熱播節目推介”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 5 internal links, 9 external

    The homepage links to 5 pages on mytvsuper.com and 9 external pages.

6 checks passed
  • Meta description: 85 characters

    Your meta description is 85 characters: “探索myTV SUPER網頁版極致娛樂!免費區線上看TVB劇集及綜藝娛樂節目重溫、電視直播、節目表、中外電影猛片、賽馬一應俱全,升級myTV Gold享受更多功能和體驗!”.

  • Canonical URL set

    The canonical URL is https://www.mytvsuper.com/tc/home/.

  • 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://www.mytvsuper.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.mytvsuper.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.

2 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: 6 of 6 facts

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

Other pages

1 to fix95
  • 2 pages without an H1

    https://www.mytvsuper.com/sc/home and https://www.mytvsuper.com/en/home have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.mytvsuper.com/sc/home and https://www.mytvsuper.com/en/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.

  • 2 internal pages checked

    We fetched 2 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 2 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 2 pages that loaded have a meta description.

  • 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 to fixGoogle 5469
  • 1 broken image

    1 image failed to load on a phone, for example https://www.mytvsuper.com/tc/home/#.

  • 55 small tap targets

    55 of 89 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 third-party cookies

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

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“The Topics API is deprecated and will be removed in a future release.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'addEventListener')”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

8 to fix31
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

  • Only about 54 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 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.

  • 48 other companies contacted

    Loading the homepage contacts 48 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 mytvsuper.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Google Cloud

Company

Founded
2016
Headquarters
TVB (headquarters)

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on mytvsuper.com, including 25 speed issues, 2 SEO issues and 8 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