Page Speed Fixes That Matter on a Criminal Defense Website
A person who has just been charged with a crime is usually searching on a phone, often late at night, sometimes from a parking lot outside the jail. If your charge page takes several seconds to show anything useful, that person taps back and calls the next firm in the results. Speed is one of the few technical problems that costs you cases you never hear about.
Most defense firm sites are slow for boring reasons, like an oversized hero photo or a chat widget that loads before the text. Fixing them takes someone willing to measure first and work in the right order.
Start with field data, not a single test
Google's page experience signals rely on Core Web Vitals, which are three measurements taken from real Chrome users. Largest Contentful Paint (LCP) tracks how long the main content takes to appear, and Google's "good" mark is 2.5 seconds or less. Interaction to Next Paint (INP) replaced First Input Delay in March 2024 and looks at how quickly the page responds after someone taps, with 200 milliseconds as the good mark. Cumulative Layout Shift (CLS) measures how much things jump around while loading, and a score of 0.1 or lower is good.
Lab tools like PageSpeed Insights give you a score from one simulated visit. That score swings from run to run and can scare you over nothing. The more useful number sits at the top of the PageSpeed report under "Discover what your real users are experiencing," and in the Core Web Vitals report inside Search Console. Those come from actual visitors over the past 28 days. If you have never opened Search Console, a walkthrough like this first week in Google Search Console for defense lawyers will get you to that report quickly.
Smaller sites may lack page-level field data. Then the origin-level result in PageSpeed Insights is your best guide.
Fix the hero image first
On most law firm homepages and charge pages, the largest element is a photo: the courthouse, the skyline, the lawyer with arms crossed. That photo is usually what LCP measures, and it is usually far too large.
Here is the order I work in:
- Export the image at the size it actually displays, not the 5,000 pixel original from the photographer.
- Serve it as WebP or AVIF, with a JPEG fallback only if your platform needs one.
- Do not lazy load the image that appears at the top of the page. Lazy loading is for images further down.
- Add width and height attributes so the browser reserves the space and the layout does not jump.
On a WordPress site with a heavy theme, those four changes alone often move LCP from failing to passing.
Third-party scripts are usually the INP problem
When a page feels sticky after you tap the menu or the call button, the cause is nearly always JavaScript from somewhere else. Live chat vendors, call tracking scripts, review widgets, heat mapping tools and two or three analytics tags all compete for the same thread in the browser.
Make a list of every script the site loads. Your developer can pull it from the browser's network panel in a few minutes. Then ask a plain question about each one: who uses the data this produces, and when did they last look at it? Firms often find tracking tags from an agency they left years ago still running on every page.
For the scripts you keep, delaying them until after the page has loaded, or until the visitor first scrolls or taps, usually fixes INP without losing the tool. Chat is the common exception people argue about. If your intake team truly answers chat at 2 a.m., keep it, but load it after the main content.
Layout shift and the call button
CLS sounds abstract until you watch it happen on a phone. The visitor goes to tap your phone number, a cookie banner or promo bar slides in at the top, the whole page drops 80 pixels, and they hit a link to your blog instead. That is a lost call.
The usual culprits are banners injected after load, web fonts that swap in late and change line lengths, and embedded maps or videos with no fixed height. Reserve space for anything that loads late. Preload the one or two font files you actually use. If you need a sticky call bar on mobile, build it into the page template instead of adding it with a plugin that inserts it after everything else renders.
Hosting and caching are the last mile
Once the page itself is lean, the server becomes the bottleneck. Cheap shared hosting can take a full second just to start sending the page, which leaves little room for anything else. A caching layer and a content delivery network fix most of this. Many hosts now include both, and static site setups get it almost for free.
Do not chase a perfect lab score of 100. Google has been clear that page experience is one signal among many and that relevant, helpful content still matters more. The goal is passing field data so speed is never the reason a charge page loses to a competitor, and so the visitor at midnight sees your number before they lose patience.
Questions about page speed on defense firm sites
Will a faster site move me up in Google by itself?
Rarely. Speed works more like a tiebreaker. A slow page with weak content will not jump to the top because it got faster, but a strong page can be held back if it fails Core Web Vitals badly.
Should I rebuild my site to fix speed?
Usually not first. Image fixes, script cleanup and better hosting solve most problems on existing sites. A rebuild makes sense when the theme or page builder itself is the bottleneck and nothing else moves the numbers.
How often should I check these numbers?
Look at the Search Console report monthly and after any site change, such as a new plugin, a new chat vendor or a redesign. Field data lags by about four weeks, so give fixes time to show up.
For more on crawling, indexing and other technical fixes, see our technical SEO guides for law firm websites.
SBD Marketing works only with criminal defense law firms, one firm per city. We build websites for defense practices, handle SEO for the charges a firm defends, work on visibility in AI search tools and run SEO audits that include the kind of speed review described here.