Website review, no card needed
getguru.com website review
Visit site (opens in a new tab)Reviewed 2 November 202631 issues · 81 checks
This review found 31 issues worth fixing on getguru.com, 9 of them high impact, across 81 checks. The most urgent: fails Core Web Vitals for real visitors. 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
73CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.5 s |
| May 23, 2026 | 4.7 s |
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.7 s |
| Jun 13, 2026 | 4.6 s |
| Jun 20, 2026 | 4.4 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.4 s |
| Jul 11, 2026 | 4.5 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.6 s |
| Aug 1, 2026 | 4.6 s |
| Aug 8, 2026 | 4.8 s |
| Aug 15, 2026 | 4.8 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.8 s |
| Oct 3, 2026 | 4.8 s |
| Oct 10, 2026 | 4.7 s |
| Oct 17, 2026 | 4.6 s |
| Oct 24, 2026 | 4.5 s |
| Oct 31, 2026 | 4.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 227 ms |
| May 23, 2026 | 243 ms |
| May 30, 2026 | 265 ms |
| Jun 6, 2026 | 272 ms |
| Jun 13, 2026 | 274 ms |
| Jun 20, 2026 | 274 ms |
| Jun 27, 2026 | 277 ms |
| Jul 4, 2026 | 288 ms |
| Jul 11, 2026 | 292 ms |
| Jul 18, 2026 | 290 ms |
| Jul 25, 2026 | 293 ms |
| Aug 1, 2026 | 288 ms |
| Aug 8, 2026 | 281 ms |
| Aug 15, 2026 | 282 ms |
| Aug 22, 2026 | 277 ms |
| Aug 29, 2026 | 278 ms |
| Sep 5, 2026 | 272 ms |
| Sep 12, 2026 | 263 ms |
| Sep 19, 2026 | 270 ms |
| Sep 26, 2026 | 252 ms |
| Oct 3, 2026 | 252 ms |
| Oct 10, 2026 | 250 ms |
| Oct 17, 2026 | 247 ms |
| Oct 24, 2026 | 250 ms |
| Oct 31, 2026 | 239 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Main-thread work: 7.3 s
A phone's processor spends 7.3 s on main-thread work while loading, 4.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Wistia, reddit and website-files.com and others), adding 1.6 MB and 2.1 s of main-thread time.
Reduce unused JavaScript
300 ms · 805 KiBAbout 805 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
150 ms · 624 KiB33 files are served with short cache lifetimes, so returning visitors download them again (624 KiB).
Wistia adds 619 ms
619 msWistia costs a phone 619 ms of main-thread work and 466 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.
Render-blocking requests
450 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
reddit adds 362 ms
362 msreddit costs a phone 362 ms of main-thread work and 37 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.
website-files.com adds 252 ms
252 mswebsite-files.com costs a phone 252 ms of main-thread work and 593 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.
1,635 HTML elements
The page has 1,635 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 232 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need.
Reduce unused CSS
28 KiBAbout 28 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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 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.3 s
4.3 sReal visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.5 s
4.5 sReal visitors see the first content after 4.5 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 23.7 s
23.7 sThe page becomes fully interactive after 23.7 s. Good is under 3.8 s.
Speed Index: 10.8 s
10.8 sVisually, the page fills in at 10.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Real-user INP: 244 ms
244 msReal visitors wait 244 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest Contentful Paint: 3.4 s
3.4 sYour largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Stop running your business on confidently wr🚫ng AI.”. Most of its time is element render delay (2.3 s).
31 images without width and height
31 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 227 ms to 239 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.5 s to 4.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 650 ms
650 msReal visitors wait 650 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 229 requests
3.2 MBYour homepage downloads 3.2 MB in 229 requests on a phone: scripts 2.3 MB (75), fonts 566 KiB (15) and HTML 105 KiB (5). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 107.9 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
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
button, link, and menuitem elements do not have accessible names.
button, link, and menuitem elements do not have accessible names. (6 elements).
1 checks passed
Every image has alt text
All 52 images in the HTML carry an alt attribute.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
72 internal links, 16 external
The homepage links to 72 pages on getguru.com and 16 external pages.
7 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Stop running your business on confidently wrong AI. Guru structures, governs, and continuously improves your knowledge—…”.
One H1 headline
Your main headline reads: “Stop running your business on confidently wr🚫ng AI.”.
Title: 46 characters
Your title is a healthy 46 characters: “The Governed Knowledge Layer for Enterprise AI”.
Canonical URL set
The canonical URL is https://www.getguru.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.getguru.com/sitemap.xml.
AI search readiness
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.
No llms.txt
There is no https://www.getguru.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.
2 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 (714 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 56 found) and read each the way a search engine does.
7 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.
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
3 broken images
3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97086404&tm=gtm002&Ver=2&mid=8dae924d-cc86-476b-8686-8b79569f69b4&bo=3&sid=dc3c33f0d68e11f1a588ad1235ccc32e&vid=dc3c5af0d68e11f1bd5283fe344e425d&vids=0&msclkid=N&pi=91.
11 small tap targets
11 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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 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 473 words of copy
The homepage carries about 473 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: “Talk to sales”.
8 calls to action
The homepage has 8 calls to action, for example “Download Now >”, “Pricing” and “Talk to sales”.
Social proof on the page
Social proof on the homepage: 12 testimonial or review blocks, 6 customer or partner logos, a star rating and 52 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Analytics, Google Tag Manager and HubSpot and 5 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
29 cookies set on arrival
29Opening the homepage sets 29 cookies (measured from a US location before any click).
63 other companies contacted
Loading the homepage contacts 63 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) 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 getguru.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
- Webflow
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Webflow
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on getguru.com, including 20 speed issues, 1 SEO issue 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.