Website review, no card needed

solarwinds.com logo

solarwinds.com website review

Visit site (opens in a new tab)Reviewed 29 October 202639 issues · 86 checks

This review found 39 issues worth fixing on solarwinds.com, 10 of them high impact, across 86 checks. The most urgent: render-blocking requests. 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.5 s2.4 sMay 9Oct 242.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.1 s
May 16, 20265.1 s
May 23, 20265.1 s
May 30, 20265.1 s
Jun 6, 20265.0 s
Jun 13, 20265.0 s
Jun 20, 20264.9 s
Jun 27, 20264.9 s
Jul 4, 20264.9 s
Jul 11, 20264.8 s
Jul 18, 20264.8 s
Jul 25, 20264.6 s
Aug 1, 20264.4 s
Aug 8, 20264.0 s
Aug 15, 20263.5 s
Aug 22, 20263.3 s
Aug 29, 20263.1 s
Sep 5, 20263.0 s
Sep 12, 20262.9 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
345 ms188 msMay 9Oct 24231 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026289 ms
May 16, 2026316 ms
May 23, 2026327 ms
May 30, 2026315 ms
Jun 6, 2026302 ms
Jun 13, 2026275 ms
Jun 20, 2026288 ms
Jun 27, 2026307 ms
Jul 4, 2026313 ms
Jul 11, 2026322 ms
Jul 18, 2026302 ms
Jul 25, 2026279 ms
Aug 1, 2026267 ms
Aug 8, 2026250 ms
Aug 15, 2026232 ms
Aug 22, 2026235 ms
Aug 29, 2026229 ms
Sep 5, 2026228 ms
Sep 12, 2026229 ms
Sep 19, 2026212 ms
Sep 26, 2026206 ms
Oct 3, 2026210 ms
Oct 10, 2026212 ms
Oct 17, 2026223 ms
Oct 24, 2026231 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 solarwinds.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. solarwinds.com at 0.8 s0.8 s
  2. solarwinds.com at 1.5 s1.5 s
  3. solarwinds.com at 2.3 s2.3 s
  4. solarwinds.com at 3.0 s3.0 s
  5. solarwinds.com at 3.8 s3.8 s
  6. solarwinds.com at 4.5 s4.5 s
  7. solarwinds.com at 5.3 s5.3 s
  8. solarwinds.com at 6.0 s6.0 s

Speed

11 to fix63
  • Render-blocking requests

    1.0 s

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

  • Main-thread work: 9.4 s

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

  • 3,181 HTML elements

    The page has 3,181 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, Adobe Tag Manager and TrackJS and others), adding 1.2 MB and 1.8 s of main-thread time.

  • Mobile performance score: 63

    63/100

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

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 519 ms

    519 ms

    Google Tag Manager costs a phone 519 ms of main-thread work and 525 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 JavaScript

    540 KiB

    About 540 KiB of JavaScript is downloaded but never used on this page.

  • Adobe Tag Manager adds 444 ms

    444 ms

    Adobe Tag Manager costs a phone 444 ms of main-thread work and 104 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.

  • Use efficient cache lifetimes

    335 KiB

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

  • TrackJS adds 272 ms

    272 ms

    TrackJS costs a phone 272 ms of main-thread work and 11 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

    43 KiB

    Polyfills for old browsers add 43 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    32 KiB

    About 32 KiB of CSS is downloaded but never applied on this page.

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 226 ms

    226 ms

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

Core Web Vitals

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

  • Time to Interactive: 23.7 s

    23.7 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Speed Index: 8.6 s

    8.6 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

6 checks passed
  • Real-user INP: 178 ms

    178 ms

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

  • Tap response (INP) got 25% faster for real visitors

    -25%

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

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

    -45%

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

  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Introducing goal-oriented AI.”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 2.5 MB in 220 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 220 requests on a phone: scripts 1.7 MB (74), fonts 284 KiB (8) and other files 223 KiB (96). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Avior_Demo_Screenshot_Original file.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.7 g of CO₂ per visit

    0.70 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

6 to fixGoogle 9692
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

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

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

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 141 images in the HTML carry an alt attribute.

  • 44 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: 44 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9285
  • 2 H1 headlines

    There are 2 <h1> headlines (“Introducing goal-oriented AI.” and “Introducing goal-oriented AI.”). One clear main headline is easier for people and search engines.

  • Structured data has 8 problems

    Structured data found (Organization, SoftwareApplication, WebPage and WebSite) but with 8 problems, for example “SoftwareApplication: no offers (price) block”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 224 internal links, 35 external

    The homepage links to 224 pages on solarwinds.com and 35 external pages.

5 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Simple, powerful, secure hybrid IT observability and IT management software built to accelerate your transformation. St…”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Observability, Database, and IT Service Management | SolarWinds”.

  • Canonical URL set

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

  • 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.solarwinds.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.solarwinds.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.

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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

3 to fix75
  • 2 pages without a title

    https://www.solarwinds.com/observability/network and https://www.solarwinds.com/observability/infrastructure have no <title>, so Google invents the link text in results.

  • 2 pages without a meta description

    https://www.solarwinds.com/observability/network and https://www.solarwinds.com/observability/infrastructure have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.solarwinds.com/observability/network, https://www.solarwinds.com/observability/infrastructure and https://www.solarwinds.com/observability/application have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.solarwinds.com/database took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9687
  • 3 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 866 words of copy

    The homepage carries about 866 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Register Now”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Register Now”, “Pricing” and “Request a Quote”.

  • 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: a star rating and 17 trust badges.

Privacy and tracking

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (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.

  • 7 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Netlify

Hiring

Hiring
85 open roles
Teams
Sales (29), G&A (21), R&D (13), MKTG (6)
Job board
greenhouse

Company

Founded
1999
Headquarters
Austin

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on solarwinds.com, including 19 speed issues, 5 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