Website review, no card needed

52shuku.net logo

52shuku.net website review

Visit site (opens in a new tab)Reviewed 11 October 202630 issues · 73 checks

This review found 30 issues worth fixing on 52shuku.net, 8 of them high impact, across 73 checks. The most urgent: 147 text elements with low contrast. 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
1.1 s538 msApr 18Oct 3597 ms
Show as table
DateReal-visitor load time (LCP)
Apr 18, 2026828 ms
Apr 25, 2026779 ms
May 2, 2026760 ms
May 9, 2026764 ms
May 16, 2026775 ms
May 23, 2026775 ms
May 30, 2026778 ms
Jun 6, 2026779 ms
Jun 13, 2026788 ms
Jun 20, 2026795 ms
Jun 27, 2026813 ms
Jul 4, 2026831 ms
Jul 11, 2026844 ms
Jul 18, 2026884 ms
Jul 25, 2026907 ms
Aug 1, 2026947 ms
Aug 8, 2026983 ms
Aug 15, 2026990 ms
Aug 22, 2026993 ms
Aug 29, 2026970 ms
Sep 5, 2026954 ms
Sep 12, 2026954 ms
Sep 19, 2026878 ms
Sep 26, 2026735 ms
Oct 3, 2026597 ms
Real-visitor tap response (INP)75th percentile, phones
125 ms72 msApr 18Oct 378 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 202679 ms
Apr 25, 202680 ms
May 2, 202681 ms
May 9, 202683 ms
May 16, 202684 ms
May 23, 202684 ms
May 30, 202685 ms
Jun 6, 202689 ms
Jun 13, 202694 ms
Jun 20, 2026102 ms
Jun 27, 2026107 ms
Jul 4, 2026110 ms
Jul 11, 2026105 ms
Jul 18, 2026104 ms
Jul 25, 2026106 ms
Aug 1, 2026108 ms
Aug 8, 2026113 ms
Aug 15, 2026116 ms
Aug 22, 2026116 ms
Aug 29, 2026116 ms
Sep 5, 2026118 ms
Sep 12, 2026119 ms
Sep 19, 2026112 ms
Sep 26, 202694 ms
Oct 3, 202678 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 52shuku.net (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 52shuku.net at 0.4 s0.4 s
  2. 52shuku.net at 0.8 s0.8 s
  3. 52shuku.net at 1.1 s1.1 s
  4. 52shuku.net at 1.5 s1.5 s
  5. 52shuku.net at 1.9 s1.9 s
  6. 52shuku.net at 2.3 s2.3 s
  7. 52shuku.net at 2.6 s2.6 s
  8. 52shuku.net at 3.0 s3.0 s

Speed

4 to fix82
  • Mobile performance score: 82

    82/100

    Your mobile performance score is 82 (desktop: 100). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    700 ms

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

  • Reduce unused JavaScript

    300 ms · 73 KiB

    About 73 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Use efficient cache lifetimes

    300 ms · 46 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google Analytics), adding 189 KiB and 185 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.6 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 4.5 s

    4.5 s

    Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GL百合小说:现代百合 古代百合 甜宠文 年代文 欢喜冤家 查看更多”.

  • Time to Interactive: 4.5 s

    4.5 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Tap response (INP) held steady for real visitors

    +8%

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

10 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: 0.6 s

    0.6 s

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

  • Real-user INP: 74 ms

    74 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.6 s

    0.6 s

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

  • Real-user TTFB: 229 ms

    229 ms

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

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

    -17%

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

  • Speed Index: 2.5 s

    2.5 s

    Visually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 109 ms

    109 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.08 g of CO₂ per visit

    0.08 g

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

1 checks passed
  • Page weight: 302 KiB in 9 requests

    302 KiB

    Your homepage downloads 302 KiB in 9 requests on a phone: scripts 201 KiB (3), fonts 76 KiB (1) and stylesheets 15 KiB (2). That is a lean page.

Accessibility

6 to fixGoogle 8989
  • 147 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • All page content should be contained by landmarks (28 elements)

    All page content should be contained by landmarks: 28 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

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

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 32 automated accessibility rules passed

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

SEO

5 to fixGoogle 10074
  • No H1 headline

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

  • Title is short (23 characters)

    Your title is only 23 characters: “52书库_好看的小说推荐_热门全本小说在线阅读”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 226 internal links, 0 external

    The homepage links to 226 pages on 52shuku.net and 0 external pages.

4 checks passed
  • Meta description: 94 characters

    Your meta description is 94 characters: “52书库(www.52shuku.net)分享各类好看的耽美小说,言情小说,GL百合小说等等,覆盖了穿书,甜宠,追妻,仙侠等等类型,均为全本完结的精彩小说,欢迎前来在线阅读,无弹窗广告哦~”.

  • Canonical URL set

    The canonical URL is https://www.52shuku.net/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.52shuku.net/sitemap.xml.

AI search readiness

1 to fix83
  • 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://www.52shuku.net/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

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://www.52shuku.net/e/member/fava, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 5 pages without a meta description

    https://www.52shuku.net/bookcase.html, https://www.52shuku.net/zuozhe/daquan.html, https://www.52shuku.net/nan, https://www.52shuku.net/ZhiNan.html and https://www.52shuku.net/tuijian/shuoming.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://www.52shuku.net/bookcase.html, https://www.52shuku.net/tuijian, https://www.52shuku.net/xiandaidushi, https://www.52shuku.net/chongsheng, https://www.52shuku.net/jiakong and https://www.52shuku.net/gl and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 pages with very little text

    https://www.52shuku.net/bookcase.html, https://www.52shuku.net/tuijian, https://www.52shuku.net/zuozhe/daquan.html, https://www.52shuku.net/xiandaidushi, https://www.52shuku.net/chongsheng and https://www.52shuku.net/jiakong and 8 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 199 found) and read each the way a search engine does.

4 checks passed
  • 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 97 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Invalid left-hand side expression in prefix operation”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • 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 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 33 words

    The homepage has only about 33 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.

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and 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.

  • 2 cookies set on arrival

    2

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

  • 3 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on 52shuku.net, including 7 speed issues, 5 SEO issues and 5 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