Website review, no card needed
athletic.bg website review
Visit site (opens in a new tab)Reviewed 24 October 202633 issues · 79 checks
This review found 33 issues worth fixing on athletic.bg, 12 of them high impact, across 79 checks. The most urgent: render-blocking requests. 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.7 s |
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 942 ms |
| Sep 26, 2026 | 841 ms |
| Oct 3, 2026 | 836 ms |
| Oct 10, 2026 | 836 ms |
| Oct 17, 2026 | 836 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 118 ms |
| May 9, 2026 | 117 ms |
| May 16, 2026 | 116 ms |
| May 23, 2026 | 118 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 127 ms |
| Jun 13, 2026 | 128 ms |
| Jun 20, 2026 | 130 ms |
| Jun 27, 2026 | 132 ms |
| Jul 4, 2026 | 132 ms |
| Jul 11, 2026 | 135 ms |
| Jul 18, 2026 | 136 ms |
| Jul 25, 2026 | 134 ms |
| Aug 1, 2026 | 130 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 127 ms |
| Sep 12, 2026 | 120 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 119 ms |
| Oct 3, 2026 | 118 ms |
| Oct 10, 2026 | 120 ms |
| Oct 17, 2026 | 119 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
Speed
Render-blocking requests
3.4 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.
Improve image delivery
1.6 s · 258 KiB1 image could be 258 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Mobile performance score: 45
45/100Your mobile performance score is 45 (desktop: 93). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
1 third-party service on the page
1 third-party service load with your homepage (Google Tag Manager), adding 713 KiB and 914 ms of main-thread time.
Google Tag Manager adds 914 ms
914 msGoogle Tag Manager costs a phone 914 ms of main-thread work and 713 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.
Use efficient cache lifetimes
800 ms · 158 KiB7 files are served with short cache lifetimes, so returning visitors download them again (158 KiB).
Reduce unused JavaScript
361 KiBAbout 361 KiB of JavaScript is downloaded but never used on this page.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 354 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 15 KiBAbout 15 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.
Minify CSS
150 ms · 3 KiB3 KiB could be saved by minifying CSS.
Phones get a much slower page than desktops
Desktop scores 93 but mobile only 45. 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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 821 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.3 s
8.3 sYour largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ТРЕНИРАЙ ОТ 24.99€ НА МЕСЕЦ”.
Time to Interactive: 9.1 s
9.1 sThe page becomes fully interactive after 9.1 s. Good is under 3.8 s.
Total Blocking Time: 738 ms
738 msScripts block taps and scrolling for 738 ms in total while the page loads. Good is under 200 ms.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.107
0.107The layout shifts by 0.107 while loading, so content jumps under the reader's thumb. Good is under 0.1.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 118 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 107 ms
107 msReal visitors wait 107 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.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 528 ms
528 msReal visitors wait 528 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 52% faster for real visitors
-52%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.7 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 2.8 MB in 28 requests
2.8 MBYour homepage downloads 2.8 MB in 28 requests on a phone: images 1.7 MB (8), scripts 755 KiB (9) and fonts 395 KiB (7). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (1.6 MB) 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.
4 images below the first screen load straight away
4 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
258 KiB2 images are downloaded at several times the size a phone draws them, for example 12-athletic-botev-plovdiv-silovi-uredi-oranjevi-koloni-scale at 1,920 px wide, shown at 350 px. Resized copies would save about 258 KiB.
About 0.8 g of CO₂ per visit
0.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 96.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
35 text elements with low contrast
35 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Elements must only use permitted ARIA attributes (3 elements)
Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 9 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (23 characters)
Your title is only 23 characters: “Начало | Атлетик Фитнес”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (HowTo, ItemList, Organization and Service) but with 1 problem, for example “Service: no offers (price) block”.
87 internal links, 8 external
The homepage links to 87 pages on athletic.bg and 8 external pages.
6 checks passed
Meta description: 100 characters
Your meta description is 100 characters: “Тренирай в модерни Атлетик клубове из България — с професионални треньори и разнообразни тренировки.”.
One H1 headline
Your main headline reads: “Тренирайот 24.99€ на месец”.
Canonical URL set
The canonical URL is https://athletic.bg/bg/.
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://athletic.bg/sitemap.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://athletic.bg/llms.txt (5 KiB, 37 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://athletic.bg/grad/plovdiv is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://athletic.bg/grad/plovdiv has no meta description, so Google writes the search snippet from whatever text it finds.
14 pages with very little text
https://athletic.bg/klubove, https://athletic.bg/grad/sofia, https://athletic.bg/klubove/dianabad, https://athletic.bg/klubove/cherni-vrah, https://athletic.bg/klubove/studentski-grad and https://athletic.bg/klubove/kopernik and 8 others 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 46 found) and read each the way a search engine does.
5 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
16 of 19 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.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 83 words
The homepage has only about 83 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
2 checks passed
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
6 other companies contacted
Loading the homepage contacts 6 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 athletic.bg, 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 33 issues on athletic.bg, including 16 speed issues, 2 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.