Website review, no card needed
radiopopular.pt website review
Visit site (opens in a new tab)Reviewed 30 October 202651 issues · 100 checks
This review found 51 issues worth fixing on radiopopular.pt, 21 of them high impact, across 100 checks. The most urgent: use efficient cache lifetimes. 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 261 ms |
| May 16, 2026 | 258 ms |
| May 23, 2026 | 257 ms |
| May 30, 2026 | 262 ms |
| Jun 6, 2026 | 270 ms |
| Jun 13, 2026 | 278 ms |
| Jun 20, 2026 | 285 ms |
| Jun 27, 2026 | 291 ms |
| Jul 4, 2026 | 293 ms |
| Jul 11, 2026 | 292 ms |
| Jul 18, 2026 | 291 ms |
| Jul 25, 2026 | 291 ms |
| Aug 1, 2026 | 292 ms |
| Aug 8, 2026 | 294 ms |
| Aug 15, 2026 | 299 ms |
| Aug 22, 2026 | 302 ms |
| Aug 29, 2026 | 303 ms |
| Sep 5, 2026 | 306 ms |
| Sep 12, 2026 | 303 ms |
| Sep 19, 2026 | 303 ms |
| Sep 26, 2026 | 309 ms |
| Oct 3, 2026 | 312 ms |
| Oct 10, 2026 | 314 ms |
| Oct 17, 2026 | 317 ms |
| Oct 24, 2026 | 313 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.5 s
3.0 s
4.6 s
6.1 s
7.6 s
9.1 s
10.6 s
12.2 s
Speed
Use efficient cache lifetimes
1.6 s · 4.5 MB176 files are served with short cache lifetimes, so returning visitors download them again (4.5 MB).
Reduce unused JavaScript
4.2 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.
Render-blocking requests
5.0 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.0 s.
12,007 HTML elements
The page has 12,007 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Tag Manager adds 1.0 s
1.0 sGoogle Tag Manager costs a phone 1.0 s of main-thread work and 726 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 10.9 s
A phone's processor spends 10.9 s on main-thread work while loading, 5.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 29
29/100Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Prefix Box AI Search and Facebook and others), adding 1.9 MB and 2.5 s of main-thread time.
Improve image delivery
500 ms · 1.2 MB52 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.4 s. During a long task the page ignores taps.
Reduce unused CSS
900 ms · 164 KiBAbout 164 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Minify JavaScript
750 ms · 149 KiB149 KiB could be saved by minifying JavaScript.
Prefix Box AI Search adds 360 ms
360 msPrefix Box AI Search costs a phone 360 ms of main-thread work and 297 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.
Facebook adds 337 ms
337 msFacebook costs a phone 337 ms of main-thread work and 217 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.
TikTok adds 316 ms
316 msTikTok costs a phone 316 ms of main-thread work and 169 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 CDN adds 183 ms
183 msGoogle CDN costs a phone 183 ms of main-thread work and 303 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
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
57 KiBPolyfills for old browsers add 57 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 CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 333 ms
333 msYour server sent the HTML in 333 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: 24.6 s
24.6 sYour largest element takes 24.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hallow Iva Desconto Direto + 5% Extra Talão em todas as cat…”.
Speed Index: 17.0 s
17.0 sVisually, the page fills in at 17.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 40.2 s
40.2 sThe page becomes fully interactive after 40.2 s. Good is under 3.8 s.
Total Blocking Time: 2.0 s
2.0 sScripts block taps and scrolling for 2.0 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.2 s
4.2 sThe first text or image appears after 4.2 s on a phone. Good is under 1.8 s.
Real-user INP: 374 ms
374 msReal visitors wait 374 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 261 ms to 313 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 476 ms
476 msReal visitors wait 476 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.045
0.045The layout barely moves while loading (CLS 0.045, good is under 0.1).
Images and page weight
Page weight: 7.8 MB in 308 requests
7.8 MBYour homepage downloads 7.8 MB in 308 requests on a phone: images 4.0 MB (164), scripts 3.1 MB (63) and other files 289 KiB (59). Under 2 MB keeps phones on slow connections fast.
About 2.2 g of CO₂ per visit
2.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.22 g of CO₂e: 266.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
87 images without alt text
87 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
ARIA role should be appropriate for the element (75 elements)
ARIA role should be appropriate for the element: 75 elements on the page fail this check, rated minor by axe-core.
28 links without text
28 visible links have no text or label, so screen readers cannot say where they go.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (5 elements)
Headings should not be empty: 5 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
48 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: 48 passed and 10 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 H1 headlines
There are 4 <h1> headlines (“Junta-te à Radio Popular”, “Ganhar está ON” and “Ganhar está ON”). One clear main headline is easier for people and search engines.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
2,348 internal links, 17 external
The homepage links to 2,348 pages on radiopopular.pt and 17 external pages.
7 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Compre na Radio Popular, Computadores, Portáteis, Smart Phones, Frigoríficos, Combinados, Tvs, Máq. Fotográficas, Café,…”.
Title: 37 characters
Your title is a healthy 37 characters: “Radio Popular | Entregas em 24 horas!”.
Canonical URL set
The canonical URL is https://www.radiopopular.pt/.
Structured data in place
Structured data found: Organization.
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://lojae-s3-prd-files.radiopopular.pt/files/sitemaps/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.radiopopular.pt/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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (9,695 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.radiopopular.pt/links declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
4 pages share a title
/, https://www.radiopopular.pt/esg-sustentabilidade, https://www.radiopopular.pt/clube-rp and https://www.radiopopular.pt/links all use the title “Radio Popular | Entregas em 24 horas!”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://www.radiopopular.pt/esg-sustentabilidade, https://www.radiopopular.pt/clube-rp and https://www.radiopopular.pt/marcas have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.radiopopular.pt/esg-sustentabilidade, https://www.radiopopular.pt/servicos, https://www.radiopopular.pt/clube-rp, https://www.radiopopular.pt/links, https://www.radiopopular.pt/marcas and https://www.radiopopular.pt/categoria/grandes-eletrodomesticos and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
8 pages slow to respond
https://www.radiopopular.pt/links, https://www.radiopopular.pt/marcas, https://www.radiopopular.pt/categoria/grandes-eletrodomesticos, https://www.radiopopular.pt/categoria/maquinas-de-roupa, https://www.radiopopular.pt/categoria/maquinas-de-lavar-e-secar-roupa-de-encastre and https://www.radiopopular.pt/categoria/acessorios-maquinas-de-secar-roupa and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 180 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 broken images
3 images failed to load on a phone, for example https://ib.adnxs.com/setuid?entity=315&code=81yfKLybaAx-SqjNnyDz24VoUbiML5xaURx3_LH23jc&consent=1.
37 small tap targets
37 of 80 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “sendCartRpToChatwoot is not defined”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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,371 words of copy
The homepage carries about 1,371 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: “Pet Shop”.
2 calls to action
The homepage has 2 calls to action, for example “Pet Shop – Animais de Estimação” and “Pet Shop”.
Social proof on the page
Social proof on the homepage: 8 customer or partner logos and 10 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 5 mores (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.
25 cookies set on arrival
25Opening the homepage sets 25 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.
51 other companies contacted
Loading the homepage contacts 51 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 radiopopular.pt, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on radiopopular.pt, including 25 speed issues, 2 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.