Website review, no card needed

sucuri.net logo

sucuri.net website review

Visit site (opens in a new tab)Reviewed 22 October 202631 issues · 80 checks

This review found 31 issues worth fixing on sucuri.net, 9 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.5 s3.2 sMay 2Oct 173.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.6 s
May 9, 20263.4 s
May 16, 20263.4 s
May 23, 20263.4 s
May 30, 20263.6 s
Jun 6, 20263.6 s
Jun 13, 20263.7 s
Jun 20, 20263.9 s
Jun 27, 20264.0 s
Jul 4, 20264.2 s
Jul 11, 20264.1 s
Jul 18, 20263.8 s
Jul 25, 20263.6 s
Aug 1, 20263.5 s
Aug 8, 20263.5 s
Aug 15, 20263.7 s
Aug 22, 20263.9 s
Aug 29, 20264.1 s
Sep 5, 20264.2 s
Sep 12, 20264.3 s
Sep 19, 20264.3 s
Sep 26, 20264.3 s
Oct 3, 20264.3 s
Oct 10, 20263.7 s
Oct 17, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
242 ms197 msMay 2Oct 17213 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026205 ms
May 9, 2026204 ms
May 16, 2026202 ms
May 23, 2026210 ms
May 30, 2026212 ms
Jun 6, 2026212 ms
Jun 13, 2026213 ms
Jun 20, 2026215 ms
Jun 27, 2026219 ms
Jul 4, 2026223 ms
Jul 11, 2026220 ms
Jul 18, 2026221 ms
Jul 25, 2026213 ms
Aug 1, 2026213 ms
Aug 8, 2026218 ms
Aug 15, 2026221 ms
Aug 22, 2026230 ms
Aug 29, 2026231 ms
Sep 5, 2026236 ms
Sep 12, 2026232 ms
Sep 19, 2026231 ms
Sep 26, 2026237 ms
Oct 3, 2026227 ms
Oct 10, 2026219 ms
Oct 17, 2026213 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

Full-page screenshot of sucuri.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sucuri.net at 1.2 s1.2 s
  2. sucuri.net at 2.4 s2.4 s
  3. sucuri.net at 3.7 s3.7 s
  4. sucuri.net at 4.9 s4.9 s
  5. sucuri.net at 6.1 s6.1 s
  6. sucuri.net at 7.3 s7.3 s
  7. sucuri.net at 8.5 s8.5 s
  8. sucuri.net at 9.7 s9.7 s

Speed

12 to fix54
  • Use efficient cache lifetimes

    3.3 s · 646 KiB

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

  • Render-blocking requests

    3.4 s

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

  • Reduce unused JavaScript

    2.1 s · 545 KiB

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

  • Improve image delivery

    1.9 s · 375 KiB

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

  • Reduce unused CSS

    900 ms · 142 KiB

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

  • Mobile performance score: 54

    54/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, GoDaddy and Clarity and others), adding 1.4 MB and 779 ms of main-thread time.

  • Google Tag Manager adds 401 ms

    401 ms

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

  • Legacy JavaScript

    300 ms · 20 KiB

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

  • Main-thread work: 2.7 s

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

  • 2,058 HTML elements

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

  • tidio.co adds 93 ms

    93 ms

    tidio.co costs a phone 93 ms of main-thread work and 515 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.

  • 6 long tasks on the main thread

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

  • 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.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 25 ms

    25 ms

    Your server sent the HTML in 25 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • 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.

  • Largest Contentful Paint: 18.9 s

    18.9 s

    Your largest element takes 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Clean and Protect Your Website Fast Website Security Made S…”.

  • Time to Interactive: 18.9 s

    18.9 s

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

  • First Contentful Paint: 5.1 s

    5.1 s

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

  • Speed Index: 10.1 s

    10.1 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 877 ms

    877 ms

    Real visitors wait 877 ms 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.

  • Tap response (INP) held steady for real visitors

    +6%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

4 checks passed
  • Real-user INP: 176 ms

    176 ms

    Real visitors wait 176 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Total Blocking Time: 190 ms

    190 ms

    Scripts block the page for only 190 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.002

    0.002

    The layout barely moves while loading (CLS 0.002, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 2.9 MB in 118 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 118 requests on a phone: scripts 1.4 MB (40), images 935 KiB (21) and fonts 238 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (180 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.

  • 2 images below the first screen load straight away

    2 images further down the page (180 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.82 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fixGoogle 9799
  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 43 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9293
  • 8 H1 headlines

    There are 8 <h1> headlines (“Clean and Protect Your Website Fast”, “Welcome to Sucuri” and “Please select a language”). One clear main headline is easier for people and search engines.

  • 7 links with vague text

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

  • 98 internal links, 38 external

    The homepage links to 98 pages on sucuri.net and 38 external pages.

7 checks passed
  • Meta description: 122 characters

    Your meta description is 122 characters: “Website security made simple—Sucuri offers fast malware cleanup, reliable monitoring, and powerful protection for any C…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Sucuri - Complete Website Security, Protection & Monitoring”.

  • Canonical URL set

    The canonical URL is https://sucuri.net/.

  • Structured data in place

    Structured data found: WPFooter, WPHeader 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://sucuri.net/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://sucuri.net/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.

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,190 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 13 pages share a title

    https://sucuri.net/live-chat, https://sucuri.net/website-security, https://sucuri.net/website-security-platform, https://sucuri.net/website-firewall, https://sucuri.net/custom/enterprise and https://sucuri.net/custom/agency and 7 others all use the title “You are being redirected...”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://sucuri.net/live-chat, https://sucuri.net/website-security, https://sucuri.net/website-security-platform, https://sucuri.net/website-firewall, https://sucuri.net/custom/enterprise and https://sucuri.net/custom/agency and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://sucuri.net/live-chat, https://sucuri.net/website-security, https://sucuri.net/website-security-platform, https://sucuri.net/website-firewall, https://sucuri.net/custom/enterprise and https://sucuri.net/custom/agency and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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

1 to fixGoogle 9293
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'offsetHeight')”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    14 of 16 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • About 1,148 words of copy

    The homepage carries about 1,148 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “See Pricing” and “Contact Us”.

  • 22 calls to action

    The homepage has 22 calls to action, for example “Sign up now.”, “See Pricing” and “Learn More”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • 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

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 1 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.

  • 19 other companies contacted

    Loading the homepage contacts 19 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 sucuri.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress

Company

Founded
2010
Headquarters
Menifee

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on sucuri.net, including 21 speed issues and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25