Website review, no card needed
rtv.rs website review
Visit site (opens in a new tab)Reviewed 25 October 202646 issues · 84 checks
This review found 46 issues worth fixing on rtv.rs, 17 of them high impact, across 84 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.3 s |
| May 9, 2026 | 1.2 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 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.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 89 ms |
| May 9, 2026 | 90 ms |
| May 16, 2026 | 91 ms |
| May 23, 2026 | 91 ms |
| May 30, 2026 | 91 ms |
| Jun 6, 2026 | 93 ms |
| Jun 13, 2026 | 93 ms |
| Jun 20, 2026 | 93 ms |
| Jun 27, 2026 | 93 ms |
| Jul 4, 2026 | 93 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 95 ms |
| Aug 1, 2026 | 95 ms |
| Aug 8, 2026 | 94 ms |
| Aug 15, 2026 | 92 ms |
| Aug 22, 2026 | 93 ms |
| Aug 29, 2026 | 94 ms |
| Sep 5, 2026 | 94 ms |
| Sep 12, 2026 | 96 ms |
| Sep 19, 2026 | 95 ms |
| Sep 26, 2026 | 96 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 95 ms |
| Oct 17, 2026 | 95 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
2.1 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Improve image delivery
1.1 s · 824 KiB19 images could be 824 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Use efficient cache lifetimes
1,001 KiB35 files are served with short cache lifetimes, so returning visitors download them again (1,001 KiB).
Mobile performance score: 69
69/100Your mobile performance score is 69 (desktop: 81). Pages that score under 90 lose visitors before the first paint.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Facebook and Google Fonts and others), adding 2.0 MB and 398 ms of main-thread time.
Reduce unused JavaScript
414 KiBAbout 414 KiB of JavaScript is downloaded but never used on this page.
Font display
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
Google Tag Manager adds 243 ms
243 msGoogle Tag Manager costs a phone 243 ms of main-thread work and 613 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.
1,529 HTML elements
The page has 1,529 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Instagram adds 0 ms
0 msInstagram costs a phone 0 ms of main-thread work and 1.0 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 76 ms. During a long task the page ignores taps.
Reduce unused CSS
39 KiBAbout 39 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 409 ms of it running JavaScript. That is comfortably low.
Server response: 80 ms
80 msYour server sent the HTML in 80 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 11.3 s
11.3 sThe page becomes fully interactive after 11.3 s. Good is under 3.8 s.
Largest Contentful Paint: 5.0 s
5.0 sYour largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.101
0.101The layout shifts by 0.101 while loading, so content jumps under the reader's thumb. Good is under 0.1.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 89 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 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: 0.8 s
0.8 sReal visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 27 ms
27 msScripts block the page for only 27 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.9 MB in 93 requests
3.9 MBYour homepage downloads 3.9 MB in 93 requests on a phone: images 2.6 MB (51), scripts 974 KiB (23) and fonts 253 KiB (5). Under 2 MB keeps phones on slow connections fast.
16 images in older formats
16 images (1.5 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.
6 images below the first screen load straight away
6 images further down the page (534 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images far larger than shown
171 KiB4 images are downloaded at several times the size a phone draws them, for example izbori-glasanje-.jpg at 1,100 px wide, shown at 340 px. Resized copies would save about 171 KiB.
About 1.1 g of CO₂ per visit
1.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.10 g of CO₂e: 132.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
17 text elements with low contrast
17 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.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (32 elements)
All page content should be contained by landmarks: 32 elements on the page fail 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.
40 links without text
40 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
28 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 28 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
13 H1 headlines
There are 13 <h1> headlines (“Саичић: Студентска листа освојила 52,08 одсто гла…”, “Кос, Фон дер Лајен и Кошта честитали Студентској …” and “Вучић: Изгубили смо ове изборе, победила је студе…”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://rtv.rs/sitemap.xml, so Google discovers your pages only by following links.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
365 internal links, 91 external
The homepage links to 365 pages on rtv.rs and 91 external pages.
1 checks passed
Title: 38 characters
Your title is a healthy 38 characters: “НАСЛОВНА :: РАДИО-ТЕЛЕВИЗИЈА ВОЈВОДИНЕ”.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
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://rtv.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.
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.
Other pages
2 pages share a title
/ and https://rtv.rs/sr_ci all use the title “НАСЛОВНА :: РАДИО-ТЕЛЕВИЗИЈА ВОЈВОДИНЕ”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://rtv.rs/sr_ci/email-vesti, https://rtv.rs/sr_ci/program/prvi-program, https://rtv.rs/sr_ci/program/drugi-program, https://rtv.rs/sr_ci/program/program-na-srpskom-jeziku, https://rtv.rs/hu/program/magyar-nyelvu-adas and https://rtv.rs/sr_ci/program/program-na-jezicima-nacionalnih-zajednica and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://rtv.rs/sr_ci/email-vesti, https://rtv.rs/sr_ci/program/prvi-program, https://rtv.rs/sr_ci/program/drugi-program, https://rtv.rs/sr_ci/program/program-na-srpskom-jeziku, https://rtv.rs/hu/program/magyar-nyelvu-adas and https://rtv.rs/sr_ci/program/program-na-jezicima-nacionalnih-zajednica and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages with very little text
https://rtv.rs/sr_ci/email-vesti, https://rtv.rs/sr_ci/program/prvi-program, https://rtv.rs/sr_ci/program/program-na-srpskom-jeziku, https://rtv.rs/sr_ci/uzivo and https://rtv.rs/sr_ci 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.
1 page slow to respond
https://rtv.rs/sr_ci/uzivo took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 162 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
12 small tap targets
12 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 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.
Only about 85 words
The homepage has only about 85 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.
1 checks passed
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
8 other companies contacted
Loading the homepage contacts 8 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 rtv.rs, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Company
- Founded
- 1975
- Headquarters
- Novi Sad
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on rtv.rs, including 16 speed issues, 6 SEO 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.