cctv.com website review

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

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

The page goes through 1 redirect before it starts loading, costing about 845 ms. Link and advertise the final URL directly.

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

14 images could be 310 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

5 third-party services load with your homepage (cctvpic.com, alicdn.com and Tencent and others), adding 1.0 MB and 164 ms of main-thread time.

cctvpic.com costs a phone 153 ms of main-thread work and 1.0 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.

The HTML itself could arrive about 200 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

About 41 KiB of CSS is downloaded but never applied on this page.

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying JavaScript.

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 visitors wait 5.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

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

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

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

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Some list items are not inside a list.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

<td> elements in a large <table> do not have table headers. (1 element).

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

Your title is only 10 characters: “央视网_世界就在眼前”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No XML sitemap at https://www.cctv.com/sitemap.xml, so Google discovers your pages only by following links.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 16 pages on cctv.com and 1,159 external pages.

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.

/special/guanyunew/PAGE13818868795101874/index.shtml and /special/guanyunew/PAGE13818868795101879/index.shtml all use the title “央视网”. Search engines can't tell which page to show for a search, so each competes with the others.

/special/guanyunew/gongsijianjie/index.shtml and /special/guanyunew/jianjiePAGEQezAEWqHSGGmjjQL6s0V231214/index.shtml use the same meta description. A description written for each page earns more clicks.

/culture/index.shtml, /gyys/index.shtml, /special/guanyunew/gongsijianjie/index.shtml, /special/guanyunew/PAGE13818868795101874/index.shtml and /special/guanyunew/PAGE13818868795101879/index.shtml have no <h1> headline, so visitors and search engines get no clear main topic.

/culture/index.shtml, /2026/10/30/ARTI97lo9WcC4jAqOwcm1NRk261030.shtml, /2026/10/30/ARTIRhCnqAO44iyMsMyYhN1m261030.shtml, /2026/10/30/ARTIXPJf1Z3DYkIn5V0gYZq5261030.shtml, /gyys/index.shtml and /special/guanyunew/gongsijianjie/index.shtml and 3 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.

/culture/index.shtml, /2026/10/30/ARTI97lo9WcC4jAqOwcm1NRk261030.shtml and /2026/10/30/ARTIRhCnqAO44iyMsMyYhN1m261030.shtml took over 3 s to send their HTML from our server.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

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

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

Your certificate from GlobalSign nv-sa · GlobalSign RSA OV SSL CA 2018 expires in 4 days. If it doesn't renew automatically, visitors get a security warning.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

cctv.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

cctv.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

cctv.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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.

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