Website review, no card needed
oneesports.gg website review
Visit site (opens in a new tab)Reviewed 3 November 202645 issues · 88 checks
This review found 45 issues worth fixing on oneesports.gg, 15 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 215 ms |
| May 23, 2026 | 215 ms |
| May 30, 2026 | 217 ms |
| Jun 6, 2026 | 220 ms |
| Jun 13, 2026 | 220 ms |
| Jun 20, 2026 | 221 ms |
| Jun 27, 2026 | 216 ms |
| Jul 4, 2026 | 211 ms |
| Jul 11, 2026 | 205 ms |
| Jul 18, 2026 | 203 ms |
| Jul 25, 2026 | 202 ms |
| Aug 1, 2026 | 201 ms |
| Aug 8, 2026 | 206 ms |
| Aug 15, 2026 | 205 ms |
| Aug 22, 2026 | 204 ms |
| Aug 29, 2026 | 203 ms |
| Sep 5, 2026 | 204 ms |
| Sep 12, 2026 | 211 ms |
| Sep 19, 2026 | 216 ms |
| Sep 26, 2026 | 220 ms |
| Oct 3, 2026 | 217 ms |
| Oct 10, 2026 | 213 ms |
| Oct 17, 2026 | 213 ms |
| Oct 24, 2026 | 212 ms |
| Oct 31, 2026 | 211 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
How it loaded on a phone
2.2 s
4.4 s
6.7 s
8.9 s
11.1 s
13.3 s
15.5 s
17.7 s
Speed
Reduce unused JavaScript
4.1 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.
Use efficient cache lifetimes
3.3 s · 1.7 MB130 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Render-blocking requests
1.8 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
primis.tech adds 1.4 s
1.4 sprimis.tech costs a phone 1.4 s of main-thread work and 1.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 15.2 s
A phone's processor spends 15.2 s on main-thread work while loading, 7.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (primis.tech, Rubicon Project and Google Tag Manager and others), adding 3.3 MB and 4.3 s of main-thread time.
Improve image delivery
350 ms · 440 KiB11 images could be 440 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Google Tag Manager adds 638 ms
638 msGoogle Tag Manager costs a phone 638 ms of main-thread work and 505 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.
Rubicon Project adds 682 ms
682 msRubicon Project costs a phone 682 ms of main-thread work and 75 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
500 ms · 46 KiBPolyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.
fuseplatform.net adds 451 ms
451 msfuseplatform.net costs a phone 451 ms of main-thread work and 293 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 468 ms. During a long task the page ignores taps.
Google/Doubleclick Ads adds 379 ms
379 msGoogle/Doubleclick Ads costs a phone 379 ms of main-thread work and 479 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.
Minify JavaScript
290 ms · 47 KiB47 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.
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: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
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.
Largest Contentful Paint: 17.0 s
17.0 sYour largest element takes 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Honkai Star Rail 3.4 KV featuring Phainon”.
Speed Index: 21.2 s
21.2 sVisually, the page fills in at 21.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 47.3 s
47.3 sThe page becomes fully interactive after 47.3 s. Good is under 3.8 s.
Total Blocking Time: 3.4 s
3.4 sScripts block taps and scrolling for 3.4 s in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 215 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 188 ms
188 msReal visitors wait 188 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.4 MB in 1,221 requests
5.4 MBYour homepage downloads 5.4 MB in 1,221 requests on a phone: scripts 3.3 MB (60), images 816 KiB (374) and other files 637 KiB (629). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (53 KiB) is 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 1.5 g of CO₂ per visit
1.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.52 g of CO₂e: 182.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
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.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 16 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 3 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 (11 characters)
Your title is only 11 characters: “ONE Esports”. 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.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
113 internal links, 16 external
The homepage links to 113 pages on oneesports.gg and 16 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.oneesports.gg/.
Structured data in place
Structured data found: 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://www.oneesports.gg/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, 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://www.oneesports.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 (512 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
https://www.oneesports.gg/press, https://www.oneesports.gg/partner-with-us and https://www.oneesports.gg/tag/esports have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.oneesports.gg/press, whose canonical is https://www.oneesports.gg/category/press. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
9 pages without an H1
https://www.oneesports.gg/press, https://www.oneesports.gg/partner-with-us, https://www.oneesports.gg/category/call-of-duty, https://www.oneesports.gg/category/league-of-legends, https://www.oneesports.gg/category/valorant and https://www.oneesports.gg/category/anime and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.oneesports.gg/partner-with-us has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.
4 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
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 13 pages that loaded have a <title>.
Best practices
20 small tap targets
20 of 85 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
18 third-party cookies
18 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 254 words of copy
The homepage carries about 254 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CALL OF DUTY” and “CONTACT US”.
8 calls to action
The homepage has 8 calls to action, for example “Contact Us”, “Call of Duty” and “Login/Signup”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 4 mores (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 1 of them by other companies (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.
59 other companies contacted
Loading the homepage contacts 59 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 oneesports.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
- Bootstrap
- Analytics
- Google Tag Manager
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 oneesports.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.