Website review, no card needed
gsstore.org website review
Visit site (opens in a new tab)Reviewed 23 October 202656 issues · 98 checks
This review found 56 issues worth fixing on gsstore.org, 20 of them high impact, across 98 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
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.5 s |
| May 9, 2026 | 1.5 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 124 ms |
| May 9, 2026 | 122 ms |
| May 16, 2026 | 120 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 122 ms |
| Jun 20, 2026 | 123 ms |
| Jun 27, 2026 | 125 ms |
| Jul 4, 2026 | 128 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 148 ms |
| Jul 25, 2026 | 158 ms |
| Aug 1, 2026 | 174 ms |
| Aug 8, 2026 | 180 ms |
| Aug 15, 2026 | 186 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 201 ms |
| Sep 5, 2026 | 207 ms |
| Sep 12, 2026 | 205 ms |
| Sep 19, 2026 | 203 ms |
| Sep 26, 2026 | 201 ms |
| Oct 3, 2026 | 199 ms |
| Oct 10, 2026 | 197 ms |
| Oct 17, 2026 | 196 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
1.1 s
2.1 s
3.2 s
4.2 s
5.3 s
6.3 s
7.4 s
8.4 s
Speed
Reduce unused JavaScript
1.2 s · 529 KiBAbout 529 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.1 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7,376 HTML elements
The page has 7,376 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 6.2 s
A phone's processor spends 6.2 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (akinoncloudcdn.com, efilli.com and Google Tag Manager and others), adding 7.3 MB and 1.6 s of main-thread time.
Improve image delivery
2.1 MB72 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
akinoncloudcdn.com adds 690 ms
690 msakinoncloudcdn.com costs a phone 690 ms of main-thread work and 6.6 MB 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.
Use efficient cache lifetimes
300 ms · 250 KiB8 files are served with short cache lifetimes, so returning visitors download them again (250 KiB).
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 483 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 147 KiBAbout 147 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
efilli.com adds 437 ms
437 msefilli.com costs a phone 437 ms of main-thread work and 77 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 220 ms
220 msGoogle Tag Manager costs a phone 220 ms of main-thread work and 326 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.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Legacy JavaScript
150 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
13 KiB13 KiB could be saved by minifying JavaScript.
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: 120 ms
120 msYour server sent the HTML in 120 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.
Time to Interactive: 16.3 s
16.3 sThe page becomes fully interactive after 16.3 s. Good is under 3.8 s.
Largest Contentful Paint: 6.1 s
6.1 sYour largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 4.7 s
4.7 sThe first text or image appears after 4.7 s on a phone. Good is under 1.8 s.
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 909 ms
909 msScripts block taps and scrolling for 909 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 247 ms
247 msReal visitors wait 247 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 60% slower for real visitors
+60%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 124 ms to 196 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 7.5 MB in 360 requests
7.5 MBYour homepage downloads 7.5 MB in 360 requests on a phone: images 6.1 MB (315), scripts 1.0 MB (14) and stylesheets 165 KiB (5). Under 2 MB keeps phones on slow connections fast.
11 images below the first screen load straight away
11 images further down the page (456 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
10 KiB2 images are downloaded at several times the size a phone draws them, for example 78b70496-95a8-4ee0-a63a-44ff48fcd2d2.jpg at 960 px wide, shown at 310 px. Resized copies would save about 10 KiB.
About 2.1 g of CO₂ per visit
2.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.12 g of CO₂e: 254.0 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
7 buttons without a name
7 buttons have no accessible name, so screen readers announce just “button”.
23 tap targets too small
23 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.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (31 elements)
All page content should be contained by landmarks: 31 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (4 elements)
Banner landmark should not be contained in another landmark: 4 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.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
12 form fields without a label
12 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (12 elements)
ARIA role should be appropriate for the element: 12 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
44 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: 44 passed and 14 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (167 characters)
Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (WebSite) but with 2 problems, for example “WebSite: missing name”.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
681 internal links, 11 external
The homepage links to 681 pages on gsstore.org and 11 external pages.
4 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “Galatasaray Spor Kulübü Resmi Alışveriş Sitesi - GSStore”.
Canonical URL set
The canonical URL is https://www.gsstore.org/.
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.gsstore.org/sitemap.xml.
AI search readiness
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.gsstore.org/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 (2,010 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages share a meta description
https://www.gsstore.org/puma-forma, https://www.gsstore.org/puma-ic-saha, https://www.gsstore.org/puma-deplasman, https://www.gsstore.org/puma-alternatif, https://www.gsstore.org/puma-kaleci and https://www.gsstore.org/puma-diger-branslar and 8 others use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 187 found) and read each the way a search engine does.
7 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.
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
1 broken image
1 image failed to load on a phone, for example https://www.gsstore.org/.
Pasting is blocked
A form field blocks pasting, which frustrates password managers and people on phones.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
219 of 230 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 3 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 1,082 words of copy
The homepage carries about 1,082 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “SHOP BY PLAYER”.
1 short form
A short form (0 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
14 other companies contacted
Loading the homepage contacts 14 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 gsstore.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
Company
- Founded
- 2008
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 56 issues on gsstore.org, including 24 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.