Website review, no card needed

sysdig.com logo

sysdig.com website review

Visit site (opens in a new tab)Reviewed 29 October 202637 issues · 81 checks

This review found 37 issues worth fixing on sysdig.com, 17 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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
5.2 s2.1 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.2 s
May 16, 20263.3 s
May 23, 20263.5 s
May 30, 20263.8 s
Jun 6, 20263.8 s
Jun 13, 20264.2 s
Jun 20, 20264.6 s
Jun 27, 20264.8 s
Jul 4, 20264.9 s
Jul 11, 20264.4 s
Jul 18, 20263.8 s
Jul 25, 20263.2 s
Aug 1, 20262.4 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
176 ms100 msMay 9Oct 24138 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026114 ms
May 16, 2026122 ms
May 23, 2026129 ms
May 30, 2026147 ms
Jun 6, 2026144 ms
Jun 13, 2026152 ms
Jun 20, 2026163 ms
Jun 27, 2026165 ms
Jul 4, 2026167 ms
Jul 11, 2026138 ms
Jul 18, 2026123 ms
Jul 25, 2026114 ms
Aug 1, 2026109 ms
Aug 15, 2026111 ms
Aug 22, 2026116 ms
Aug 29, 2026118 ms
Sep 5, 2026124 ms
Sep 12, 2026130 ms
Sep 19, 2026129 ms
Sep 26, 2026133 ms
Oct 3, 2026130 ms
Oct 10, 2026127 ms
Oct 17, 2026136 ms
Oct 24, 2026138 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 sysdig.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sysdig.com at 0.9 s0.9 s
  2. sysdig.com at 1.9 s1.9 s
  3. sysdig.com at 2.8 s2.8 s
  4. sysdig.com at 3.8 s3.8 s
  5. sysdig.com at 4.7 s4.7 s
  6. sysdig.com at 5.7 s5.7 s
  7. sysdig.com at 6.6 s6.6 s
  8. sysdig.com at 7.6 s7.6 s

Speed

12 to fix31
  • Reduce unused JavaScript

    4.7 s · 1.0 MB

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

  • Render-blocking requests

    3.2 s

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

  • Use efficient cache lifetimes

    2.3 s · 497 KiB

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

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 870 KiB 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: 31

    31/100

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

  • Main-thread work: 5.1 s

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

  • 3,656 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, pathfactory.com and website-files.com and others), adding 2.5 MB and 2.4 s of main-thread time.

  • pathfactory.com adds 512 ms

    512 ms

    pathfactory.com costs a phone 512 ms of main-thread work and 663 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.

  • Reduce unused CSS

    450 ms · 112 KiB

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

  • website-files.com adds 337 ms

    337 ms

    website-files.com costs a phone 337 ms of main-thread work and 644 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.

  • 16 long tasks on the main thread

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

  • Improve image delivery

    8 KiB

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

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 10 ms

    10 ms

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

Core Web Vitals

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

  • First Contentful Paint: 9.3 s

    9.3 s

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

  • Largest Contentful Paint: 17.5 s

    17.5 s

    Your largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sysdig and its vendors use cookies and related technologies…”.

  • Time to Interactive: 19.7 s

    19.7 s

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

  • Speed Index: 9.3 s

    9.3 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Tap response (INP) got 16% slower for real visitors

    +16%

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

4 checks passed
  • Real-user INP: 137 ms

    137 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 24% faster for real visitors

    -24%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.8 MB in 129 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 129 requests on a phone: scripts 2.3 MB (32), stylesheets 167 KiB (12) and images 105 KiB (31). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.80 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 9794
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • Elements must only use permitted ARIA attributes (6 elements)

    Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (2 elements)

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

  • 4 form fields without a label

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

  • 1 text element with low contrast

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

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

3 to fixGoogle 9289
  • Meta description is long (165 characters)

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

  • Structured data has 1 problem

    Structured data found (WebPage) but with 1 problem, for example “WebPage: url is not an absolute URL ("/")”.

  • 2 links with vague text

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

  • 96 internal links, 48 external

    The homepage links to 96 pages on sysdig.com and 48 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Cloud and AI defense rooted in runtime intelligence.”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Sysdig | Cloud Security Starts at Runtime”.

  • Canonical URL set

    The canonical URL is https://www.sysdig.com/.

  • 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.sysdig.com/sitemap-rewrite/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.

3 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 (1,398 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.sysdig.com/llms.txt (14 KiB, 59 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 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.sysdig.com/solutions/cloud-native-application-protection-platform, whose canonical is https://www.sysdig.com/solutions/cloud-native-application-protection-platform-cnapp. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 63 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

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17150324&tm=gtm002&Ver=2&mid=389e61f4-a6ae-4cf9-adb1-22f1e23c17d0&bo=1&sid=aeba5ec0d3dc11f1a35ff9ce8e0d623d&vid=aeba8b50d3dc11f1a747db194c5d86ba&vids=1&msclkid=N&pi=91.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “MktoForms2 is not defined”.

2 checks passed
  • Tap targets are thumb-sized

    17 of 21 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No call to action on the first screen

    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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,006 words of copy

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

4 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact Us”, “Contact Support” and “Get Demo”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 9 testimonial or review blocks and 20 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 5 trackers load before any consent

    5

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

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies (measured from a US location before any click).

  • 36 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 sysdig.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
Webflow
Analytics
Google Tag Manager
Hosting
CloudFront

Hiring

Hiring
31 open roles
Teams
SALES REPS (9), SECURE (4), CISO Security & Compliance (3), CS (3)
Job board
lever

Company

Employees
197

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on sysdig.com, including 22 speed issues, 3 SEO issues and 2 conversion gaps. 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