Website review, no card needed

billallenlaw.com logo

billallenlaw.com website review

Visit site (opens in a new tab)Reviewed 6 November 202621 issues · 82 checks

This review found 21 issues worth fixing on billallenlaw.com, 8 of them high impact, across 82 checks. The most urgent: page weight: 12.2 MB in 59 requests. 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
2.3 s1.9 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20262.1 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
138 ms63 msMay 16Oct 31108 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202672 ms
May 23, 202684 ms
May 30, 202677 ms
Jun 6, 202677 ms
Jun 13, 202688 ms
Jun 20, 202687 ms
Jun 27, 202690 ms
Jul 4, 202693 ms
Jul 11, 202695 ms
Jul 18, 202695 ms
Jul 25, 2026105 ms
Aug 1, 2026124 ms
Aug 8, 2026124 ms
Aug 15, 2026125 ms
Aug 22, 2026112 ms
Aug 29, 2026102 ms
Sep 5, 2026105 ms
Sep 12, 2026112 ms
Sep 19, 2026116 ms
Sep 26, 2026129 ms
Oct 3, 2026119 ms
Oct 10, 2026119 ms
Oct 17, 2026119 ms
Oct 24, 202696 ms
Oct 31, 2026108 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 billallenlaw.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

1 to fix100
  • 1,636 HTML elements

    The page has 1,636 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 2 third-party services on the page

    2 third-party services load with your homepage (CallRail and nitrocdn.com), adding 218 KiB and 56 ms of main-thread time.

  • Improve image delivery

    39 KiB

    1 image could be 39 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    22 KiB

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

  • Reduce unused CSS

    16 KiB

    About 16 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    12 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 checks passed
  • Mobile performance score: 100

    100/100

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

  • Main-thread work: 0.5 s

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

  • Server response: 22 ms

    22 ms

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

Core Web Vitals

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

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

    +31%

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

9 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 108 ms

    108 ms

    Real visitors wait 108 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.

  • First Contentful Paint: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0.009

    0.009

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

  • Largest Contentful Paint: 1.3 s

    1.3 s

    Your largest element renders in 1.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Gainesville Personal Injury Lawyers”.

  • Speed Index: 1.3 s

    1.3 s

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

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.3 s

    1.3 s

    The page is fully interactive after 1.3 s.

Images and page weight

1 to fix70
  • Page weight: 12.2 MB in 59 requests

    12.2 MB

    Your homepage downloads 12.2 MB in 59 requests on a phone: media 11.2 MB (1), other files 705 KiB (42) and fonts 111 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (40 KiB) is 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.

  • About 3.5 g of CO₂ per visit

    3.46 g

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

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

11 to fixGoogle 7385
  • 42 text elements with low contrast

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

  • Positive tabindex

    7 elements have a tabindex above 0, which scrambles the keyboard order.

  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • Links look like plain text

    4 links inside paragraphs rely on colour alone to stand out.

  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 link without text

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

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 17 links with vague text

    17 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 140 internal links, 22 external

    The homepage links to 140 pages on billallenlaw.com and 22 external pages.

8 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Gainesville personal injury lawyers at Allen Law have helped injured Floridians since 1992. Offices in Gainesville and …”.

  • One H1 headline

    Your main headline reads: “Gainesville Personal Injury Lawyers”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Gainesville Personal Injury Lawyer - Allen Law”.

  • Canonical URL set

    The canonical URL is https://billallenlaw.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, ImageObject, LegalService and Organization.

  • 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://billallenlaw.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://billallenlaw.com/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.

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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 79 found) and read each the way a search engine does.

7 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 a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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

2 to fixGoogle 10087
  • 22 small tap targets

    22 of 27 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 “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix95
  • A 8-field form

    Your longest form asks for 8 fields (5 required). Every extra field lowers completion.

  • About 3,134 words of copy

    The homepage carries about 3,134 words of visible text.

9 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call Now Button”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”, “contact us” and “Call Now Button”.

  • Social proof on the page

    Social proof on the homepage: 253 testimonial or review blocks, 12 customer or partner logos and 4 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 13 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • 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

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies, 1 of them by other companies (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.

  • 4 other companies contacted

    Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 billallenlaw.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager | Hotjar
Hosting
WP Engine

Hiring

Hiring
1 open role
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on billallenlaw.com, including 5 speed issues, 1 SEO issue and 1 conversion gap. 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