Website review, no card needed

glassbox.com logo

glassbox.com website review

Visit site (opens in a new tab)Reviewed 28 October 202632 issues · 77 checks

This review found 32 issues worth fixing on glassbox.com, 11 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.7 s2.4 sMay 9Oct 243.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.5 s
May 16, 20262.7 s
May 23, 20262.8 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.8 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.8 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.8 s
Aug 15, 20263.0 s
Aug 22, 20263.2 s
Aug 29, 20263.1 s
Sep 5, 20263.3 s
Sep 12, 20263.2 s
Sep 19, 20263.2 s
Sep 26, 20263.4 s
Oct 3, 20263.4 s
Oct 10, 20263.6 s
Oct 17, 20263.5 s
Oct 24, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
197 ms137 msMay 9Oct 24184 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026147 ms
May 16, 2026144 ms
May 23, 2026144 ms
May 30, 2026145 ms
Jun 6, 2026147 ms
Jun 13, 2026150 ms
Jun 20, 2026155 ms
Jun 27, 2026147 ms
Jul 4, 2026155 ms
Jul 11, 2026155 ms
Jul 18, 2026152 ms
Jul 25, 2026161 ms
Aug 1, 2026155 ms
Aug 8, 2026149 ms
Aug 15, 2026144 ms
Aug 22, 2026145 ms
Aug 29, 2026146 ms
Sep 5, 2026160 ms
Sep 12, 2026185 ms
Sep 19, 2026188 ms
Sep 26, 2026190 ms
Oct 3, 2026186 ms
Oct 10, 2026181 ms
Oct 17, 2026183 ms
Oct 24, 2026184 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

Full-page screenshot of glassbox.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. glassbox.com at 0.4 s0.4 s
  2. glassbox.com at 0.8 s0.8 s
  3. glassbox.com at 1.1 s1.1 s
  4. glassbox.com at 1.5 s1.5 s
  5. glassbox.com at 1.9 s1.9 s
  6. glassbox.com at 2.3 s2.3 s
  7. glassbox.com at 2.6 s2.6 s
  8. glassbox.com at 3.0 s3.0 s

Speed

9 to fix41
  • Use efficient cache lifetimes

    1.9 s · 2.0 MB

    21 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).

  • Reduce unused JavaScript

    2.3 s · 636 KiB

    About 636 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Mobile performance score: 41

    41/100

    Your mobile performance score is 41. 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, Intercom and cookiehub.eu and others), adding 1.1 MB and 1.1 s of main-thread time.

  • Render-blocking requests

    850 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.

  • Google Tag Manager adds 594 ms

    594 ms

    Google Tag Manager costs a phone 594 ms of main-thread work and 679 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.

  • Improve image delivery

    500 ms · 129 KiB

    2 images could be 129 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.

  • Main-thread work: 3.3 s

    A phone's processor spends 3.3 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 293 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    22 KiB

    About 22 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    16 KiB

    Polyfills for old browsers add 16 KiB JavaScript that modern phones do not need.

  • 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: 67 ms

    67 ms

    Your server sent the HTML in 67 ms, well inside Google's 600 ms guideline.

Core Web Vitals

13 to fix33
  • 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.6 s

    11.6 s

    Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Glassbox earns Solutions Partner with certified software de…”.

  • Time to Interactive: 16.3 s

    16.3 s

    The page becomes fully interactive after 16.3 s. Good is under 3.8 s.

  • First Contentful Paint: 5.4 s

    5.4 s

    The first text or image appears after 5.4 s on a phone. Good is under 1.8 s.

  • Speed Index: 6.8 s

    6.8 s

    Visually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 731 ms

    731 ms

    Scripts block taps and scrolling for 731 ms in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.1 s

    3.1 s

    Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 238 ms

    238 ms

    Real visitors wait 238 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 26% slower for real visitors

    +26%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 147 ms to 184 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 33% slower for real visitors

    +33%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.5 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.6 s

    2.6 s

    Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 820 ms

    820 ms

    Real visitors wait 820 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • 5 images without width and height

    5 images have no width and height attributes, so the layout jumps as each one loads.

2 checks passed
  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 5.4 MB in 74 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 74 requests on a phone: media 3.5 MB (4), scripts 1.3 MB (17) and images 327 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.52 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.52 g of CO₂e: 182.2 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

2 to fixGoogle 9696
  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 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.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 84 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 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 128 internal links, 7 external

    The homepage links to 128 pages on glassbox.com and 7 external pages.

8 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Glassbox provides digital customer experience analytics for web and mobile apps. Drive revenue, profitability & loyalty…”.

  • One H1 headline

    Your main headline reads: “Proactive, Preventive and Secure Digital Experiences”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Digital Customer Experience Analytics - Glassbox”.

  • Canonical URL set

    The canonical URL is https://www.glassbox.com/.

  • Structured data in place

    Structured data found: Organization, WebPage 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.glassbox.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.glassbox.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 (957 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.glassbox.com/platform/rapid-response has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.glassbox.com/platform, https://www.glassbox.com/platform/customer-journey-analytics, https://www.glassbox.com/platform/mobile-app-analytics, https://www.glassbox.com/platform/session-replay, https://www.glassbox.com/platform/performance-analytics and https://www.glassbox.com/platform/product-analytics and 9 others have 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 62 found) and read each the way a search engine does.

5 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.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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

    7 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 478 words of copy

    The homepage carries about 478 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get a demo”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Plans & Pricing”, “Contact UsWe'd love to connect with you” and “Contact Sales”.

  • Social proof on the page

    Social proof on the homepage: 73 testimonial or review blocks, 9 customer or partner logos and 1 trust badge.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 28 other companies contacted

    Loading the homepage contacts 28 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 glassbox.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Nuxt
Hosting
Netlify

Company

Founded
2010
Headquarters
Petah Tikva

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on glassbox.com, including 22 speed issues, 1 SEO issue 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25