devo.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, YouTube and Hotjar and others), adding 3.3 MB and 2.0 s of main-thread time.

8 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 302 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

YouTube costs a phone 674 ms of main-thread work and 1.9 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.

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

Hotjar costs a phone 369 ms of main-thread work and 67 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.

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

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

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

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 17.3 MB in 228 requests on a phone: media 10.8 MB (1), scripts 3.8 MB (67) and images 1.7 MB (73). Under 2 MB keeps phones on slow connections fast.

white-glich-xl.webp weighs 666 KiB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example white-glich-xl.webp at 5,562 px wide, shown at 390 px. Resized copies would save about 692 KiB.

1 image further down the page (278 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 4.90 g of CO₂e: 588.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

3 images have no alt text, which hurts accessibility and image search.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

There are 2 <h1> headlines (“Defend with data” and “Defend with data..”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 107 pages on devo.com and 14 external pages.

Your homepage links to /why-devo/devo-for-higher-education and /blog/beyond-siem-transform-into-a-data-driven-organization-with-devo, which answer with an error. Visitors hit a dead end and search engines drop them.

/public-sector-solutions and /why-devo/devo-for-telecommunications took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343186816&tm=gtm002&Ver=2&mid=a5622d39-2faf-462d-a9de-82b02cd99fc1&bo=1&sid=cd34c1a0d7b911f185c8d9faf83fbf1e&vid=cd34d890d7b911f18d2f1b56bddc2048&vids=1&msclkid=N&pi=9.

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

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

Large scripts ship without source maps.

5 links from your homepage to your own site are broken, for example https://www.devo.com/why-devo/devo-for-higher-education/ (504).

2 links to other sites are dead, for example https://us.devo.com/ (404).

1 link go through two or more redirects, for example http://www.clubdevo.com/devo-home.

X-XSS-Protection is set to “1; mode=block;”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

devo.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

devo.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

devo.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 27 cookies, 1 of them by other companies (measured from a US location before any click).

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