Website review, no card needed

wrestlinginc.com logo

wrestlinginc.com website review

Visit site (opens in a new tab)Reviewed 11 October 202634 issues · 83 checks

This review found 34 issues worth fixing on wrestlinginc.com, 7 of them high impact, across 83 checks. The most urgent: 81 text elements with low contrast. 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
1.0 s916 msApr 18Oct 3981 ms
Show as table
DateReal-visitor load time (LCP)
Apr 18, 2026953 ms
Apr 25, 2026941 ms
May 2, 2026933 ms
May 9, 2026927 ms
May 16, 2026935 ms
May 23, 2026943 ms
May 30, 2026939 ms
Jun 6, 2026967 ms
Jun 13, 2026982 ms
Jun 20, 2026990 ms
Jun 27, 2026999 ms
Jul 4, 2026972 ms
Jul 11, 2026951 ms
Jul 18, 2026940 ms
Jul 25, 2026939 ms
Aug 1, 2026955 ms
Aug 8, 2026962 ms
Aug 15, 2026959 ms
Aug 22, 2026961 ms
Aug 29, 2026956 ms
Sep 5, 2026966 ms
Sep 12, 2026982 ms
Sep 19, 2026989 ms
Sep 26, 2026996 ms
Oct 3, 2026981 ms
Real-visitor tap response (INP)75th percentile, phones
127 ms110 msApr 18Oct 3125 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026120 ms
Apr 25, 2026115 ms
May 2, 2026113 ms
May 9, 2026112 ms
May 16, 2026112 ms
May 23, 2026114 ms
May 30, 2026114 ms
Jun 6, 2026118 ms
Jun 13, 2026121 ms
Jun 20, 2026123 ms
Jun 27, 2026123 ms
Jul 4, 2026121 ms
Jul 11, 2026118 ms
Jul 18, 2026116 ms
Jul 25, 2026115 ms
Aug 1, 2026117 ms
Aug 8, 2026117 ms
Aug 15, 2026117 ms
Aug 22, 2026117 ms
Aug 29, 2026116 ms
Sep 5, 2026119 ms
Sep 12, 2026121 ms
Sep 19, 2026122 ms
Sep 26, 2026124 ms
Oct 3, 2026125 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 wrestlinginc.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix86
  • Mobile performance score: 86

    86/100

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

  • Use efficient cache lifetimes

    300 ms · 572 KiB

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

  • Improve image delivery

    450 ms · 407 KiB

    15 images could be 407 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused JavaScript

    150 ms · 607 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (adthrive.com, Google Tag Manager and Google CDN and others), adding 1.1 MB and 434 ms of main-thread time.

  • adthrive.com adds 154 ms

    154 ms

    adthrive.com costs a phone 154 ms of main-thread work and 518 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.

  • Google Tag Manager adds 143 ms

    143 ms

    Google Tag Manager costs a phone 143 ms of main-thread work and 310 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.

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    14 KiB

    About 14 KiB of CSS is downloaded but never applied on this page.

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

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 11.4 s

    11.4 s

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

  • Largest Contentful Paint: 3.9 s

    3.9 s

    Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “[Left] Leon Slater confronts Nic Nemeth and [Right] Xia Bro…”.

  • Speed Index: 3.6 s

    3.6 s

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

  • Tap response (INP) held steady for real visitors

    +6%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.8 s

    0.8 s

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

  • Real-user INP: 94 ms

    94 ms

    Real visitors wait 94 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.

  • Real-user FCP: 0.7 s

    0.7 s

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

  • Real-user TTFB: 336 ms

    336 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 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: 57 ms

    57 ms

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

Images and page weight

3 to fix68
  • Page weight: 2.0 MB in 95 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 95 requests on a phone: scripts 1.1 MB (16), images 782 KiB (32) and fonts 71 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    51 KiB

    3 images are downloaded at several times the size a phone draws them, for example intro-1791685853.webp at 780 px wide, shown at 163 px. Resized copies would save about 51 KiB.

  • 12 images below the first screen load straight away

    12 images further down the page (331 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.57 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 7993
  • 81 text elements with low contrast

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

  • 30 tap targets too small

    30 tap targets are too small or too close together to hit reliably with a finger.

  • 2 links without text

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is long (76 characters)

    Your title is 76 characters, so Google will cut it off around 60: “Wrestling Inc. | Pro Wrestling News, WWE & AEW Results, Superstar Interviews”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “TNA Bound For Glory 2026 Results W/ Live Updates”). One clear main headline is easier for people and search engines.

  • 30 links with vague text

    30 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 166 internal links, 29 external

    The homepage links to 166 pages on wrestlinginc.com and 29 external pages.

6 checks passed
  • Meta description: 110 characters

    Your meta description is 110 characters: “The latest WWE, AEW, NJPW real-time results, news, exclusive interviews, live coverage, and more - since 1997.”.

  • Canonical URL set

    The canonical URL is https://www.wrestlinginc.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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.wrestlinginc.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.wrestlinginc.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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Other pages

4 to fix74
  • 1 page without a title

    https://www.wrestlinginc.com/feed has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://www.wrestlinginc.com/feed has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.wrestlinginc.com/about, https://www.wrestlinginc.com/policies, https://www.wrestlinginc.com/ai-policy and https://www.wrestlinginc.com/sitemap use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.wrestlinginc.com/feed has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.wrestlinginc.com/sitemap 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 39 found) and read each the way a search engine does.

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

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

Best practices

3 to fixGoogle 7385
  • 34 small tap targets

    34 of 85 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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.

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

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

  • 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 648 words of copy

    The homepage carries about 648 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Comscore, 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.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies, 2 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.

  • 41 other companies contacted

    Loading the homepage contacts 41 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 wrestlinginc.com, 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
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 34 issues on wrestlinginc.com, including 10 speed issues, 3 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