Website review, no card needed
revuze.it website review
Visit site (opens in a new tab)Reviewed 25 October 202639 issues · 83 checks
This review found 39 issues worth fixing on revuze.it, 12 of them high impact, across 83 checks. The most urgent: render-blocking requests. 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
71CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.0 s |
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 4.4 s |
| Aug 1, 2026 | 4.7 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 3.8 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 178 ms |
| May 9, 2026 | 172 ms |
| May 16, 2026 | 162 ms |
| May 23, 2026 | 151 ms |
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 135 ms |
| Jun 20, 2026 | 153 ms |
| Jun 27, 2026 | 206 ms |
| Jul 4, 2026 | 193 ms |
| Jul 11, 2026 | 227 ms |
| Jul 18, 2026 | 207 ms |
| Jul 25, 2026 | 197 ms |
| Aug 1, 2026 | 217 ms |
| Aug 8, 2026 | 213 ms |
| Aug 15, 2026 | 233 ms |
| Aug 22, 2026 | 275 ms |
| Aug 29, 2026 | 229 ms |
| Sep 5, 2026 | 290 ms |
| Sep 12, 2026 | 343 ms |
| Sep 19, 2026 | 313 ms |
| Sep 26, 2026 | 343 ms |
| Oct 3, 2026 | 252 ms |
| Oct 10, 2026 | 244 ms |
| Oct 17, 2026 | 226 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
Render-blocking requests
2.0 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
4,709 HTML elements
The page has 4,709 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 353 KiBAbout 353 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Cookiebot and Hubspot and others), adding 927 KiB and 513 ms of main-thread time.
Improve image delivery
500 ms · 60 KiB1 image could be 60 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Google Tag Manager adds 369 ms
369 msGoogle Tag Manager costs a phone 369 ms of main-thread work and 503 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.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 255 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
244 KiB5 files are served with short cache lifetimes, so returning visitors download them again (244 KiB).
Minify CSS
7 KiB7 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.
1 checks passed
Server response: 197 ms
197 msYour server sent the HTML in 197 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 CLS: 0.56
0.56For real visitors the layout shifts by 0.56 (75th percentile). Good is under 0.1.
Time to Interactive: 22.8 s
22.8 sThe page becomes fully interactive after 22.8 s. Good is under 3.8 s.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Left animation desktop”.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 223 ms
223 msReal visitors wait 223 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 34% slower for real visitors
+34%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 178 ms to 226 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 310 ms
310 msScripts block taps and scrolling for 310 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 14.2 MB in 93 requests
14.2 MBYour homepage downloads 14.2 MB in 93 requests on a phone: media 9.6 MB (6), scripts 3.2 MB (29) and other files 616 KiB (13). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (90 KiB) is 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.
About 4.0 g of CO₂ per visit
4.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.04 g of CO₂e: 484.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Scrollable region must have keyboard access (10 elements)
Scrollable region must have keyboard access: 10 elements on the page fail this check, rated serious by axe-core.
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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (296 elements)
All page content should be contained by landmarks: 296 elements on the page fail this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 418 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
17 links with vague text
17 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
192 internal links, 13 external
The homepage links to 192 pages on revuze.it and 13 external pages.
7 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “Revuze unifies consumer feedback, social signals, product, care, and sales data into AI market intelligence mapped from…”.
One H1 headline
Your main headline reads: “The AI market intelligence layer for category-to-SKU clarity”.
Title: 56 characters
Your title is a healthy 56 characters: “Revuze | AI Market Intelligence for Brands and Retailers”.
Canonical URL set
The canonical URL is https://www.revuze.it/.
Structured data in place
Structured data found: Article, Organization, Person, WebPage and WebSite.
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.revuze.it/sitemap_index.xml.
AI search readiness
4 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 (5,916 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.revuze.it/llms.txt (195 KiB, 327 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share 2 titles
https://www.revuze.it/industries/cosmetics-fragrances and https://www.revuze.it/industries/personal-care all use the title “Market Intelligence for Beauty & Fragrance Brands”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://www.revuze.it/revuze-ai/agentic-ai, https://www.revuze.it/beauty-beyond-the-surface, https://www.revuze.it/kitchen-grill-report and https://www.revuze.it/revuze-ai have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://www.revuze.it/industries/cosmetics-fragrances and https://www.revuze.it/industries/personal-care use the same meta description. A description written for each page earns more clicks.
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.revuze.it/industries/appliances-vertical, whose canonical is https://www.revuze.it/industries/home-appliances. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://www.revuze.it/industries/cosmetics-fragrances, https://www.revuze.it/industries/appliances-vertical, https://www.revuze.it/industries/personal-care and https://www.revuze.it/industries/home-appliances have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.revuze.it/industries/appliances-vertical took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 88 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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
23 of 27 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 2,396 words of copy
The homepage carries about 2,396 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: “Book a Demo” and “Start a Free Trial”.
40 calls to action
The homepage has 40 calls to action, for example “Learn More”, “Start an Interactive Tour” and “Get My Copy”.
Social proof on the page
Social proof on the homepage: 94 customer or partner logos and 40 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight (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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
13 other companies contacted
Loading the homepage contacts 13 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 revuze.it, 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
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
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 revuze.it, including 22 speed issues, 2 SEO issues and 1 conversion gap. 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.