Programmable

Website review, no card needed

publicrecordsdata.us logo

publicrecordsdata.us website review

Visit site (opens in a new tab)Reviewed 11 October 202612 issues · 71 checks

This review found 12 issues worth fixing on publicrecordsdata.us, 4 of them high impact, across 71 checks. The most urgent: 3 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

Site score

92A

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.2 s505 msApr 18Oct 3856 ms
Show as table
DateReal-visitor load time (LCP)
Apr 18, 2026631 ms
Apr 25, 2026629 ms
May 2, 2026584 ms
May 9, 2026587 ms
May 16, 2026710 ms
May 23, 2026804 ms
May 30, 2026906 ms
Jun 6, 2026999 ms
Jun 13, 2026890 ms
Jun 20, 2026860 ms
Jun 27, 2026858 ms
Jul 4, 2026837 ms
Jul 11, 2026954 ms
Jul 18, 2026971 ms
Jul 25, 2026966 ms
Aug 1, 20261.0 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.0 s
Sep 26, 2026921 ms
Oct 3, 2026856 ms
Real-visitor tap response (INP)75th percentile, phones
338 ms111 msApr 18Oct 3295 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026185 ms
Apr 25, 2026260 ms
May 2, 2026280 ms
May 9, 2026204 ms
May 16, 2026187 ms
May 23, 2026159 ms
May 30, 2026137 ms
Jun 6, 2026154 ms
Jun 13, 2026153 ms
Jun 20, 2026158 ms
Jun 27, 2026167 ms
Jul 4, 2026174 ms
Jul 11, 2026196 ms
Jul 18, 2026207 ms
Jul 25, 2026215 ms
Aug 1, 2026229 ms
Aug 8, 2026253 ms
Aug 15, 2026278 ms
Aug 22, 2026297 ms
Aug 29, 2026306 ms
Sep 5, 2026308 ms
Sep 12, 2026312 ms
Sep 19, 2026306 ms
Sep 26, 2026300 ms
Oct 3, 2026295 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

www.publicrecordsdata.us (opens in a new tab)
Full-page screenshot of publicrecordsdata.us (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

99

  • Reduce unused CSS

    260 ms · 17 KiB

    About 17 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 260 ms faster on a phone.

  • Reduce unused JavaScript

    229 KiB

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

  • 5 long tasks on the main thread

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

  • Use efficient cache lifetimes

    124 KiB

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

  • Render-blocking requests

    100 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

  • 5 third-party services on the page

    5 third-party services load with your homepage (FullStory, Google/Doubleclick Ads and Google Tag Manager and others), adding 93 KiB and 51 ms of main-thread time.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

3 checks passed

  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99 (desktop: 99). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.7 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

3 to fix100

  • Tap response (INP) got 34% slower for real visitors

    +34%

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

  • Largest content (LCP) got 41% slower for real visitors

    +41%

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

  • Time to Interactive: 6.0 s

    6.0 s

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

11 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.9 s

    0.9 s

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

  • Real-user INP: 102 ms

    102 ms

    Real visitors wait 102 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.9 s

    0.9 s

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

  • Real-user TTFB: 566 ms

    566 ms

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

  • Total Blocking Time: 128 ms

    128 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “PublicRecordsData.us does not provide consumer reports or o…”.

  • Speed Index: 1.2 s

    1.2 s

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

Images and page weight

100

  • About 0.2 g of CO₂ per visit

    0.15 g

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

4 checks passed

  • Page weight: 556 KiB in 17 requests

    556 KiB

    Your homepage downloads 556 KiB in 17 requests on a phone: scripts 495 KiB (6), HTML 31 KiB (1) and stylesheets 22 KiB (1). That is a lean page.

  • 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

2 to fixGoogle 9697

  • 3 text elements with low contrast

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

  • 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 checks passed

  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

1 to fixGoogle 10090

  • No H1 headline

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

  • 6 internal links, 10 external

    The homepage links to 6 pages on publicrecordsdata.us and 10 external pages.

7 checks passed

  • Meta description: 160 characters

    Your meta description is 160 characters: “Search public records by name to access court records, property history, contact details, and background information fr…”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “Public Records Search | PublicRecordsData.us”.

  • Canonical URL set

    The canonical URL is https://www.publicrecordsdata.us/.

  • Structured data in place

    Structured data found: FAQPage, Organization 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://www.publicrecordsdata.us/sitemap.xml.

AI search readiness

100

  • No llms.txt

    There is no https://www.publicrecordsdata.us/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.

  • Opted out of AI training for 3 crawlers

    robots.txt blocks Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Other pages

2 to fix88

  • 1 linked page hidden from search

    https://www.publicrecordsdata.us/feature/age-verification is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without an H1

    https://www.publicrecordsdata.us/feature/age-verification has no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 internal pages checked

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

5 checks passed

  • Linked pages load

    All 5 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 5 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093

  • 3 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix71

  • 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 social proof

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

  • About 1,213 words of copy

    The homepage carries about 1,213 words of visible text.

5 checks passed

  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • 2 short forms

    2 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix

  • 3 trackers load before any consent

    3

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

  • 13 cookies set on arrival

    13

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

  • 7 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 12 issues on publicrecordsdata.us, including 3 speed issues, 1 SEO issue and 2 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