Website review, no card needed
glair.ai website review
Visit site (opens in a new tab)Reviewed 8 November 202640 issues · 85 checks
This review found 40 issues worth fixing on glair.ai, 13 of them high impact, across 85 checks. The most urgent: mobile performance score: 36. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 114 ms |
| May 30, 2026 | 117 ms |
| Jun 6, 2026 | 119 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 120 ms |
| Jun 27, 2026 | 132 ms |
| Jul 4, 2026 | 132 ms |
| Jul 11, 2026 | 215 ms |
| Jul 18, 2026 | 226 ms |
| Jul 25, 2026 | 205 ms |
| Aug 1, 2026 | 193 ms |
| Aug 8, 2026 | 126 ms |
| Aug 15, 2026 | 122 ms |
| Aug 22, 2026 | 101 ms |
| Oct 10, 2026 | 124 ms |
| Oct 17, 2026 | 129 ms |
| Oct 24, 2026 | 150 ms |
| Oct 31, 2026 | 162 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
Mobile performance score: 36
36/100Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
150 ms · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (website-files.com, Google Tag Manager and cloudfront.net and others), adding 4.2 MB and 486 ms of main-thread time.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 758 ms. During a long task the page ignores taps.
website-files.com adds 266 ms
266 mswebsite-files.com costs a phone 266 ms of main-thread work and 3.3 MB 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.
Improve image delivery
300 ms · 156 KiB16 images could be 156 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.
Render-blocking requests
400 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
Reduce unused CSS
300 ms · 88 KiBAbout 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 170 ms
170 msGoogle Tag Manager costs a phone 170 ms of main-thread work and 299 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.
Adobe TypeKit adds 7 ms
7 msAdobe TypeKit costs a phone 7 ms of main-thread work and 346 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
150 ms · 17 KiB4 files are served with short cache lifetimes, so returning visitors download them again (17 KiB).
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 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.
Largest Contentful Paint: 11.5 s
11.5 sYour largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “GLChat Website Interface”.
Time to Interactive: 29.7 s
29.7 sThe page becomes fully interactive after 29.7 s. Good is under 3.8 s.
Speed Index: 13.4 s
13.4 sVisually, the page fills in at 13.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 832 ms
832 msScripts block taps and scrolling for 832 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 35% slower for real visitors
+35%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 114 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.101
0.101The layout shifts by 0.101 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 187 ms
187 msReal visitors wait 187 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user TTFB: 668 ms
668 msReal visitors wait 668 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 7.0 MB in 139 requests
7.0 MBYour homepage downloads 7.0 MB in 139 requests on a phone: scripts 3.2 MB (59), images 3.1 MB (41) and fonts 595 KiB (27). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.
An image on the first screen is lazy-loaded
6989ba601943ed7a10a99598_GLChat-Laptop.svg 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).
2 images below the first screen load straight away
2 images further down the page (619 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (58 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 2.0 g of CO₂ per visit
2.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.00 g of CO₂e: 239.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
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”.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (19 elements)
All page content should be contained by landmarks: 19 elements on the page fail 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.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
2 checks passed
Every image has alt text
All 114 images in the HTML carry an alt attribute.
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("/")”.
No XML sitemap
No XML sitemap at https://glair.ai/sitemap.xml, so Google discovers your pages only by following links.
32 internal links, 72 external
The homepage links to 32 pages on glair.ai and 72 external pages.
6 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “GLAIR provides enterprise AI solutions through GLChat and AI consulting. Focused on practical outcomes, data security, …”.
One H1 headline
Your main headline reads: “GLChat”.
Title: 46 characters
Your title is a healthy 46 characters: “GLAIR | Enterprise AI Platform & AI Consulting”.
Canonical URL set
The canonical URL is https://glair.ai/.
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.
AI search readiness
No llms.txt
There is no https://glair.ai/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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (405 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages are broken
Your homepage links to https://glair.ai/consulting/recommendation-system and https://glair.ai/retail-execution, which answer with an error. Visitors hit a dead end and search engines drop them.
12 links to non-canonical URLs
Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://glair.ai/en-glchat, whose canonical is //en-glchat. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages share a meta description
https://glair.ai/en-glchat and https://glair.ai/paperless use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://glair.ai/contact-us has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://glair.ai/contact-us has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
1 page slow to respond
https://glair.ai/privacy-policy took over 3 s to send its HTML from our server.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Every page has a meta description
All 12 pages that loaded have a meta description.
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.
Every page has a title
All 12 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 execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'.”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
33 of 34 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 384 words of copy
The homepage carries about 384 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”.
5 calls to action
The homepage has 5 calls to action, for example “CONTACT US”, “LEARN MORE” and “Contact Us”.
Social proof on the page
Social proof on the homepage: 10 testimonial or review blocks, 75 customer or partner logos and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Hotjar.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
4 cookies set on arrival
4Opening the homepage sets 4 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.
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 glair.ai, 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 | Hotjar
- Hosting
- Webflow
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on glair.ai, including 21 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.