Website review, no card needed

jdsports.com.ph logo

jdsports.com.ph website review

Visit site (opens in a new tab)Reviewed 20 November 202639 issues · 90 checks

This review found 39 issues worth fixing on jdsports.com.ph, 11 of them high impact, across 90 checks. The most urgent: mobile performance score: 41. 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
2.6 s1.8 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.4 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.3 s
Sep 19, 20262.1 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Nov 7, 20261.9 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
207 ms149 msMay 30Nov 14189 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026156 ms
Jun 6, 2026162 ms
Jun 13, 2026164 ms
Jun 20, 2026164 ms
Jun 27, 2026166 ms
Jul 4, 2026168 ms
Jul 11, 2026167 ms
Jul 18, 2026169 ms
Jul 25, 2026171 ms
Aug 1, 2026171 ms
Aug 8, 2026173 ms
Aug 15, 2026178 ms
Aug 22, 2026186 ms
Aug 29, 2026193 ms
Sep 5, 2026198 ms
Sep 12, 2026198 ms
Sep 19, 2026192 ms
Sep 26, 2026193 ms
Oct 3, 2026197 ms
Oct 10, 2026200 ms
Oct 17, 2026200 ms
Oct 24, 2026200 ms
Oct 31, 2026195 ms
Nov 7, 2026188 ms
Nov 14, 2026189 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 jdsports.com.ph (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. jdsports.com.ph at 4.0 s4.0 s
  2. jdsports.com.ph at 7.9 s7.9 s
  3. jdsports.com.ph at 11.9 s11.9 s
  4. jdsports.com.ph at 15.9 s15.9 s
  5. jdsports.com.ph at 19.9 s19.9 s
  6. jdsports.com.ph at 23.8 s23.8 s
  7. jdsports.com.ph at 27.8 s27.8 s
  8. jdsports.com.ph at 31.8 s31.8 s

Speed

14 to fix41
  • Mobile performance score: 41

    41/100

    Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.3 s

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

  • 4,150 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Clarity and others), adding 1.6 MB and 1.6 s of main-thread time.

  • Reduce unused JavaScript

    1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page.

  • Render-blocking requests

    750 ms

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

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    450 ms · 168 KiB

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

  • Improve image delivery

    300 ms · 168 KiB

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

  • Use efficient cache lifetimes

    407 KiB

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

  • Shopify adds 293 ms

    293 ms

    Shopify costs a phone 293 ms of main-thread work and 605 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 290 ms

    290 ms

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

  • customerfields.com adds 260 ms

    260 ms

    customerfields.com costs a phone 260 ms of main-thread work and 209 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.

  • Clarity adds 273 ms

    273 ms

    Clarity costs a phone 273 ms of main-thread work and 29 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

    124 KiB

    124 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    28 KiB

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

  • Minify CSS

    16 KiB

    16 KiB could be saved by minifying CSS.

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

    21 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 20.8 s

    20.8 s

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

  • Speed Index: 10.5 s

    10.5 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • Largest Contentful Paint: 5.8 s

    5.8 s

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

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

    +19%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 156 ms to 189 ms 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: 1.8 s

    1.8 s

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

  • Real-user INP: 173 ms

    173 ms

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 681 ms

    681 ms

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

  • Largest content (LCP) got 22% faster for real visitors

    -22%

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.022

    0.022

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

Images and page weight

1 to fix70
  • Page weight: 4.7 MB in 311 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 311 requests on a phone: scripts 2.1 MB (93), other files 1.2 MB (157) and images 917 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (232 KiB) 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 1.3 g of CO₂ per visit

    1.34 g

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

10 to fixGoogle 8889
  • 5 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (9 elements)

    All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 12 links without text

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

  • 7 form fields without a label

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

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • Title is short (21 characters)

    Your title is only 21 characters: “JD Sports Philippines”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (175 characters)

    Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.

  • One H1 headline

    Your <h1> is empty.

  • 472 internal links, 67 external

    The homepage links to 472 pages on jdsports.com.ph and 67 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.jdsports.com.ph/.

  • Structured data in place

    Structured data found: Organization and 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.jdsports.com.ph/sitemap.xml.

AI search readiness

100
4 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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.jdsports.com.ph/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 2 pages share a meta description

    https://www.jdsports.com.ph/blogs/jd-blog and https://www.jdsports.com.ph/collections/sale use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.jdsports.com.ph/blogs/jd-blog, https://www.jdsports.com.ph/pages/store-locator, https://www.jdsports.com.ph/collections/men, https://www.jdsports.com.ph/collections/women, https://www.jdsports.com.ph/collections/kids and https://www.jdsports.com.ph/pages/brands and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.jdsports.com.ph/blogs/jd-blog, https://www.jdsports.com.ph/pages/store-locator and https://www.jdsports.com.ph/pages/brands have 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 196 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.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

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

  • 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

2 to fixGoogle 7791
  • Deprecated browser APIs

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    42 of 45 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 447 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: “Shop Now” and “Shop PUMA”.

  • 24 calls to action

    The homepage has 24 calls to action, for example “Shop Now”, “Shop PUMA” and “Shop now”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Microsoft Clarity (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.

  • 8 cookies set on arrival

    8

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

  • 22 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Live Search by Okas Concepts;Shopify;Shopify Plus
Hosting
Shopify

Hiring

Hiring
228 open roles
Teams
Retail Sales Assistants & Supervisors (99), Retail Sales Advisor (70), Retail Store Management (15), Retail (10)
Job board
greenhouse

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on jdsports.com.ph, including 18 speed issues, 3 SEO issues and 2 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