decisionone.com website review

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

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

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

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.

Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Facebook and others), adding 1.5 MB and 946 ms of main-thread time.

79 KiB could be saved by minifying CSS.

Google Tag Manager costs a phone 428 ms of main-thread work and 534 KiB 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.

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

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

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

Vimeo costs a phone 39 ms of main-thread work and 540 KiB 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.

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

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

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

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

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

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

Your largest element takes 18.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 97 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Your homepage downloads 4.5 MB in 177 requests on a phone: scripts 2.4 MB (52), stylesheets 1.2 MB (48) and images 629 KiB (28). Under 2 MB keeps phones on slow connections fast.

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

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

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

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

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

Your title is only 7 characters: “Pomeroy”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“empowering every worker” and “Introducing”). One clear main headline is easier for people and search engines.

The homepage links to 123 pages on decisionone.com and 14 external pages.

There is no https://pomeroy.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://pomeroy.com/insights/case-studies/leading-national-retailer-5, https://pomeroy.com/what-we-do/managed-it-services/smartservices and https://pomeroy.com/what-we-do/managed-services/managed-cybersecurity-services have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=20132099&tm=gtm002&Ver=2&mid=5cce2802-745a-45d5-a075-29cf659bb6f1&bo=1&sid=2cf75880d44b11f1adb1410394f36b97&vid=2cf77430d44b11f1a3a23dbe3c111760&vids=1&msclkid=N&pi=91.

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

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 402 ()”.

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

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 608 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 4 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 25 cookies, 2 of them by other companies (measured from a US location before any click).

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