Programmable

Website review, no card needed

now.gg logo

now.gg website review

Visit site (opens in a new tab)Reviewed 11 October 202637 issues · 81 checks

This review found 37 issues worth fixing on now.gg, 7 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.

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

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

Site score

77C

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.3 s1.8 sApr 18Oct 31.9 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20262.2 s
Apr 25, 20262.1 s
May 2, 20262.1 s
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.2 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
300 ms250 msApr 18Oct 3288 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026268 ms
Apr 25, 2026269 ms
May 2, 2026270 ms
May 9, 2026272 ms
May 16, 2026272 ms
May 23, 2026271 ms
May 30, 2026268 ms
Jun 6, 2026264 ms
Jun 13, 2026259 ms
Jun 20, 2026256 ms
Jun 27, 2026259 ms
Jul 4, 2026264 ms
Jul 11, 2026274 ms
Jul 18, 2026279 ms
Jul 25, 2026280 ms
Aug 1, 2026281 ms
Aug 8, 2026278 ms
Aug 15, 2026277 ms
Aug 22, 2026275 ms
Aug 29, 2026277 ms
Sep 5, 2026284 ms
Sep 12, 2026289 ms
Sep 19, 2026294 ms
Sep 26, 2026293 ms
Oct 3, 2026288 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

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

How it loaded on a phone

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

Speed

8 to fix56

  • Main-thread work: 8.1 s

    A phone's processor spends 8.1 s on main-thread work while loading, 4.0 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 (Rubicon Project, Amazon Ads and aditude.io and others), adding 1.4 MB and 1.7 s of main-thread time.

  • Reduce unused JavaScript

    560 ms · 605 KiB

    About 605 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 560 ms faster on a phone.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56 (desktop: 59). Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    743 KiB

    158 files are served with short cache lifetimes, so returning visitors download them again (743 KiB).

  • Rubicon Project adds 584 ms

    584 ms

    Rubicon Project costs a phone 584 ms of main-thread work and 165 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.

  • 20 long tasks on the main thread

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

  • Amazon Ads adds 252 ms

    252 ms

    Amazon Ads costs a phone 252 ms of main-thread work and 122 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.

  • Legacy JavaScript

    150 ms · 39 KiB

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

  • Improve image delivery

    14 KiB

    3 images could be 14 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

    5 ms

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

Core Web Vitals

7 to fix67

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

  • Time to Interactive: 45.4 s

    45.4 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

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

  • Real-user INP: 294 ms

    294 ms

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

  • Speed Index: 5.5 s

    5.5 s

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

  • Largest Contentful Paint: 3.8 s

    3.8 s

    Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

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

7 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 CLS: 0.10

    0.10

    For real visitors the layout shifts by 0.10 (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.

  • Real-user TTFB: 366 ms

    366 ms

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

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

    -10%

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

  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81

  • Page weight: 3.4 MB in 1,099 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 1,099 requests on a phone: scripts 2.1 MB (88), other files 669 KiB (540) and images 394 KiB (308). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    oval-red.8ef011b6.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).

  • About 1.0 g of CO₂ per visit

    0.97 g

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

2 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9193

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (78 elements)

    All page content should be contained by landmarks: 78 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 43 links without text

    43 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h1 → h5), which makes the page harder to scan with a screen reader.

2 checks passed

  • Every image has alt text

    All 137 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9291

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 14 H1 headlines

    There are 14 <h1> headlines (“Top Games”, “Popular Games” and “More Games”). One clear main headline is easier for people and search engines.

  • 111 internal links, 1 external

    The homepage links to 111 pages on now.gg and 1 external page.

6 checks passed

  • Meta description: 132 characters

    Your meta description is 132 characters: “Play your favorite games online for free. No downloads or installs. Enjoy non-stop gaming on any device at a single cli…”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Play Online Games for Free | now.gg Mobile Cloud”.

  • Canonical URL set

    The canonical URL is https://now.gg/.

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

AI search readiness

1 to fix88

  • 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://now.gg/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 (717 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix75

  • 15 linked pages hidden from search

    https://now.gg/apps/valvolex/52100/rally-racer-dirt.html, https://now.gg/apps/rivals/19911/rivals.html, https://now.gg/apps/Grow-a-Garden/19903/Grow-a-Garden.html, https://now.gg/apps/dandys-world-alpha/19929/dandys-world-alpha.html, https://now.gg/apps/the-strongest-battle/19913/the-strongest-battle.html and https://now.gg/apps/99-Nights/19902/99-Nights.html and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 15 pages share a title

    https://now.gg/apps/valvolex/52100/rally-racer-dirt.html, https://now.gg/apps/rivals/19911/rivals.html, https://now.gg/apps/Grow-a-Garden/19903/Grow-a-Garden.html, https://now.gg/apps/dandys-world-alpha/19929/dandys-world-alpha.html, https://now.gg/apps/the-strongest-battle/19913/the-strongest-battle.html and https://now.gg/apps/99-Nights/19902/99-Nights.html and 9 others all use the title “Something went wrong | now.gg”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://now.gg/apps/valvolex/52100/rally-racer-dirt.html, https://now.gg/apps/rivals/19911/rivals.html, https://now.gg/apps/Grow-a-Garden/19903/Grow-a-Garden.html, https://now.gg/apps/dandys-world-alpha/19929/dandys-world-alpha.html, https://now.gg/apps/the-strongest-battle/19913/the-strongest-battle.html and https://now.gg/apps/99-Nights/19902/99-Nights.html and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://now.gg/apps/valvolex/52100/rally-racer-dirt.html, https://now.gg/apps/rivals/19911/rivals.html, https://now.gg/apps/Grow-a-Garden/19903/Grow-a-Garden.html, https://now.gg/apps/dandys-world-alpha/19929/dandys-world-alpha.html, https://now.gg/apps/the-strongest-battle/19913/the-strongest-battle.html and https://now.gg/apps/99-Nights/19902/99-Nights.html 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 87 found) and read each the way a search engine does.

3 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 title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 3588

  • 38 third-party cookies

    38 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“The Topics API is deprecated and will be removed in a future release.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

2 checks passed

  • Tap targets are thumb-sized

    37 of 46 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

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

  • Only about 226 words

    The homepage has only about 226 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

3 checks passed

  • 1 call to action

    The homepage has 1 call to action, for example “Get in Touch”.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 1 more (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.

  • 29 cookies set on arrival

    29

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

  • 72 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on now.gg, including 15 speed issues, 2 SEO 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