Website review, no card needed
teampwr.gg website review
Visit site (opens in a new tab)Reviewed 3 November 202645 issues · 83 checks
This review found 45 issues worth fixing on teampwr.gg, 21 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 7.3 s |
| May 23, 2026 | 7.5 s |
| May 30, 2026 | 7.8 s |
| Jun 6, 2026 | 8.0 s |
| Jun 13, 2026 | 8.1 s |
| Jun 20, 2026 | 8.3 s |
| Jun 27, 2026 | 8.5 s |
| Jul 4, 2026 | 8.7 s |
| Jul 11, 2026 | 8.7 s |
| Jul 18, 2026 | 8.8 s |
| Jul 25, 2026 | 8.7 s |
| Aug 1, 2026 | 8.8 s |
| Aug 8, 2026 | 9.2 s |
| Aug 15, 2026 | 9.3 s |
| Aug 22, 2026 | 9.6 s |
| Aug 29, 2026 | 9.7 s |
| Sep 5, 2026 | 9.8 s |
| Sep 12, 2026 | 9.7 s |
| Sep 19, 2026 | 9.2 s |
| Sep 26, 2026 | 9.0 s |
| Oct 3, 2026 | 8.7 s |
| Oct 10, 2026 | 8.7 s |
| Oct 17, 2026 | 8.9 s |
| Oct 24, 2026 | 9.1 s |
| Oct 31, 2026 | 9.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 95 ms |
| May 23, 2026 | 96 ms |
| May 30, 2026 | 97 ms |
| Jun 6, 2026 | 98 ms |
| Jun 13, 2026 | 102 ms |
| Jun 20, 2026 | 101 ms |
| Jun 27, 2026 | 102 ms |
| Jul 4, 2026 | 106 ms |
| Jul 11, 2026 | 106 ms |
| Jul 18, 2026 | 106 ms |
| Jul 25, 2026 | 107 ms |
| Aug 1, 2026 | 107 ms |
| Aug 8, 2026 | 107 ms |
| Aug 15, 2026 | 108 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 103 ms |
| Sep 12, 2026 | 102 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 100 ms |
| Oct 3, 2026 | 105 ms |
| Oct 10, 2026 | 106 ms |
| Oct 17, 2026 | 107 ms |
| Oct 24, 2026 | 112 ms |
| Oct 31, 2026 | 104 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
Speed
Use efficient cache lifetimes
18.8 s · 20.1 MB142 files are served with short cache lifetimes, so returning visitors download them again (20.1 MB).
Improve image delivery
6.2 s · 4.4 MB42 images could be 4.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.2 s faster on a phone.
Render-blocking requests
6.2 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.2 s.
Reduce unused JavaScript
2.6 s · 507 KiBAbout 507 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.
Reduce unused CSS
2.5 s · 416 KiBAbout 416 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Font display
1.5 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.5 s).
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Document request latency
650 ms · 141 KiBThe HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
655 msReduce initial server response time. Google estimates savings of 655 ms on a phone.
Minify JavaScript
380 ms · 87 KiB87 KiB could be saved by minifying JavaScript.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 555 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,025 HTML elements
The page has 2,025 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 755 ms
755 msYour server takes 755 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Cloudflare CDN and others), adding 363 KiB and 169 ms of main-thread time.
Minify CSS
150 ms · 14 KiB14 KiB could be saved by minifying CSS.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 132 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Core Web Vitals
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: 11.9 s
11.9 sReal visitors wait 11.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 8.9 s
8.9 sReal visitors see the first content after 8.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.7 s
3.7 sReal visitors wait 3.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 51.1 s
51.1 sYour largest element takes 51.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PWR TAKES GAMING, CONTENT AND CREATIVE TO A NEW LEVEL A lea…”.
Speed Index: 23.0 s
23.0 sVisually, the page fills in at 23.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 55.4 s
55.4 sThe page becomes fully interactive after 55.4 s. Good is under 3.8 s.
First Contentful Paint: 7.4 s
7.4 sThe first text or image appears after 7.4 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 7.3 s to 9.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
63 images without width and height
63 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 95 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 110 ms
110 msReal visitors wait 110 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Total Blocking Time: 147 ms
147 msScripts block the page for only 147 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.014
0.014The layout barely moves while loading (CLS 0.014, good is under 0.1).
Images and page weight
Page weight: 26.6 MB in 160 requests
26.6 MBYour homepage downloads 26.6 MB in 160 requests on a phone: media 13.9 MB (2), images 10.1 MB (97) and scripts 1.2 MB (32). Under 2 MB keeps phones on slow connections fast.
About 7.5 g of CO₂ per visit
7.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.54 g of CO₂e: 904.7 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
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
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.
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
1 checks passed
24 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 26 WCAG 2.2 A/AA and best-practice rules on the phone render: 24 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
Title is short (10 characters)
Your title is only 10 characters: “Home - PWR”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
85 internal links, 16 external
The homepage links to 85 pages on teampwr.gg and 16 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://teampwr.gg/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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://teampwr.gg/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://teampwr.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.
1 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.
Other pages
3 linked pages are broken
Your homepage links to https://teampwr.gg/pwrcreate/brainrot-card-tycoon, https://teampwr.gg/pwrcreate/duo-endless-zone-wars-ranked and https://teampwr.gg/pwrcreate/og-endless-zone-wars, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages without a meta description
https://teampwr.gg/pwr and https://teampwr.gg/pwr/creators have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://teampwr.gg/pwr and https://teampwr.gg/pwr/creators have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://teampwr.gg/pwr and https://teampwr.gg/pwr/creators took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 52 found) and read each the way a search engine does.
4 checks passed
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 2 pages that loaded have a <title>.
Best practices
13 small tap targets
13 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 26 words
The homepage has only about 26 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
12 calls to action
The homepage has 12 calls to action, for example “Contact”, “Shop Now” and “Apply Now”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
6 other companies contacted
Loading the homepage contacts 6 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 teampwr.gg, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on teampwr.gg, including 23 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.