thezenith.com website review

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

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

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

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

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

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

39 KiB could be saved by minifying CSS.

3 third-party services load with your homepage (Accessibe Accessibility Overlay, Swiftype and JSDelivr CDN), adding 440 KiB and 169 ms of main-thread time.

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

9 KiB could be saved by minifying JavaScript.

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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 first text or image appears after 16.4 s on a phone. Good is under 1.8 s.

Your largest element takes 20.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “hp-slide-103”.

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

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

2 images have no width and height attributes, so the layout jumps as each one loads.

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 3.9 MB in 66 requests on a phone: scripts 1.7 MB (23), stylesheets 985 KiB (21) and images 825 KiB (12). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example hp-slide-103.jpg at 1,200 px wide, shown at 356 px. Resized copies would save about 14 KiB.

4 images (266 KiB) are 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 1.12 g of CO₂e: 134.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 4 <h1> headlines (“TheZenith”, “Home” and “TheZenith Home Page”). One clear main headline is easier for people and search engines.

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

No XML sitemap at https://thezenith.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at thezenith.com/robots.txt, the first file search crawlers ask for.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 71 pages on thezenith.com and 1 external page.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no /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.

/policyholders/workers-compensation/service-expertise and /policyholders/agribusiness-solutions/service-expertise all use the title “Service Expertise – TheZenith”. Search engines can't tell which page to show for a search, so each competes with the others.

/zenith/who-we-are, /zenith/contacts, /careers, /policyholders/workers-compensation/thezenith-difference, /policyholders/workers-compensation/service-expertise and /policyholders/workers-compensation/resources-support-online-tools and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 343 words of visible text.

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.