Programmable

Website review, no card needed

grid.gg logo

grid.gg website review

Visit site (opens in a new tab)Reviewed 18 October 202612 issues · 79 checks

This review found 12 issues worth fixing on grid.gg, 2 of them high impact, across 79 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Site score

93A

Closest competitors among SaaS websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.2 s1.5 sApr 25Oct 101.6 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.1 s
May 2, 20262.0 s
May 9, 20262.0 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
143 ms99 msApr 25Oct 10105 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026117 ms
May 2, 2026112 ms
May 9, 2026129 ms
May 16, 2026138 ms
May 23, 2026129 ms
May 30, 2026136 ms
Jun 6, 2026136 ms
Jun 13, 2026126 ms
Jun 20, 2026134 ms
Jun 27, 2026134 ms
Jul 4, 2026134 ms
Jul 11, 2026136 ms
Jul 18, 2026137 ms
Jul 25, 2026134 ms
Aug 1, 2026123 ms
Aug 8, 2026121 ms
Aug 15, 2026113 ms
Aug 22, 2026113 ms
Aug 29, 2026111 ms
Sep 5, 2026104 ms
Sep 12, 2026111 ms
Sep 19, 2026112 ms
Sep 26, 2026112 ms
Oct 3, 2026112 ms
Oct 10, 2026105 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

grid.gg (opens in a new tab)
Full-page screenshot of grid.gg (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

grid.gg does not allow embedding, so this is Google's rendering of the page.

Speed

99

  • Legacy JavaScript

    150 ms · 12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Render-blocking requests

    100 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 55 ms. During a long task the page ignores taps.

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

3 checks passed

  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99 (desktop: 100). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 200 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

2 to fix100

  • 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 TTFB: 861 ms

    861 ms

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

  • Tap response (INP) held steady for real visitors

    -5%

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

11 checks passed

  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 106 ms

    106 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Largest content (LCP) got 21% faster for real visitors

    -21%

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

  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “The official esports live data behind sportsbooks, predicti…”.

  • Speed Index: 2.3 s

    2.3 s

    Visually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Time to Interactive: 2.2 s

    2.2 s

    The page is fully interactive after 2.2 s.

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 1.0 s

    1.0 s

    The first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 3 ms

    3 ms

    Scripts block the page for only 3 ms while loading. Good is under 200 ms.

Images and page weight

100

  • About 0.07 g of CO₂ per visit

    0.07 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.07 g of CO₂e: 8.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 checks passed

  • Page weight: 257 KiB in 37 requests

    257 KiB

    Your homepage downloads 257 KiB in 37 requests on a phone: scripts 140 KiB (15), images 55 KiB (15) and other files 40 KiB (4). That is a lean page.

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

  • 9 text elements with low contrast

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed

  • Every image has alt text

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

SEO

Google 100100

  • 46 internal links, 5 external

    The homepage links to 46 pages on grid.gg and 5 external pages.

8 checks passed

  • Meta description: 160 characters

    Your meta description is 160 characters: “An official esports live data platform: match data, widgets, and AI-powered insights for sportsbooks, media, and predic…”.

  • One H1 headline

    Your main headline reads: “The official esports live data behind sportsbooks, prediction markets, and media.”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “GRID: An Official Esports Live Data Platform”.

  • Canonical URL set

    The canonical URL is https://www.grid.gg/.

  • Structured data in place

    Structured data found: Organization.

  • 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.grid.gg/sitemap.xml.

AI search readiness

100

  • No llms.txt

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

Other pages

100

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 22 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

2 to fixGoogle 9687

  • 3 small tap targets

    3 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

1 to fix94

  • No Content-Security-Policy

    No Content-Security-Policy header, the main browser-side defence against injected scripts.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed

  • Served over HTTPS

    The homepage is served over HTTPS (grid.gg).

  • Valid certificate (51 days left)

    The certificate from Let's Encrypt · YR2 verifies for grid.gg and is valid for another 51 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://grid.gg redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

  • All 26 links work

    All 26 links checked from your homepage (23 internal, 3 external) answered without errors.

Domain and trust

  • No CAA record

    grid.gg has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Content and conversion

4 to fix67

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • A 10-field form

    Your longest form asks for 10 fields (7 required). Every extra field lowers completion.

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

    The homepage carries about 663 words of visible text.

2 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “LEARN MORE”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Learn More” and “Learn More →”.

Email authentication

1 to fix70

  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be grid.gg is still delivered. Reports are on, so moving to quarantine is the next step.

  • Email authentication score: 70/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

2 checks passed

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.google.com include:mailgun.org a mx ~all”.

  • DKIM signing found

    A DKIM key is published (selector “google”, “s1” and “mail”), so receivers can verify mail really came from you.

Privacy and tracking

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

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Framework
Next.js
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This free review found 12 issues on grid.gg, including 2 speed issues and 4 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