Website review, no card needed
infinidat.com website review
Visit site (opens in a new tab)Reviewed 4 November 202647 issues · 87 checks
This review found 47 issues worth fixing on infinidat.com, 17 of them high impact, across 87 checks. The most urgent: improve image delivery. 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
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.2 s |
| Oct 31, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 129 ms |
| May 23, 2026 | 149 ms |
| May 30, 2026 | 173 ms |
| Jun 6, 2026 | 161 ms |
| Jun 13, 2026 | 161 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 144 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 130 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 119 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 132 ms |
| Aug 29, 2026 | 137 ms |
| Sep 5, 2026 | 144 ms |
| Sep 12, 2026 | 136 ms |
| Sep 19, 2026 | 138 ms |
| Sep 26, 2026 | 131 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 125 ms |
| Oct 17, 2026 | 121 ms |
| Oct 24, 2026 | 124 ms |
| Oct 31, 2026 | 124 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
1.7 s
3.5 s
5.2 s
7.0 s
8.7 s
10.4 s
12.2 s
13.9 s
Speed
Improve image delivery
2.9 s · 1.3 MB9 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.
Reduce unused JavaScript
1.4 s · 340 KiBAbout 340 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Render-blocking requests
1.6 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Use efficient cache lifetimes
1.0 s · 170 KiB27 files are served with short cache lifetimes, so returning visitors download them again (170 KiB).
Mobile performance score: 45
45/100Your mobile performance score is 45. 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 (Google Tag Manager, Osano CMP and 6sc.co and others), adding 835 KiB and 1.1 s of main-thread time.
Google Tag Manager adds 529 ms
529 msGoogle Tag Manager costs a phone 529 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.
Legacy JavaScript
350 ms · 27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 235 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 69 KiBAbout 69 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Minify JavaScript
23 KiB23 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.
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: 17 ms
17 msYour server sent the HTML in 17 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.2 s
4.2 sReal visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 25.8 s
25.8 sYour largest element takes 25.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SKYROCKETING STORAGE COSTS?”. Most of its time is element render delay (13.1 s).
Speed Index: 16.0 s
16.0 sVisually, the page fills in at 16.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 26.2 s
26.2 sThe page becomes fully interactive after 26.2 s. Good is under 3.8 s.
First Contentful Paint: 4.6 s
4.6 sThe first text or image appears after 4.6 s on a phone. Good is under 1.8 s.
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
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.
Total Blocking Time: 456 ms
456 msScripts block taps and scrolling for 456 ms in total while the page loads. Good is under 200 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
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.2 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 129 ms to 124 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.038
0.038The layout barely moves while loading (CLS 0.038, good is under 0.1).
Images and page weight
9 images far larger than shown
1.4 MB9 images are downloaded at several times the size a phone draws them, for example Storage Capacity 4.jpg at 1,917 px wide, shown at 390 px. Resized copies would save about 1.4 MB.
1 image over 500 KB
Storage Capacity 4.jpg weighs 492 KiB. On a phone connection a single image that size takes seconds.
Page weight: 3.5 MB in 186 requests
3.5 MBYour homepage downloads 3.5 MB in 186 requests on a phone: images 1.9 MB (47), scripts 1.0 MB (63) and fonts 418 KiB (5). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (1.9 MB) 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.
An image on the first screen is lazy-loaded
Storage Capacity 4.jpg 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).
4 images below the first screen load straight away
4 images further down the page (475 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
1.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 120.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
43 tap targets too small
43 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
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.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 H1 headlines
There are 4 <h1> headlines (“LENOVO ACQUIRES INFINIDAT”, “PUT CYBER CRIMINALS ON DEFENSE” and “SKYROCKETING STORAGE COSTS?”). One clear main headline is easier for people and search engines.
29 links with vague text
29 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Meta description is long (241 characters)
Your meta description is 241 characters; Google truncates after about 160, so the end of your pitch is cut.
191 internal links, 27 external
The homepage links to 191 pages on infinidat.com and 27 external pages.
6 checks passed
Title: 45 characters
Your title is a healthy 45 characters: “Enterprise Data & Cloud Solutions | Infinidat”.
Canonical URL set
The canonical URL is https://www.infinidat.com/en.
Structured data in place
Structured data found: Organization and WebSite.
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://www.infinidat.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.infinidat.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 (1,329 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.infinidat.com/en/cost-effective-storage-solutions and https://www.infinidat.com/industry-solutions all use the title “Data Storage Industry Solutions | Infinidat”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://www.infinidat.com/en/next-gen-data-protection-and-recovery, https://www.infinidat.com/en/products-technology/infinibox-ssa, https://www.infinidat.com/en/node/2872, https://www.infinidat.com/guarantees, https://www.infinidat.com/en/artificial-intelligence and https://www.infinidat.com/en/cyber-resilience have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://www.infinidat.com/products-technology/infiniverse and https://www.infinidat.com/products-technology/infinibox use the same meta description. A description written for each page earns more clicks.
8 links to non-canonical URLs
Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.infinidat.com/products-technology, whose canonical is https://www.infinidat.com/en/products-technology. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.infinidat.com/guarantees has 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 57 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 broken image
1 image failed to load on a phone, for example https://s.ml-attr.com/getuid?https%3a%2f%2fattr.ml-api.io%2f%3fdomain%3dwww.infinidat.com%26pId%3d%24UID.
9 small tap targets
9 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://www.infinidat.com' has been blocke…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 1,187 words of copy
The homepage carries about 1,187 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: “Learn More”.
37 calls to action
The homepage has 37 calls to action, for example “LEARN MORE”, “Contact Us” and “Request a Demo”.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
23 other companies contacted
Loading the homepage contacts 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Osano
A consent management tool (Osano) 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 infinidat.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
- Drupal
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Hiring
- Hiring
- 25 open roles
- Job board
- careers page
Company
- Founded
- 2011
- Headquarters
- Herzliya
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on infinidat.com, including 19 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.