jshfirm.com website review

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

About 234 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

A phone's processor spends 4.6 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

13 images could be 161 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

4 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Google Fonts and others), adding 421 KiB and 149 ms of main-thread time.

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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.

Your largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (12.7 s).

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

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

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

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

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

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

Your homepage downloads 2.6 MB in 141 requests on a phone: images 1.2 MB (43), scripts 750 KiB (73) and fonts 358 KiB (10). Under 2 MB keeps phones on slow connections fast.

1 image (35 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.

2 images further down the page (130 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

101 images have no alt text, which hurts accessibility and image search.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

14 visible links have no text or label, so screen readers cannot say where they go.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

There are 6 <h1> headlines (“Mark Zukowski Featured in October 2026 edition of…”, “Recent News” and “Defending Self-Insureds, Insurers & Insureds in t…”). One clear main headline is easier for people and search engines.

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

The homepage links to 116 pages on jshfirm.com and 15 external pages.

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

https://www.jshfirm.com/professionals, https://www.jshfirm.com/practices_industries/alternative-dispute-resolution, https://www.jshfirm.com/practices_industries/automobile-liability-defense, https://www.jshfirm.com/practices_industries/aviation-law, https://www.jshfirm.com/practices_industries/bad-faith-and-extra-contractual-liability and https://www.jshfirm.com/practices_industries/construction-litigation and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.jshfirm.com/professionals, https://www.jshfirm.com/practices_industries/appeals, https://www.jshfirm.com/practices_industries/automobile-liability-defense, https://www.jshfirm.com/practices_industries/aviation-law, https://www.jshfirm.com/practices_industries/bad-faith-and-extra-contractual-liability and https://www.jshfirm.com/practices_industries/commercial-law and 4 others took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://www.jshfirm.com/wp-content/uploads/2019/01/PLAN-LOGO-.png.

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

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 ()”.

3 images are served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 559 words of visible text.

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

Opening the homepage sets 2 cookies (measured from a US location before any click).

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.

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