Website review, no card needed
netezza.com website review
Visit site (opens in a new tab)Reviewed 18 November 202650 issues · 97 checks
This review found 50 issues worth fixing on netezza.com, 26 of them high impact, across 97 checks. The most urgent: use efficient cache lifetimes. 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
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 4.9 s |
| Jun 20, 2026 | 5.1 s |
| Jun 27, 2026 | 5.2 s |
| Jul 4, 2026 | 5.1 s |
| Jul 11, 2026 | 5.2 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 5.0 s |
| Aug 1, 2026 | 5.1 s |
| Aug 8, 2026 | 5.0 s |
| Aug 15, 2026 | 4.9 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 4.9 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.5 s |
| Oct 10, 2026 | 4.4 s |
| Oct 17, 2026 | 4.4 s |
| Oct 24, 2026 | 4.4 s |
| Oct 31, 2026 | 4.4 s |
| Nov 7, 2026 | 4.4 s |
| Nov 14, 2026 | 4.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 291 ms |
| Jun 6, 2026 | 301 ms |
| Jun 13, 2026 | 301 ms |
| Jun 20, 2026 | 301 ms |
| Jun 27, 2026 | 304 ms |
| Jul 4, 2026 | 288 ms |
| Jul 11, 2026 | 287 ms |
| Jul 18, 2026 | 287 ms |
| Jul 25, 2026 | 283 ms |
| Aug 1, 2026 | 291 ms |
| Aug 8, 2026 | 295 ms |
| Aug 15, 2026 | 299 ms |
| Aug 22, 2026 | 311 ms |
| Aug 29, 2026 | 323 ms |
| Sep 5, 2026 | 337 ms |
| Sep 12, 2026 | 352 ms |
| Sep 19, 2026 | 364 ms |
| Sep 26, 2026 | 371 ms |
| Oct 3, 2026 | 378 ms |
| Oct 10, 2026 | 383 ms |
| Oct 17, 2026 | 382 ms |
| Oct 24, 2026 | 378 ms |
| Oct 31, 2026 | 370 ms |
| Nov 7, 2026 | 362 ms |
| Nov 14, 2026 | 359 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
Speed
Use efficient cache lifetimes
4.7 s · 3.5 MB117 files are served with short cache lifetimes, so returning visitors download them again (3.5 MB).
Reduce unused JavaScript
4.0 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Render-blocking requests
5.3 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.3 s.
Reduce unused CSS
1.6 s · 1.9 MBAbout 1.9 MB 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.
IBM Digital Analytics adds 1.3 s
1.3 sIBM Digital Analytics costs a phone 1.3 s of main-thread work and 2.6 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.
Main-thread work: 10.7 s
A phone's processor spends 10.7 s on main-thread work while loading, 5.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (IBM Digital Analytics, o11.tech and Tealium and others), adding 3.4 MB and 2.1 s of main-thread time.
Legacy JavaScript
450 ms · 44 KiBPolyfills for old browsers add 44 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
300 ms · 176 KiB6 images could be 176 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 420 ms. During a long task the page ignores taps.
2,796 HTML elements
The page has 2,796 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Minify CSS
76 KiB76 KiB could be saved by minifying CSS.
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 JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
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: 4.8 s
4.8 sReal visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 761 ms
761 msReal visitors wait 761 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 3.9 s
3.9 sReal visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 29.9 s
29.9 sYour largest element takes 29.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Homepage - IBV - Winning on the agentic frontier - ambient …”.
Speed Index: 15.8 s
15.8 sVisually, the page fills in at 15.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 44.4 s
44.4 sThe page becomes fully interactive after 44.4 s. Good is under 3.8 s.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 291 ms to 359 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.8 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.06
0.06The layout barely moves while loading (CLS 0.06, good is under 0.1).
Images and page weight
Page weight: 7.6 MB in 443 requests
7.6 MBYour homepage downloads 7.6 MB in 443 requests on a phone: scripts 5.0 MB (188), other files 1,006 KiB (176) and images 881 KiB (50). Under 2 MB keeps phones on slow connections fast.
About 2.2 g of CO₂ per visit
2.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.15 g of CO₂e: 258.4 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
Certain ARIA roles must be contained by particular parents (11 elements)
Certain ARIA roles must be contained by particular parents: 11 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (78 elements)
All page content should be contained by landmarks: 78 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails 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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
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 15 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 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 11 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 short (3 characters)
Your title is only 3 characters: “IBM”. Between 30 and 65 characters leaves room to say what you do and for whom.
No XML sitemap
No XML sitemap at https://www.ibm.com/content/sitemap/href-sitemap-index.xml, so Google discovers your pages only by following links.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
23 internal links, 17 external
The homepage links to 23 pages on netezza.com and 17 external pages.
6 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “For more than a century, IBM has been a global technology innovator, leading advances in AI, automation and hybrid clou…”.
One H1 headline
Your main headline reads: “Bring agentic AI value into focus”.
Canonical URL set
The canonical URL is https://www.ibm.com/us-en.
Structured data in place
Structured data found: Corporation 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.
AI search readiness
No llms.txt
There is no https://www.ibm.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (812 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.ibm.com/campaign/digital-sovereignty-index is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.ibm.com/campaign/digital-sovereignty-index has no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.ibm.com/thought-leadership/institute-business-value/report/agentic-ai-learning, whose canonical is https://www.ibm.com/thought-leadership/institute-business-value/en-us/report/agentic-ai-learning. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page slow to respond
https://www.ibm.com/new/announcements/ibm-concert-platform-advances-the-path-to-cross-domain-agentic-it-operations took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 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.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://id.rlcdn.com/464526.gif.
9 small tap targets
9 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 third-party cookies
4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 808 words of copy
The homepage carries about 808 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Start shaping tomorrow”.
1 short form
A short form (0 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Ads and 4 mores (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.
42 cookies set on arrival
42Opening the homepage sets 42 cookies, 1 of them by other companies (measured from a US location before any click).
62 other companies contacted
Loading the homepage contacts 62 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: TrustArc
A consent management tool (TrustArc) 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 netezza.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Microsoft Clarity
Company
- Founded
- 1999
- Headquarters
- Marlborough
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on netezza.com, including 24 speed issues, 3 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.