Website review, no card needed

paldb.cc logo

paldb.cc website review

Visit site (opens in a new tab)Reviewed 12 October 202639 issues · 74 checks

This review found 39 issues worth fixing on paldb.cc, 19 of them high impact, across 74 checks. The most urgent: reduce unused JavaScript. 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.6 s1.1 sApr 18Oct 31.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.5 s
Apr 25, 20261.5 s
May 2, 20261.5 s
May 9, 20261.5 s
May 16, 20261.5 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.3 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
159 ms116 msApr 18Oct 3154 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026153 ms
Apr 25, 2026147 ms
May 2, 2026146 ms
May 9, 2026147 ms
May 16, 2026149 ms
May 23, 2026153 ms
May 30, 2026154 ms
Jun 6, 2026153 ms
Jun 13, 2026150 ms
Jun 20, 2026147 ms
Jun 27, 2026146 ms
Jul 4, 2026146 ms
Jul 11, 2026126 ms
Jul 18, 2026121 ms
Jul 25, 2026123 ms
Aug 1, 2026126 ms
Aug 8, 2026128 ms
Aug 15, 2026131 ms
Aug 22, 2026135 ms
Aug 29, 2026134 ms
Sep 5, 2026137 ms
Sep 12, 2026140 ms
Sep 19, 2026146 ms
Sep 26, 2026151 ms
Oct 3, 2026154 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 paldb.cc (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. paldb.cc at 0.4 s0.4 s
  2. paldb.cc at 0.8 s0.8 s
  3. paldb.cc at 1.2 s1.2 s
  4. paldb.cc at 1.6 s1.6 s
  5. paldb.cc at 2.0 s2.0 s
  6. paldb.cc at 2.4 s2.4 s
  7. paldb.cc at 2.8 s2.8 s
  8. paldb.cc at 3.2 s3.2 s

Speed

6 to fix11
  • Reduce unused JavaScript

    6.8 s · 1.6 MB

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

  • Avoid multiple page redirects

    2.0 s

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

  • Main-thread work: 11.2 s

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

  • Mobile performance score: 11

    11/100

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

  • 20 long tasks on the main thread

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

  • Cloudflare CDN adds 183 ms

    183 ms

    Cloudflare CDN costs a phone 183 ms of main-thread work and 317 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Cloudflare CDN, datatables.net and Unpkg and others), adding 385 KiB and 221 ms of main-thread time.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

9 to fix67
  • 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 CLS: 0.28

    0.28

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

  • First Contentful Paint: 7.9 s

    7.9 s

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

  • Largest Contentful Paint: 17.4 s

    17.4 s

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

  • Time to Interactive: 44.5 s

    44.5 s

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

  • Total Blocking Time: 3.4 s

    3.4 s

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

  • Speed Index: 12.5 s

    12.5 s

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

  • Cumulative Layout Shift: 0.286

    0.286

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

  • 23 images without width and height

    23 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 153 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user INP: 97 ms

    97 ms

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 748 ms

    748 ms

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

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

    -12%

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

Images and page weight

1 to fix70
  • Page weight: 5.3 MB in 596 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 596 requests on a phone: scripts 3.9 MB (92), images 516 KiB (184) and HTML 377 KiB (36). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.50 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.50 g of CO₂e: 179.7 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

3 to fixGoogle 8795
  • 65 images without alt text

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

  • 29 links without text

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

  • Frames without titles

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

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

6 to fixGoogle 8362
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (22 characters)

    Your title is only 22 characters: “Palworld Database Wiki”. 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 canonical URL

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

  • 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 X (Twitter) card tag

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

  • 266 internal links, 6 external

    The homepage links to 266 pages on paldb.cc and 6 external pages.

2 checks passed
  • 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://paldb.cc/sitemap.xml.

AI search readiness

1 to fix88
  • 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://paldb.cc/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 (695 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    / and https://paldb.cc/en all use the title “Palworld Database Wiki”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://paldb.cc/en, https://paldb.cc/en/Palpagos_Islands, https://paldb.cc/en/The_World_Tree, https://paldb.cc/en/Breed, https://paldb.cc/en/Pal_Calc and https://paldb.cc/en/Capture_Rate and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://paldb.cc/en, https://paldb.cc/en/Palpagos_Islands, https://paldb.cc/en/The_World_Tree, https://paldb.cc/en/Breed, https://paldb.cc/en/Pal_Calc and https://paldb.cc/en/Capture_Rate and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 146 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

5 to fixGoogle 5073
  • 8 broken images

    8 images failed to load on a phone, for example https://ids4.ad.gt/api/v1/ip_match?id=AU1D-0100-001791770545-YBFOCXLS-ZJ9W.

  • 36 third-party cookies

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

  • Deprecated browser APIs

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) NotSupportedError: Failed to execute 'browsingTopics' on 'Document': document.browsingTopics() is…”.

  • 22 distorted images

    22 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • 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 524 words of copy

    The homepage carries about 524 words of visible text.

2 checks passed
  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 19 cookies set on arrival

    19

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

  • 57 other companies contacted

    Loading the homepage contacts 57 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 paldb.cc, 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 39 issues on paldb.cc, including 15 speed issues, 6 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

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