Website review, no card needed
fljud13.org website review
Visit site (opens in a new tab)Reviewed 30 October 202633 issues · 86 checks
This review found 33 issues worth fixing on fljud13.org, 8 of them high impact, across 86 checks. The most urgent: improve image delivery. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.1 s |
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 294 ms |
| May 16, 2026 | 296 ms |
| May 23, 2026 | 295 ms |
| May 30, 2026 | 295 ms |
| Jun 6, 2026 | 287 ms |
| Jun 13, 2026 | 270 ms |
| Jun 20, 2026 | 219 ms |
| Jun 27, 2026 | 80 ms |
| Jul 4, 2026 | 81 ms |
| Jul 11, 2026 | 82 ms |
| Jul 18, 2026 | 80 ms |
| Jul 25, 2026 | 83 ms |
| Aug 1, 2026 | 84 ms |
| Aug 8, 2026 | 87 ms |
| Aug 15, 2026 | 88 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 87 ms |
| Sep 5, 2026 | 82 ms |
| Sep 12, 2026 | 85 ms |
| Sep 19, 2026 | 87 ms |
| Sep 26, 2026 | 89 ms |
| Oct 3, 2026 | 95 ms |
| Oct 10, 2026 | 92 ms |
| Oct 17, 2026 | 88 ms |
| Oct 24, 2026 | 89 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
How it loaded on a phone
0.4 s
0.8 s
1.3 s
1.7 s
2.1 s
2.5 s
3.0 s
3.4 s
Speed
Improve image delivery
4.1 s · 855 KiB4 images could be 855 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.1 s faster on a phone.
Render-blocking requests
2.5 s33 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Reduce unused JavaScript
900 ms · 202 KiBAbout 202 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, userway.org and docaccess.com and others), adding 419 KiB and 313 ms of main-thread time.
Use efficient cache lifetimes
250 ms · 39 KiB3 files are served with short cache lifetimes, so returning visitors download them again (39 KiB).
Legacy JavaScript
250 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Reduce unused CSS
150 ms · 43 KiBAbout 43 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
150 ms · 17 KiB17 KiB could be saved by minifying JavaScript.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 124 ms. During a long task the page ignores taps.
Document request latency
80 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 628 ms of it running JavaScript. That is comfortably low.
Server response: 98 ms
98 msYour server sent the HTML in 98 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.2 s
11.2 sYour largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 11.2 s
11.2 sThe page becomes fully interactive after 11.2 s. Good is under 3.8 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.13
0.13The layout shifts by 0.13 while loading, so content jumps under the reader's thumb. Good is under 0.1.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 79 ms
79 msReal visitors wait 79 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 559 ms
559 msReal visitors wait 559 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 70% faster for real visitors
-70%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 294 ms to 89 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 122 ms
122 msScripts block the page for only 122 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.1 MB in 65 requests
2.1 MBYour homepage downloads 2.1 MB in 65 requests on a phone: images 1.2 MB (6), scripts 529 KiB (25) and HTML 121 KiB (1). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (536 KiB) 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.
2 images far larger than shown
155 KiB2 images are downloaded at several times the size a phone draws them, for example logo-white.png at 2,400 px wide, shown at 15 px. Resized copies would save about 155 KiB.
2 images below the first screen load straight away
2 images further down the page (155 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 70.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h6, h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Home page content” and “Thirteenth Judicial Circuit Court of Florida”). 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.
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 XML sitemap
No XML sitemap at https://www.fljud13.org/sitemap.xml, so Google discovers your pages only by following links.
9 links with vague text
9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
2 links crawlers can't follow
2 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.
144 internal links, 9 external
The homepage links to 144 pages on fljud13.org and 9 external pages.
2 checks passed
Title: 34 characters
Your title is a healthy 34 characters: “Thirteenth Judicial Circuit > Home”.
robots.txt in place
robots.txt is in place.
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://www.fljud13.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 (507 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages share 2 titles
/, https://www.fljud13.org/tabid/43/Default.aspx and https://www.fljud13.org/Home all use the title “Thirteenth Judicial Circuit > Home”, and 1 other title repeat too. 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://www.fljud13.org/About/About-the-Court/About-the-Court-3, https://www.fljud13.org/Directory/Judges, https://www.fljud13.org/Resources/Administrative-Orders, https://www.fljud13.org/Resources/ADA, https://www.fljud13.org/tabid/43/Default.aspx and https://www.fljud13.org/Home and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 59 found) and read each the way a search engine does.
5 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.
Every page has an H1
Each page we checked has a main headline.
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
35 small tap targets
35 of 52 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 194 words
The homepage has only about 194 words of visible text; thin pages give Google and first-time buyers little to go on.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more”.
10 calls to action
The homepage has 10 calls to action, for example “Contact Us”, “ADA Accommodations Request” and “Audio Request”.
1 short form
A short form (2 fields 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
2 trackers load before any consent
2Before 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.
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.
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 fljud13.org, 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
- Hosting
- BHN
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on fljud13.org, including 11 speed issues, 8 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.