Website review, no card needed
esentire.com website review
Visit site (opens in a new tab)Reviewed 19 November 202649 issues · 95 checks
This review found 49 issues worth fixing on esentire.com, 20 of them high impact, across 95 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
67DClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.8 s |
| Oct 31, 2026 | 4.5 s |
| Nov 7, 2026 | 7.9 s |
| Nov 14, 2026 | 9.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 159 ms |
| Jun 6, 2026 | 153 ms |
| Jun 13, 2026 | 175 ms |
| Jun 20, 2026 | 169 ms |
| Jun 27, 2026 | 168 ms |
| Jul 4, 2026 | 175 ms |
| Jul 11, 2026 | 154 ms |
| Jul 18, 2026 | 165 ms |
| Jul 25, 2026 | 158 ms |
| Aug 1, 2026 | 153 ms |
| Aug 8, 2026 | 155 ms |
| Aug 15, 2026 | 144 ms |
| Aug 22, 2026 | 155 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 183 ms |
| Sep 19, 2026 | 187 ms |
| Sep 26, 2026 | 174 ms |
| Oct 3, 2026 | 185 ms |
| Oct 10, 2026 | 206 ms |
| Oct 17, 2026 | 210 ms |
| Oct 24, 2026 | 213 ms |
| Oct 31, 2026 | 219 ms |
| Nov 7, 2026 | 226 ms |
| Nov 14, 2026 | 233 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
12.9 s · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.9 s faster on a phone.
Use efficient cache lifetimes
1.3 s · 1.7 MB97 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Reduce unused CSS
1.6 s · 244 KiBAbout 244 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Render-blocking requests
1.4 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Google CDN adds 1.1 s
1.1 sGoogle CDN costs a phone 1.1 s of main-thread work and 2.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 29
29/100Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.6 s
A phone's processor spends 9.6 s on main-thread work while loading, 5.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Wistia and others), adding 5.6 MB and 3.0 s of main-thread time.
Wistia adds 504 ms
504 msWistia costs a phone 504 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.
Google Tag Manager adds 624 ms
624 msGoogle Tag Manager costs a phone 624 ms of main-thread work and 550 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.
Improve image delivery
467 KiB6 images could be 467 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
350 ms · 51 KiBPolyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Drift adds 293 ms
293 msDrift costs a phone 293 ms of main-thread work and 812 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 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 253 ms. During a long task the page ignores taps.
1,878 HTML elements
The page has 1,878 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user LCP: 8.6 s
8.6 sReal visitors wait 8.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 8.3 s
8.3 sThe first text or image appears after 8.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 38.0 s
38.0 sYour largest element takes 38.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Video Thumbnail”.
Speed Index: 16.4 s
16.4 sVisually, the page fills in at 16.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 42.9 s
42.9 sThe page becomes fully interactive after 42.9 s. Good is under 3.8 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Real-user INP: 252 ms
252 msReal visitors wait 252 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 47% slower for real visitors
+47%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 159 ms to 233 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 188% slower for real visitors
+188%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.0 s to 9.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
2 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 9.3 MB in 365 requests
9.3 MBYour homepage downloads 9.3 MB in 365 requests on a phone: scripts 4.6 MB (124), other files 1.9 MB (96) and images 1.3 MB (94). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (714 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.
10 images below the first screen load straight away
10 images further down the page (735 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
52 KiB1 image is downloaded at several times the size a phone draws it, for example esentire_web_mssp_alert_2025.png at 670 px wide, shown at 171 px. Resized copies would save about 52 KiB.
About 2.6 g of CO₂ per visit
2.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.64 g of CO₂e: 316.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (32 elements)
All page content should be contained by landmarks: 32 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h6 and h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 96 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (81 characters)
Your title is 81 characters, so Google will cut it off around 60: “Managed Detection and Response Services & Security Operations Platform | eSentire”.
Meta description is long (296 characters)
Your meta description is 296 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
182 internal links, 19 external
The homepage links to 182 pages on esentire.com and 19 external pages.
6 checks passed
One H1 headline
Your main headline reads: “MDR THAT MOVES FIRST”.
Canonical URL set
The canonical URL is https://www.esentire.com/.
Structured data in place
Structured data found: BreadcrumbList, LocalBusiness, Organization, ProfessionalService and WebPage.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.esentire.com/sitemaps-1-sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,003 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.esentire.com/llms.txt (3 KiB, 24 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.esentire.com/what-we-do/atlas-user-experience, whose canonical is https://www.esentire.com/what-we-do/atlas-operations-center. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages slow to respond
https://www.esentire.com/what-we-do/esentire-managed-detection-and-response and https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/microsoft-mdr took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 93 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,036 words of copy
The homepage carries about 1,036 words of visible text.
10 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get Started” and “BUILD A QUOTE”.
14 calls to action
The homepage has 14 calls to action, for example “Get Started”, “Pricing” and “PRICING”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 52 testimonial or review blocks, 71 customer or partner logos, a star rating and 8 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 5 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Ads and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
19 cookies set on arrival
19Opening the homepage sets 19 cookies, 2 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
42 other companies contacted
Loading the homepage contacts 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at esentire.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- SEOmatic
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Company
- Employees
- 130
- Headquarters
- Waterloo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on esentire.com, including 28 speed issues and 3 SEO issues. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.