Website review, no card needed

g3solar.com logo

g3solar.com website review

Visit site (opens in a new tab)Reviewed 25 October 202618 issues · 59 checks

This review found 18 issues worth fixing on g3solar.com, 9 of them high impact, across 59 checks. The most urgent: improve image delivery. 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

Full-page screenshot of g3solar.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. g3solar.com at 0.5 s0.5 s
  2. g3solar.com at 0.9 s0.9 s
  3. g3solar.com at 1.4 s1.4 s
  4. g3solar.com at 1.8 s1.8 s
  5. g3solar.com at 2.3 s2.3 s
  6. g3solar.com at 2.7 s2.7 s
  7. g3solar.com at 3.2 s3.2 s
  8. g3solar.com at 3.6 s3.6 s

Speed

3 to fix70
  • Improve image delivery

    3.0 s · 1.6 MB

    4 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.

  • Render-blocking requests

    1.1 s

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Mobile performance score: 70

    70/100

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

  • 2 long tasks on the main thread

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Cloudflare and Google Fonts), adding 44 KiB and 11 ms of main-thread time.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

  • Use efficient cache lifetimes

    4 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (4 KiB).

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

4 to fix66
  • Largest Contentful Paint: 10.5 s

    10.5 s

    Your largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Provider: Pixmove Games RTP: 95% Volatility: Low Max Win: x…”.

  • Time to Interactive: 10.5 s

    10.5 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 5 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Speed Index: 3.0 s

    3.0 s

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

  • Cumulative Layout Shift: 0.055

    0.055

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

4 to fix40
  • 3 images over 500 KB

    3 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    1.3 MB

    3 images are downloaded at several times the size a phone draws them, for example bonus-popup.png at 1,024 px wide, shown at 277 px. Resized copies would save about 1.3 MB.

  • Page weight: 2.8 MB in 15 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 15 requests on a phone: images 2.7 MB (6), fonts 32 KiB (1) and scripts 22 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

    4 images (2.1 MB) are 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 0.8 g of CO₂ per visit

    0.78 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 9494
  • 5 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • 11 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 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 10091
  • Meta description is long (163 characters)

    Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 2 problems

    Structured data found (Article, BreadcrumbList, FAQPage and Organization) but with 2 problems, for example “Article: missing datePublished”.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 9 internal links, 12 external

    The homepage links to 9 pages on g3solar.com and 12 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Falling Pickaxe Casino Game by Pixmove Games”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Falling Pickaxe Casino Game by Pixmove Games | 95% RTP Review”.

  • Canonical URL set

    The canonical URL is https://www.g3solar.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.g3solar.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.g3solar.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 contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,526 words), so crawlers that don't run JavaScript still read it.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    20 of 22 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 form on the homepage

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

  • About 2,504 words of copy

    The homepage carries about 2,504 words of visible text.

5 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Demo”, “Demo Simulator” and “Go to Demo Player”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 16 customer or partner logos and a star rating.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • 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

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

  • 3 other companies contacted

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

Upkeep, stack and company

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on g3solar.com, including 7 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

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