Website review, no card needed
partizan.rs website review
Visit site (opens in a new tab)Reviewed 22 October 202626 issues · 72 checks
This review found 26 issues worth fixing on partizan.rs, 5 of them high impact, across 72 checks. The most urgent: fails Core Web Vitals for real visitors. 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
87BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.8 s |
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 180 ms |
| May 9, 2026 | 178 ms |
| May 16, 2026 | 191 ms |
| May 23, 2026 | 187 ms |
| May 30, 2026 | 221 ms |
| Jun 6, 2026 | 209 ms |
| Jun 13, 2026 | 192 ms |
| Jun 20, 2026 | 192 ms |
| Jun 27, 2026 | 184 ms |
| Jul 4, 2026 | 180 ms |
| Jul 11, 2026 | 163 ms |
| Jul 18, 2026 | 149 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 143 ms |
| Aug 8, 2026 | 144 ms |
| Aug 15, 2026 | 151 ms |
| Aug 22, 2026 | 151 ms |
| Aug 29, 2026 | 148 ms |
| Sep 5, 2026 | 152 ms |
| Sep 12, 2026 | 146 ms |
| Sep 19, 2026 | 150 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 151 ms |
| Oct 17, 2026 | 145 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
Mobile performance score: 80
80/100Your mobile performance score is 80 (desktop: 96). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
250 ms · 323 KiB26 files are served with short cache lifetimes, so returning visitors download them again (323 KiB).
Render-blocking requests
500 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Improve image delivery
376 KiB4 images could be 376 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
Reduce unused JavaScript
150 ms · 57 KiBAbout 57 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 108 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (YouTube and JSDelivr CDN), adding 292 KiB and 0 ms of main-thread time.
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.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 537 ms of it running JavaScript. That is comfortably low.
Server response: 116 ms
116 msYour server sent the HTML in 116 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.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “FK Partizan uz inicijativu „Pink October“”.
Largest content (LCP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
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.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Time to Interactive: 4.5 s
4.5 sThe page becomes fully interactive after 4.5 s. Good is under 3.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 155 ms
155 msReal visitors wait 155 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 180 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 52 ms
52 msScripts block the page for only 52 ms while loading. Good is under 200 ms.
Images and page weight
An image on the first screen is lazy-loaded
50976-1791379652.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 0.5 g of CO₂ per visit
0.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.49 g of CO₂e: 58.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.7 MB in 83 requests
1.7 MBYour homepage downloads 1.7 MB in 83 requests on a phone: images 898 KiB (27), other files 363 KiB (13) and scripts 195 KiB (23). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
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.
2 checks passed
Every image has alt text
All 43 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
32 internal links, 16 external
The homepage links to 32 pages on partizan.rs and 16 external pages.
8 checks passed
Meta description: 110 characters
Your meta description is 110 characters: “Zvanična stranica FK Partizan. Pratite najnovije vesti, rezultate utakmica, roster igrača i sve o našem klubu.”.
One H1 headline
Your main headline reads: “FK Partizan - Zvanična stranica”.
Title: 31 characters
Your title is a healthy 31 characters: “FK Partizan - Zvanična stranica”.
Canonical URL set
The canonical URL is https://partizan.rs/.
Structured data in place
Structured data found: SportsOrganization.
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://partizan.rs/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://partizan.rs/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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (468 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://partizan.rs/vesti/5525 and https://partizan.rs/vesti/5525/fk-partizan-uz-inicijativu-pink-october all use the title “FK Partizan uz inicijativu „Pink October“ - FK Partizan”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://partizan.rs/vesti/5525 and https://partizan.rs/vesti/5525/fk-partizan-uz-inicijativu-pink-october use the same meta description. A description written for each page earns more clicks.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://partizan.rs/vesti/5525, whose canonical is https://partizan.rs/vesti/5525/fk-partizan-uz-inicijativu-pink-october. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://partizan.rs/utakmice/236, https://partizan.rs/utakmice/235 and https://partizan.rs/utakmice/234 have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://partizan.rs/klub 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 20 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
34 of 37 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.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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.
About 624 words of copy
The homepage carries about 624 words of visible text.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 partizan.rs, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- Framework
- Nuxt
Company
- Founded
- 1945
- Headquarters
- Belgrade
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on partizan.rs, including 14 speed issues and 5 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.