Website review, no card needed

sptelevisao.pt logo

sptelevisao.pt website review

Visit site (opens in a new tab)Reviewed 26 October 202633 issues · 69 checks

This review found 33 issues worth fixing on sptelevisao.pt, 18 of them high impact, across 69 checks. The most urgent: improve image delivery. 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

Full-page screenshot of sptelevisao.pt (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sptelevisao.pt at 1.1 s1.1 s
  2. sptelevisao.pt at 2.1 s2.1 s
  3. sptelevisao.pt at 3.2 s3.2 s
  4. sptelevisao.pt at 4.3 s4.3 s
  5. sptelevisao.pt at 5.4 s5.4 s
  6. sptelevisao.pt at 6.4 s6.4 s
  7. sptelevisao.pt at 7.5 s7.5 s
  8. sptelevisao.pt at 8.6 s8.6 s

Speed

6 to fix37
  • Improve image delivery

    12.4 s · 35.2 MB

    30 images could be 35.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 12.4 s faster on a phone.

  • Use efficient cache lifetimes

    4.5 s · 31.2 MB

    64 files are served with short cache lifetimes, so returning visitors download them again (31.2 MB).

  • Render-blocking requests

    3.3 s

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.

  • Reduce unused CSS

    2.4 s · 434 KiB

    About 434 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Mobile performance score: 37

    37/100

    Your mobile performance score is 37 (desktop: 45). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused JavaScript

    740 ms · 108 KiB

    About 108 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 740 ms faster on a phone.

  • Minify JavaScript

    150 ms · 8 KiB

    8 KiB could be saved by minifying JavaScript.

  • Document request latency

    111 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 55 ms. During a long task the page ignores taps.

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 143 ms of it running JavaScript. That is comfortably low.

  • Server response: 352 ms

    352 ms

    Your server sent the HTML in 352 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix41
  • Largest Contentful Paint: 49.2 s

    49.2 s

    Your largest element takes 49.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “slider hero image”.

  • Speed Index: 60.4 s

    60.4 s

    Visually, the page fills in at 60.4 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 118.0 s

    118.0 s

    The page becomes fully interactive after 118.0 s. Good is under 3.8 s.

  • First Contentful Paint: 4.6 s

    4.6 s

    The first text or image appears after 4.6 s on a phone. Good is under 1.8 s.

  • Cumulative Layout Shift: 0.422

    0.422

    The layout shifts by 0.422 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 27 images without width and height

    27 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Total Blocking Time: 3 ms

    3 ms

    Scripts block the page for only 3 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 65.8 MB in 68 requests

    65.8 MB

    Your homepage downloads 65.8 MB in 68 requests on a phone: images 65.0 MB (60), stylesheets 459 KiB (2) and scripts 196 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 35 images over 500 KB

    35 images weigh 58.2 MB together. On a phone connection a single image that size takes seconds.

  • 12 images far larger than shown

    19.9 MB

    12 images are downloaded at several times the size a phone draws them, for example site-homepage-carrossel-1-copy.png at 1,920 px wide, shown at 260 px. Resized copies would save about 19.9 MB.

  • 40 images in older formats

    40 images (59.3 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.

  • 1 image below the first screen load straight away

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

  • About 18.7 g of CO₂ per visit

    18.65 g

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

Accessibility

4 to fixGoogle 9394
  • 10 text elements with low contrast

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

  • 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 63 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 10084
  • Title is short (12 characters)

    Your title is only 12 characters: “SP Televisão”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (214 characters)

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 60 internal links, 11 external

    The homepage links to 60 pages on sptelevisao.pt and 11 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “SP Televisão”.

  • Canonical URL set

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

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

AI search readiness

1 to fix88
  • 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://sptelevisao.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.

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

  • Text is in the HTML

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

Other pages

3 to fix83
  • 3 pages share a title

    /, https://sptelevisao.pt/pt and https://sptelevisao.pt/en all use the title “SP Televisão”. 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://sptelevisao.pt/pt/sobre-a-sp-tv, https://sptelevisao.pt/pt/producoes, https://sptelevisao.pt/pt/noticias, https://sptelevisao.pt/pt/contactos and https://sptelevisao.pt/pt/noticias/2026/avenida-portugal-reforca-elenco-com-mais-nomes-de-peso have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://sptelevisao.pt/pt/noticias/2026/madalena-almeida-junta-se-ao-elenco-de-avenida-portugal, whose canonical is https://sptelevisao.pt/pt/noticias/2026/madalena-almeida-e-ana-sofia-martins-juntam-se-ao-elenco-de-avenida-portugal. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages with very little text

    https://sptelevisao.pt/pt/instalacoes-sp-televisao, https://sptelevisao.pt/pt/producoes and https://sptelevisao.pt/pt/contactos 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 49 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 an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 9687
  • 70 small tap targets

    70 of 100 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix40
  • 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 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 585 words of copy

    The homepage carries about 585 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

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

Upkeep, stack and company

Stack

Analytics
Google Analytics

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 sptelevisao.pt, including 12 speed issues, 3 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

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