Website review, no card needed

metrohealthdc.org logo

metrohealthdc.org website review

Visit site (opens in a new tab)Reviewed 19 November 202640 issues · 79 checks

This review found 40 issues worth fixing on metrohealthdc.org, 20 of them high impact, across 79 checks. The most urgent: improve image delivery. 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

Full-page screenshot of metrohealthdc.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. metrohealthdc.org at 0.5 s0.5 s
  2. metrohealthdc.org at 1.0 s1.0 s
  3. metrohealthdc.org at 1.5 s1.5 s
  4. metrohealthdc.org at 2.0 s2.0 s
  5. metrohealthdc.org at 2.4 s2.4 s
  6. metrohealthdc.org at 2.9 s2.9 s
  7. metrohealthdc.org at 3.4 s3.4 s
  8. metrohealthdc.org at 3.9 s3.9 s

Speed

9 to fix38
  • Improve image delivery

    10.9 s · 4.0 MB

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

  • Reduce unused JavaScript

    2.2 s · 380 KiB

    About 380 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.

  • Mobile performance score: 38

    38/100

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

  • 3,442 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Unpkg and byted-static.com and others), adding 9.7 MB and 324 ms of main-thread time.

  • lightshot.app adds 0 ms

    0 ms

    lightshot.app costs a phone 0 ms of main-thread work and 8.9 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.

  • Render-blocking requests

    900 ms

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

  • Legacy JavaScript

    300 ms · 36 KiB

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

  • Google Tag Manager adds 274 ms

    274 ms

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

  • 6 long tasks on the main thread

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

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    3 KiB

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

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

2 checks passed
  • Main-thread work: 1.4 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

6 to fix35
  • Largest Contentful Paint: 50.5 s

    50.5 s

    Your largest element takes 50.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “HIỆP 2: 90' Champions League Nữ 09:45 19/11 Áo Vienna phụ n…”.

  • Time to Interactive: 51.5 s

    51.5 s

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

  • Cumulative Layout Shift: 0.707

    0.707

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

  • Speed Index: 7.2 s

    7.2 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • 18 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Total Blocking Time: 73 ms

    73 ms

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

Images and page weight

2 to fix60
  • Page weight: 14.2 MB in 278 requests

    14.2 MB

    Your homepage downloads 14.2 MB in 278 requests on a phone: images 13.2 MB (253), scripts 871 KiB (12) and stylesheets 66 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    42 KiB

    1 image is downloaded at several times the size a phone draws it, for example logo.png at 620 px wide, shown at 120 px. Resized copies would save about 42 KiB.

  • 1 image in older formats

    1 image (64 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 4.0 g of CO₂ per visit

    4.01 g

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

1 checks passed
  • Images load when needed

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

Accessibility

9 to fixGoogle 7585
  • 3 tap targets too small

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

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 7 images without alt text

    7 images have no alt text, which hurts accessibility and image search.

  • 103 links without text

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

  • Alternative text of images should not be repeated as text (107 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.

1 checks passed
  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 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

2 to fixGoogle 9295
  • No XML sitemap

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 22 internal links, 8 external

    The homepage links to 22 pages on metrohealthdc.org and 8 external pages.

7 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “ColaTV phát trực tiếp bóng đá chất lượng cao, không giật lag. Xem bóng đá trực tuyến miễn phí tại Cola TV cùng đội ngũ …”.

  • One H1 headline

    Your main headline reads: “COLATV TRỰC TIẾP BÓNG ĐÁ MIỄN PHÍ - XEM TTBD HD 90 PHÚT”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Cola TV - Trực Tiếp Bóng đá World Cup 2026 - Xem TTBD HD”.

  • Canonical URL set

    The canonical URL is https://colatv9vn.tv/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing url, 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.

  • No llms.txt

    There is no https://colatv9vn.tv/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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (9,422 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix71
  • 2 pages point its canonical at the homepage

    https://colatv9vn.tv/ket-qua-bong-da and https://colatv9vn.tv/nhan-dinh declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 3 pages share a title

    /, https://colatv9vn.tv/ket-qua-bong-da and https://colatv9vn.tv/nhan-dinh all use the title “Cola TV - Trực Tiếp Bóng đá World Cup 2026 - Xem TTBD HD”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://colatv9vn.tv/nhan-dinh-tran-dau has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://colatv9vn.tv/ket-qua-bong-da and https://colatv9vn.tv/nhan-dinh use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://colatv9vn.tv/category/tin-bong-da has no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 internal pages checked

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

3 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 5 broken images

    5 images failed to load on a phone, for example https://cdn.colatv9vn.tv/wp-content/wp-content/uploads/2025/07/ball_icon.webp.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    30 of 36 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix40
  • 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.

  • No form on the homepage

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

  • 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 10,887 words of copy

    The homepage carries about 10,887 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

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

  • 14 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on metrohealthdc.org, including 15 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

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