Website review, no card needed
glasswallsolutions.com website review
Visit site (opens in a new tab)Reviewed 5 November 202630 issues · 74 checks
This review found 30 issues worth fixing on glasswallsolutions.com, 10 of them high impact, across 74 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.4 s |
| May 23, 2026 | 4.6 s |
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 4.9 s |
| Jun 20, 2026 | 4.9 s |
| Jun 27, 2026 | 4.4 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 3.9 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 4.7 s |
| Sep 12, 2026 | 4.7 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.7 s |
| Oct 17, 2026 | 4.6 s |
| Oct 24, 2026 | 4.9 s |
| Oct 31, 2026 | 4.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 439 ms |
| May 23, 2026 | 397 ms |
| May 30, 2026 | 381 ms |
| Jun 6, 2026 | 331 ms |
| Jun 13, 2026 | 303 ms |
| Jun 20, 2026 | 309 ms |
| Jun 27, 2026 | 285 ms |
| Jul 4, 2026 | 276 ms |
| Jul 11, 2026 | 271 ms |
| Jul 18, 2026 | 252 ms |
| Jul 25, 2026 | 197 ms |
| Aug 1, 2026 | 175 ms |
| Aug 8, 2026 | 192 ms |
| Aug 15, 2026 | 219 ms |
| Aug 22, 2026 | 243 ms |
| Aug 29, 2026 | 269 ms |
| Sep 5, 2026 | 255 ms |
| Sep 12, 2026 | 243 ms |
| Sep 19, 2026 | 202 ms |
| Sep 26, 2026 | 187 ms |
| Oct 3, 2026 | 187 ms |
| Oct 10, 2026 | 199 ms |
| Oct 17, 2026 | 178 ms |
| Oct 24, 2026 | 199 ms |
| Oct 31, 2026 | 168 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
Render-blocking requests
1.0 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.0 s.
Improve image delivery
300 ms · 3.8 MB8 images could be 3.8 MB 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.
Use efficient cache lifetimes
150 ms · 2.9 MB17 files are served with short cache lifetimes, so returning visitors download them again (2.9 MB).
8 third-party services on the page
8 third-party services load with your homepage (website-files.com, consentpro.com and Google Tag Manager and others), adding 8.8 MB and 334 ms of main-thread time.
Mobile performance score: 85
85/100Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.
website-files.com adds 80 ms
80 mswebsite-files.com costs a phone 80 ms of main-thread work and 8.5 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.
Reduce unused CSS
450 ms · 72 KiBAbout 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused JavaScript
323 KiBAbout 323 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 884 ms 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 206 ms. During a long task the page ignores taps.
Legacy JavaScript
27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need.
Minify JavaScript
8 KiB8 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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 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.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.8 s
3.8 sReal visitors see the first content after 3.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.9 s
2.9 sReal visitors wait 2.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 10.7 s
10.7 sThe page becomes fully interactive after 10.7 s. Good is under 3.8 s.
Total Blocking Time: 361 ms
361 msScripts block taps and scrolling for 361 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 2.9 s
2.9 sYour largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
18 images without width and height
18 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.4 s to 4.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 162 ms
162 msReal visitors wait 162 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 56% faster for real visitors
-56%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 439 ms to 168 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.098
0.098The layout barely moves while loading (CLS 0.098, good is under 0.1).
First Contentful Paint: 1.0 s
1.0 sThe first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.
Speed Index: 1.4 s
1.4 sVisually, the page fills in at 1.4 s (Speed Index), inside the 3.4 s “good” threshold.
Images and page weight
Page weight: 9.5 MB in 117 requests
9.5 MBYour homepage downloads 9.5 MB in 117 requests on a phone: images 5.5 MB (25), media 2.8 MB (4) and scripts 937 KiB (48). Under 2 MB keeps phones on slow connections fast.
About 2.7 g of CO₂ per visit
2.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.70 g of CO₂e: 324.3 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
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (1 element).
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with role="none" or role="presentation" have conflicts
Elements with role="none" or role="presentation" have conflicts (2 elements).
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 88 images in the HTML carry an alt attribute.
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 31 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“Stop malwarebefore it reaches your network”, “Who We Protect” and “Join ourglobal partner network”). One clear main headline is easier for people and search engines.
136 internal links, 32 external
The homepage links to 136 pages on glasswallsolutions.com and 32 external pages.
6 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Stop file-based threats before they execute. Glasswall CDR rebuilds every file to a safe, clean state without disruptin…”.
Title: 51 characters
Your title is a healthy 51 characters: “Glasswall | Zero Trust File Security Powered by CDR”.
Canonical URL set
The canonical URL is https://www.glasswall.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.glasswall.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.
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.
llms.txt published
The site publishes https://www.glasswall.com/llms.txt (20 KiB, 106 links), a plain-text guide to the site for AI tools.
Other pages
Your server turned our page checks away
15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.
Best practices
1 broken image
1 image failed to load on a phone, for example https://www.glasswall.com/favicon.ico.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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.
Only about 37 words
The homepage has only about 37 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
4 checks passed
9 calls to action
The homepage has 9 calls to action, for example “Contact us”, “Book a demo” and “Talk to us”.
6 short forms
6 short forms (7 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 14 testimonial or review blocks, 13 customer or partner logos and 6 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
1 other company contacted
Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 glasswallsolutions.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
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Hiring
- Hiring
- 2 open roles
- Job board
- careers page
- Careers page
- careers.glasswall.com (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on glasswallsolutions.com, including 17 speed issues, 2 SEO issues and 5 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.