Website review, no card needed

prio.pt logo

prio.pt website review

Visit site (opens in a new tab)Reviewed 17 November 202624 issues · 59 checks

This review found 24 issues worth fixing on prio.pt, 6 of them high impact, across 59 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
3.6 s2.1 sMay 30Nov 142.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.9 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.3 s
Jun 27, 20263.4 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.1 s
Jul 25, 20263.0 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.1 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20263.0 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Nov 7, 20262.3 s
Nov 14, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
445 ms383 msMay 30Nov 14420 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026416 ms
Jun 6, 2026414 ms
Jun 13, 2026412 ms
Jun 20, 2026422 ms
Jun 27, 2026430 ms
Jul 4, 2026426 ms
Jul 11, 2026426 ms
Jul 18, 2026410 ms
Jul 25, 2026401 ms
Aug 1, 2026408 ms
Aug 8, 2026412 ms
Aug 15, 2026421 ms
Aug 22, 2026427 ms
Aug 29, 2026429 ms
Sep 5, 2026434 ms
Sep 12, 2026438 ms
Sep 19, 2026427 ms
Sep 26, 2026420 ms
Oct 3, 2026409 ms
Oct 10, 2026398 ms
Oct 17, 2026396 ms
Oct 24, 2026390 ms
Oct 31, 2026393 ms
Nov 7, 2026403 ms
Nov 14, 2026420 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

3 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user INP: 420 ms

    420 ms

    Real visitors wait 420 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user TTFB: 915 ms

    915 ms

    Real visitors wait 915 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 416 ms to 420 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

    Real 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.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Largest content (LCP) got 23% faster for real visitors

    -23%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

3 to fix65
  • Page weight: 3.7 MB

    3.7 MB

    Your homepage downloads 3.7 MB on a phone, 1.2 MB of it images (33%). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

    8 images (1.0 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.

  • 5 images far larger than shown

    477 KiB

    5 images are downloaded at several times the size a phone draws them, for example 1774631996_29c63719a5afb878fdf46206dbcb693c.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 477 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (190 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.06 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 126.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

7 to fix91
  • 19 text elements with low contrast

    19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • 3 images without alt text

    3 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 8 links without text

    8 visible links have no text or label, so screen readers cannot say where they go.

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fix90
  • 2 H1 headlines

    There are 2 <h1> headlines (“PRIO - Combust�veis, Mobilidade el�trica e G�s” and “Servi�os e produtos de qualidade”). One clear main headline is easier for people and search engines.

  • Meta description is long (203 characters)

    Your meta description is 203 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 139 internal links, 15 external

    The homepage links to 139 pages on prio.pt and 15 external pages.

6 checks passed
  • Title: 46 characters

    Your title is a healthy 46 characters: “PRIO - Combust�veis, Mobilidade el�trica e G�s”.

  • Canonical URL set

    The canonical URL is https://www.prio.pt/pt/.

  • Structured data in place

    Structured data found: OnlineStore, WebPage and WebSite.

  • 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://www.prio.pt/sitemap.xml.

AI search readiness

100
4 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 contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,213 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.prio.pt/llms.txt (4 KiB, 44 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix78
  • 2 pages share a title

    https://www.prio.pt/pt/postos/rede-de-postos_289.html and https://www.prio.pt/pt/mobilidade-eletrica/rede-de-carregamento-prio_297-.html all use the title “Localizar um posto PRIO”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.prio.pt/pt/postos/rede-de-postos_289.html, https://www.prio.pt/pt/postos/lubrificantes_251.html, https://www.prio.pt/pt/duplicado-de-fatura, https://www.prio.pt/pt/mobilidade-eletrica/rede-de-carregamento-prio_297-.html and https://www.prio.pt/pt/mobilidade-eletrica/informacao-faturacao-uve_427.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.prio.pt/pt/app_237.html, whose canonical is https://www.prio.pt/pt/prio-pt/app_237.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.prio.pt/pt/app_237.html has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.prio.pt/pt/gas-engarrafado_226-301.html took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 54 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

1 to fix93
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://1644979638.rsc.cdn77.org/plugins/search_meilisearch/css/rcc_search.base.min.css?17…”.

2 checks passed
  • Tap targets are thumb-sized

    25 of 31 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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: 1 testimonial or review block. 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 385 words of copy

    The homepage carries about 385 words of visible text.

2 checks passed
  • 4 short forms

    4 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Clarity and 3 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 1 of them by other companies (measured from a US location before any click).

  • 27 other companies contacted

    Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 prio.pt, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Redicom Prolepse
Framework
Angular
Analytics
Google Tag Manager
Hosting
Claranet

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on prio.pt, including 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25