Website review, no card needed

givemesport.com logo

givemesport.com website review

Visit site (opens in a new tab)Reviewed 20 October 202648 issues · 96 checks

This review found 48 issues worth fixing on givemesport.com, 21 of them high impact, across 96 checks. The most urgent: reduce unused JavaScript. 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
3.5 s2.7 sMay 2Oct 173.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.8 s
May 9, 20262.8 s
May 16, 20262.8 s
May 23, 20263.0 s
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20262.9 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20263.0 s
Sep 12, 20263.1 s
Sep 19, 20263.2 s
Sep 26, 20263.3 s
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
238 ms132 msMay 2Oct 17226 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026148 ms
May 9, 2026146 ms
May 16, 2026144 ms
May 23, 2026147 ms
May 30, 2026154 ms
Jun 6, 2026156 ms
Jun 13, 2026155 ms
Jun 20, 2026155 ms
Jun 27, 2026155 ms
Jul 4, 2026155 ms
Jul 11, 2026158 ms
Jul 18, 2026161 ms
Jul 25, 2026165 ms
Aug 1, 2026170 ms
Aug 8, 2026173 ms
Aug 15, 2026176 ms
Aug 22, 2026175 ms
Aug 29, 2026173 ms
Sep 5, 2026179 ms
Sep 12, 2026191 ms
Sep 19, 2026203 ms
Sep 26, 2026213 ms
Oct 3, 2026221 ms
Oct 10, 2026222 ms
Oct 17, 2026226 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 givemesport.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. givemesport.com at 1.8 s1.8 s
  2. givemesport.com at 3.6 s3.6 s
  3. givemesport.com at 5.4 s5.4 s
  4. givemesport.com at 7.2 s7.2 s
  5. givemesport.com at 9.0 s9.0 s
  6. givemesport.com at 10.9 s10.9 s
  7. givemesport.com at 12.7 s12.7 s
  8. givemesport.com at 14.5 s14.5 s

Speed

13 to fix35
  • Reduce unused JavaScript

    5.3 s · 1,017 KiB

    About 1,017 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.

  • Use efficient cache lifetimes

    3.9 s · 1.1 MB

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

  • Main-thread work: 11.0 s

    A phone's processor spends 11.0 s on main-thread work while loading, 4.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 35

    35/100

    Your mobile performance score is 35 (desktop: 66). 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 (adsninja.ca, Pubmatic and givemesportimages.com and others), adding 2.6 MB and 2.2 s of main-thread time.

  • adsninja.ca adds 569 ms

    569 ms

    adsninja.ca costs a phone 569 ms of main-thread work and 514 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.

  • Improve image delivery

    150 ms · 296 KiB

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

  • givemesportimages.com adds 290 ms

    290 ms

    givemesportimages.com costs a phone 290 ms of main-thread work and 903 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.

  • Pubmatic adds 297 ms

    297 ms

    Pubmatic costs a phone 297 ms of main-thread work and 93 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.

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • Other Google APIs/SDKs adds 245 ms

    245 ms

    Other Google APIs/SDKs costs a phone 245 ms of main-thread work and 481 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 267 ms

    267 ms

    Rubicon Project costs a phone 267 ms of main-thread work and 158 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,251 HTML elements

    The page has 2,251 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 67 KiB

    About 67 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    94 KiB

    Polyfills for old browsers add 94 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    14 KiB

    14 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 66 but mobile only 35. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 68 ms

    68 ms

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

Core Web Vitals

11 to fix100
  • 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.

  • First Contentful Paint: 8.2 s

    8.2 s

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

  • Largest Contentful Paint: 23.6 s

    23.6 s

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

  • Time to Interactive: 41.4 s

    41.4 s

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

  • Speed Index: 15.2 s

    15.2 s

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

  • Total Blocking Time: 844 ms

    844 ms

    Scripts block taps and scrolling for 844 ms in total while the page loads. Good is under 200 ms.

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

    +52%

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

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

    +21%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 892 ms

    892 ms

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

  • 5 images without width and height

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

4 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 152 ms

    152 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.3 MB in 1,297 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 1,297 requests on a phone: scripts 2.3 MB (101), images 791 KiB (418) and HTML 652 KiB (233). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.21 g

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

10 to fixGoogle 7686
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 31 text elements with low contrast

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

  • 10 tap targets too small

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

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • 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 (5 elements)

    All page content should be contained by landmarks: 5 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.

  • 5 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 142 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 8581
  • No H1 headline

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

  • Title is long (115 characters)

    Your title is 115 characters, so Google will cut it off around 60: “GiveMeSport – Sports news including results, video and analysis on Football, MMA, Boxing,…”.

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

  • 279 internal links, 30 external

    The homepage links to 279 pages on givemesport.com and 30 external pages.

6 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “GiveMeSport (GMS) is a sport media outlet providing exclusive player, coach and manager interviews, and providing fans …”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: WebSite.

  • 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.givemesport.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://www.givemesport.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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 (1,580 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.givemesport.com/db/premier-league/schedule, whose canonical is https://www.givemesport.com/db/premier-league/schedule?date=20261019. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 127 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5474
  • 6 broken images

    6 images failed to load on a phone, for example https://www.givemesport.com/?q=50&fit=crop&w=32&h=&dpr=2.

  • 34 third-party cookies

    34 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) Error: Unable to find element with ID: comments-feed-list.”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    56 of 69 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • 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.

  • About 999 words of copy

    The homepage carries about 999 words of visible text.

4 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “MLS Schedule”, “Subscribe” and “Join Our Team”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • 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

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics 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.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 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.

  • 82 other companies contacted

    Loading the homepage contacts 82 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 givemesport.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 Analytics

Company

Founded
2011
Headquarters
Montreal

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on givemesport.com, including 24 speed issues, 3 SEO issues and 3 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