prinzlawstore.com website review

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

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

About 120 KiB of CSS is downloaded but never applied on this page. 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 250 ms).

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

3 third-party services load with your homepage (userway.org, cleantalk.org and Google Fonts), adding 161 KiB and 30 ms of main-thread time.

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

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

3 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Prinz Law Office is a California tech business law firm…”. Most of its time is element render delay (3.4 s).

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.

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

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

ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is 138 characters, so Google will cut it off around 60: “Prinz Law Store: Prinz Law Office; SaaS Law Firm; SaaS Lawyer Kristie Prinz The Prinz Law…”.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 22 pages on prinzlawstore.com and 6 external pages.

There is no https://prinzlawstore.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://prinzlawstore.com/2020/11/best-practices-for-negotiating-saas-agreements-in-an-uncertain-economy-2 and https://prinzlawstore.com/2020/03/best-practices-for-negotiating-saas-agreements-in-an-uncertain-economy all use the title “Prinz Law Store: Prinz Law Office; SaaS Law Firm; SaaS Lawyer Kristie…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://prinzlawstore.com/2020/11/introduction-to-negotiating-drafting-saas-agreements, https://prinzlawstore.com/2020/11/best-practices-for-negotiating-saas-agreements-in-an-uncertain-economy-2 and https://prinzlawstore.com/2020/11/negotiating-consulting-services-agreements-in-an-uncertain-economy have no meta description, so Google writes the search snippet from whatever text it finds.

https://prinzlawstore.com/2020/03/best-practices-for-negotiating-development-agreements-in-an-uncertain-economy and https://prinzlawstore.com/2019/10/legal-developments-impacting-the-software-industry-2019 took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

No viewport meta tag, so phones render the desktop layout zoomed out.

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

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

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

The homepage carries about 393 words of visible text.

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