Website review, no card needed
51cg1.com website review
Visit site (opens in a new tab)Reviewed 11 October 202632 issues · 77 checks
This review found 32 issues worth fixing on 51cg1.com, 14 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 829 ms |
| Apr 25, 2026 | 847 ms |
| May 2, 2026 | 868 ms |
| May 9, 2026 | 879 ms |
| May 16, 2026 | 890 ms |
| May 23, 2026 | 899 ms |
| May 30, 2026 | 899 ms |
| Jun 6, 2026 | 909 ms |
| Jun 13, 2026 | 912 ms |
| Jun 20, 2026 | 906 ms |
| Jun 27, 2026 | 903 ms |
| Jul 4, 2026 | 888 ms |
| Jul 11, 2026 | 879 ms |
| Jul 18, 2026 | 880 ms |
| Jul 25, 2026 | 883 ms |
| Aug 1, 2026 | 890 ms |
| Aug 8, 2026 | 894 ms |
| Aug 15, 2026 | 897 ms |
| Aug 22, 2026 | 903 ms |
| Aug 29, 2026 | 905 ms |
| Sep 5, 2026 | 908 ms |
| Sep 12, 2026 | 912 ms |
| Sep 19, 2026 | 908 ms |
| Sep 26, 2026 | 908 ms |
| Oct 3, 2026 | 897 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 95 ms |
| Apr 25, 2026 | 96 ms |
| May 2, 2026 | 97 ms |
| May 9, 2026 | 97 ms |
| May 16, 2026 | 99 ms |
| May 23, 2026 | 102 ms |
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 103 ms |
| Jun 20, 2026 | 101 ms |
| Jun 27, 2026 | 101 ms |
| Jul 4, 2026 | 100 ms |
| Jul 11, 2026 | 101 ms |
| Jul 18, 2026 | 102 ms |
| Jul 25, 2026 | 103 ms |
| Aug 1, 2026 | 103 ms |
| Aug 8, 2026 | 103 ms |
| Aug 15, 2026 | 102 ms |
| Aug 22, 2026 | 102 ms |
| Aug 29, 2026 | 102 ms |
| Sep 5, 2026 | 101 ms |
| Sep 12, 2026 | 100 ms |
| Sep 19, 2026 | 98 ms |
| Sep 26, 2026 | 98 ms |
| Oct 3, 2026 | 97 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
Use efficient cache lifetimes
63.5 s · 17.6 MB63 files are served with short cache lifetimes, so returning visitors download them again (17.6 MB).
Render-blocking requests
59.1 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 59.1 s.
Reduce unused JavaScript
2.1 s · 568 KiBAbout 568 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Main-thread work: 8.5 s
A phone's processor spends 8.5 s on main-thread work while loading, 5.7 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, Yandex Metrica and gyezbp.cn and others), adding 16.1 MB and 209 ms of main-thread time.
gyezbp.cn adds 28 ms
28 msgyezbp.cn costs a phone 28 ms of main-thread work and 15.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.
Mobile performance score: 53
53/100Your mobile performance score is 53 (desktop: 20). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 84 KiBAbout 84 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Minify JavaScript
300 ms · 57 KiB57 KiB could be saved by minifying JavaScript.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 254 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 13 KiB13 KiB could be saved by minifying CSS.
Improve image delivery
150 ms · 5 KiB1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. 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: 72 ms
72 msYour server sent the HTML in 72 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 60.7 s
60.7 sThe first text or image appears after 60.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 139.4 s
139.4 sYour largest element takes 139.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 60.7 s
60.7 sVisually, the page fills in at 60.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 150.5 s
150.5 sThe page becomes fully interactive after 150.5 s. Good is under 3.8 s.
31 images without width and height
31 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 95 ms to 97 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 125 ms
125 msReal visitors wait 125 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 574 ms
574 msReal visitors wait 574 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 160 ms
160 msScripts block the page for only 160 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.016
0.016The layout barely moves while loading (CLS 0.016, good is under 0.1).
Images and page weight
Page weight: 33.8 MB in 174 requests
33.8 MBYour homepage downloads 33.8 MB in 174 requests on a phone: fonts 16.6 MB (4), other files 15.9 MB (109) and scripts 1.0 MB (19). Under 2 MB keeps phones on slow connections fast.
About 9.6 g of CO₂ per visit
9.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 9.57 g of CO₂e: 1148.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
17 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 18 WCAG 2.2 A/AA and best-practice rules on the phone render: 17 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (29 characters)
Your title is only 29 characters: “51吃瓜网 - 今日吃瓜爆料资讯平台,热门黑料内幕每日更新”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
140 internal links, 64 external
The homepage links to 140 pages on 51cg1.com and 64 external pages.
7 checks passed
Meta description: 122 characters
Your meta description is 122 characters: “51吃瓜网(51cg1.com)吃瓜爆料第一站,全网更新最快最全的吃瓜官网,专注网红黑料、明星八卦与社会热点。每日实时推送最新吃瓜资讯,覆盖热门黑料事件与独家爆料合集,让用户第一时间掌握全网大瓜,获取全面的吃瓜黑料信息,尽享最新爆料与吃瓜…”.
One H1 headline
Your main headline reads: “51吃瓜网 - 全网更新最快最全的吃瓜网”.
Canonical URL set
The canonical URL is https://51cg1.com/.
Structured data in place
Structured data found: CollectionPage 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://51cg1.com/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.
No llms.txt
There is no https://51cg1.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.
1 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.
Other pages
1 page without a title
https://51cg1.com/qun.html has no <title>, so Google invents the link text in results.
2 pages without a meta description
https://51cg1.com/qun.html and https://51cg1.com/telegram.html have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://51cg1.com/qun.html and https://51cg1.com/telegram.html have no <h1> headline, so visitors and search engines get no clear main topic.
11 pages with very little text
https://51cg1.com/search-page.html, https://51cg1.com/github.html, https://51cg1.com/telegram.html, https://51cg1.com/category/wpcz, https://51cg1.com/category/xsxy and https://51cg1.com/category/whhl and 5 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 78 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.
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.
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_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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.
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.
Only about 3 words
The homepage has only about 3 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Yandex Metrica (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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
12 other companies contacted
Loading the homepage contacts 12 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 51cg1.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
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on 51cg1.com, including 16 speed issues, 2 SEO issues and 4 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.