reitlerlaw.com website review

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.6 s.

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

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

5 third-party services load with your homepage (Google Tag Manager, Vimeo and Google Fonts and others), adding 27.1 MB and 197 ms of main-thread time.

Amazon Web Services costs a phone 0 ms of main-thread work and 20.4 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 70 (desktop: 35). Pages that score under 90 lose visitors before the first paint.

13 images could be 981 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Vimeo costs a phone 91 ms of main-thread work and 6.3 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 585 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

Scripts block taps and scrolling for 460 ms in total while the page loads. Good is under 200 ms.

Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “For 25 years, we have delivered exceptional counsel and wor…”.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 29.2 MB in 91 requests on a phone: images 21.7 MB (31), other files 6.0 MB (22) and scripts 1.2 MB (17). Under 2 MB keeps phones on slow connections fast.

3 images weigh 20.4 MB together. On a phone connection a single image that size takes seconds.

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

1 image is downloaded at several times the size a phone draws it, for example favicon-9.12.2023.png at 947 px wide, shown at 18 px. Resized copies would save about 289 KiB.

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (5 elements).

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

The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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

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

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

Chrome logged issues while loading the page (“Cookie”).

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 573 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.