Website review, no card needed

7piratesgames.com logo

7piratesgames.com website review

Visit site (opens in a new tab)Reviewed 2 November 202638 issues · 60 checks

This review found 38 issues worth fixing on 7piratesgames.com, 16 of them high impact, across 60 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
17.5 s2.4 sMay 16Oct 316.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.9 s
Jun 20, 20264.1 s
Jun 27, 20264.3 s
Jul 4, 20265.6 s
Jul 11, 20264.8 s
Jul 18, 20265.6 s
Jul 25, 20266.3 s
Aug 1, 20267.0 s
Aug 8, 20268.5 s
Aug 15, 20269.6 s
Aug 22, 20268.3 s
Aug 29, 20267.0 s
Sep 5, 20267.4 s
Sep 12, 20269.7 s
Sep 19, 20269.1 s
Sep 26, 202610.5 s
Oct 3, 202612.3 s
Oct 17, 202615.8 s
Oct 24, 202612.2 s
Oct 31, 20266.6 s
Real-visitor tap response (INP)75th percentile, phones
206 ms127 msMay 16Oct 31180 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026154 ms
May 23, 2026136 ms
May 30, 2026145 ms
Jun 6, 2026145 ms
Jun 13, 2026197 ms
Jun 20, 2026161 ms
Jun 27, 2026147 ms
Jul 4, 2026143 ms
Jul 11, 2026143 ms
Jul 18, 2026142 ms
Jul 25, 2026149 ms
Aug 1, 2026159 ms
Aug 8, 2026158 ms
Aug 15, 2026175 ms
Aug 22, 2026181 ms
Aug 29, 2026179 ms
Sep 5, 2026195 ms
Sep 12, 2026162 ms
Sep 19, 2026167 ms
Sep 26, 2026164 ms
Oct 3, 2026167 ms
Oct 10, 2026172 ms
Oct 17, 2026157 ms
Oct 24, 2026162 ms
Oct 31, 2026180 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 7piratesgames.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix68
  • Use efficient cache lifetimes

    16.3 s · 9.4 MB

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

  • Improve image delivery

    15.8 s · 9.0 MB

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

  • Mobile performance score: 68

    68/100

    Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    550 ms

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

  • 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 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 50 KiB and 0 ms of main-thread time.

2 checks passed
  • Main-thread work: 0.2 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

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

  • Real-user LCP: 6.6 s

    6.6 s

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

  • Largest Contentful Paint: 19.1 s

    19.1 s

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

  • Time to Interactive: 19.1 s

    19.1 s

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

  • Speed Index: 6.9 s

    6.9 s

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

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

    +88%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 958 ms

    958 ms

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

  • 12 images without width and height

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

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

    +18%

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

5 checks passed
  • Real-user INP: 180 ms

    180 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 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).

  • 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 fix25
  • Page weight: 21.9 MB in 16 requests

    21.9 MB

    Your homepage downloads 21.9 MB in 16 requests on a phone: media 12.4 MB (1), images 9.4 MB (10) and fonts 48 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 8 images over 500 KB

    8 images weigh 9.3 MB together. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    4.5 MB

    9 images are downloaded at several times the size a phone draws them, for example first-BovfYtR7.png at 1,920 px wide, shown at 390 px. Resized copies would save about 4.5 MB.

  • 10 images in older formats

    10 images (9.4 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 6.2 g of CO₂ per visit

    6.20 g

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

2 to fix93
  • 4 text elements with low contrast

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

SEO

10 to fixGoogle 9143
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://7piratesgames.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at 7piratesgames.com/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

AI search readiness

1 to fix83
  • 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://7piratesgames.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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Best practices

2 to fixGoogle 10087
  • 3 small tap targets

    3 of 7 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.

Content and conversion

6 to fix25
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

  • 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 18 words

    The homepage has only about 18 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.

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

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.

  • 2 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on 7piratesgames.com, including 13 speed issues, 10 SEO issues and 6 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