opstree.com website review

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

2 third-party services load with your homepage (rocketcdn.me and Cloudinary), adding 8.6 MB and 5 ms of main-thread time.

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

Cloudinary costs a phone 0 ms of main-thread work and 6.8 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.

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

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

rocketcdn.me costs a phone 5 ms of main-thread work and 1.8 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.

1 long task block the main thread while loading, the longest for 85 ms. During a long task the page ignores taps.

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

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.

Real visitors wait 5.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OpsTree AI Engineering”.

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

Your homepage downloads 9.0 MB in 20 requests on a phone: media 6.8 MB (1), images 2.0 MB (11) and HTML 185 KiB (1). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example BuildPiper-HOme-dashboard.webp at 1,672 px wide, shown at 358 px. Resized copies would save about 130 KiB.

1 image further down the page (222 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

5 buttons have no accessible name, so screen readers announce just “button”.

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

<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 8 elements on the page fail this check, rated serious 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: 91 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.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

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

7 links have no real href, so search engines can't follow them.

The homepage links to 163 pages on opstree.com and 27 external pages.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://opstree.com/solutions/observability-and-site-reliability, whose canonical is https://opstree.com/solutions/observability-and-system-reliability. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

5 of 15 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: net::ERR_FAILED”.

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.

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

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