Website review, no card needed

browardclerk.org logo

browardclerk.org website review

Visit site (opens in a new tab)Reviewed 11 October 202646 issues · 90 checks

This review found 46 issues worth fixing on browardclerk.org, 19 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. 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 s1.0 sApr 18Oct 31.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.1 s
Apr 25, 20261.1 s
May 2, 20261.1 s
May 9, 20261.1 s
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 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, 20261.0 s
Oct 3, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
120 ms110 msApr 18Oct 3118 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026113 ms
Apr 25, 2026113 ms
May 2, 2026112 ms
May 9, 2026112 ms
May 16, 2026111 ms
May 23, 2026112 ms
May 30, 2026112 ms
Jun 6, 2026113 ms
Jun 13, 2026113 ms
Jun 20, 2026113 ms
Jun 27, 2026113 ms
Jul 4, 2026113 ms
Jul 11, 2026113 ms
Jul 18, 2026113 ms
Jul 25, 2026115 ms
Aug 1, 2026116 ms
Aug 8, 2026119 ms
Aug 15, 2026119 ms
Aug 22, 2026119 ms
Aug 29, 2026119 ms
Sep 5, 2026117 ms
Sep 12, 2026118 ms
Sep 19, 2026118 ms
Sep 26, 2026118 ms
Oct 3, 2026118 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 browardclerk.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix48
  • Use efficient cache lifetimes

    27.9 s · 7.4 MB

    72 files are served with short cache lifetimes, so returning visitors download them again (7.4 MB).

  • Render-blocking requests

    20.8 s

    50 files block the first paint until they finish downloading. Deferring or inlining them could save about 20.8 s.

  • Reduce unused JavaScript

    12.6 s · 2.2 MB

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

  • Improve image delivery

    5.9 s · 2.7 MB

    9 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.9 s faster on a phone.

  • Reduce unused CSS

    4.2 s · 685 KiB

    About 685 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.2 s faster on a phone.

  • Minify JavaScript

    1.1 s · 230 KiB

    230 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 48

    48/100

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

  • Minify CSS

    450 ms · 77 KiB

    77 KiB could be saved by minifying CSS.

  • 3 long tasks on the main thread

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Other Google APIs/SDKs, userway.org and Google Analytics and others), adding 249 KiB and 173 ms of main-thread time.

  • Font display

    100 ms

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

  • Document request latency

    74 KiB

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

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

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 44 ms

    44 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • First Contentful Paint: 22.6 s

    22.6 s

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

  • Largest Contentful Paint: 38.9 s

    38.9 s

    Your largest element takes 38.9 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: 22.6 s

    22.6 s

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

  • Time to Interactive: 40.5 s

    40.5 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Cumulative Layout Shift: 0.124

    0.124

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 113 ms to 118 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 1.1 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 70 ms

    70 ms

    Real visitors wait 70 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 TTFB: 539 ms

    539 ms

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

  • Total Blocking Time: 179 ms

    179 ms

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

Images and page weight

5 to fix18
  • Page weight: 7.8 MB in 91 requests

    7.8 MB

    Your homepage downloads 7.8 MB in 91 requests on a phone: images 3.8 MB (24), scripts 3.0 MB (27) and stylesheets 792 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    FallCourthouseMarriageFlyer_Oct302026.png weighs 1.2 MB. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    1.3 MB

    4 images are downloaded at several times the size a phone draws them, for example FallCourthouseMarriageFlyer_Oct302026.png at 897 px wide, shown at 72 px. Resized copies would save about 1.3 MB.

  • 14 images in older formats

    14 images (2.5 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 5 images below the first screen load straight away

    5 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.20 g

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

Accessibility

8 to fixGoogle 9487
  • 4 text elements with low contrast

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

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • 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 (22 elements)

    All page content should be contained by landmarks: 22 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.

  • 5 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

  • Tables do not use <caption> instead of cells with the [colspan] attribute to indicate a caption.

    Tables do not use <caption> instead of cells with the [colspan] attribute to indicate a caption. (2 elements).

1 checks passed
  • 34 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 6 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 9278
  • No structured data

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

  • 3 H1 headlines

    There are 3 <h1> headlines (“US Citizens may apply for or renew passports at a…”, “Check out our NEW eServices!” and “Your Feedback Matters!”). One clear main headline is easier for people and search engines.

  • No canonical URL

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

  • Meta description is long (273 characters)

    Your meta description is 273 characters; Google truncates after about 160, so the end of your pitch is cut.

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

  • 5 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 156 internal links, 38 external

    The homepage links to 156 pages on browardclerk.org and 38 external pages.

3 checks passed
  • Title: 42 characters

    Your title is a healthy 42 characters: “Home Page - Broward County Clerk of Courts”.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at http://www.browardclerk.org/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://www.browardclerk.org/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 (1,340 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 2 pages share a title

    https://www.browardclerk.org/GeneralInformation/eFILING and https://www.browardclerk.org/GeneralInformation/eFiling all use the title “eFiling - Broward County Clerk of Courts”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.browardclerk.org/ClerkWebsite/BCCOC2/filedownload.aspx has no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages share a meta description

    https://www.browardclerk.org/GeneralInformation/Miscellaneous, https://www.browardclerk.org/GeneralInformation/eFILING, https://www.browardclerk.org/GeneralInformation/eFiling and https://www.browardclerk.org/Divisions/Appeals use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.browardclerk.org/ClerkWebsite/BCCOC2/filedownload.aspx has 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 42 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

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

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 919 words of visible text.

4 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Risk Protection Order”, “Apply for Criminal Indigent Status” and “Apply for Civil Indigent Status”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 browardclerk.org, 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 46 issues on browardclerk.org, including 17 speed issues, 6 SEO issues and 3 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