fpb.pt website review

Not measured in this review.

• Largest content (LCP) got 27% slower for real visitors

  +27%

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

• Real-user FCP: 1.8 s

  1.8 s

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

• Real-user TTFB: 1.6 s

  1.6 s

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

• Tap response (INP) held steady for real visitors

  +8%

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

• Page weight: 5.2 MB

  5.2 MB

  Your homepage downloads 5.2 MB on a phone, 3.4 MB of it images (65%). Under 2 MB keeps phones on slow connections fast.

• 2 images over 500 KB

  2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.

  Elements (2)

• 3 images far larger than shown

  784 KiB

  3 images are downloaded at several times the size a phone draws them, for example SiteAds_fpb_pleno_302x302-copy-4.jpg at 1,259 px wide, shown at 338 px. Resized copies would save about 784 KiB.

  Elements (3)

• 12 images in older formats

  12 images (2.7 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.

  Elements (5)

• 4 images below the first screen load straight away

  4 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (4)

• About 1.5 g of CO₂ per visit

  1.46 g

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

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

  Elements (1)

• Frames without titles

  1 frame has no title, so screen-reader users cannot tell what it contains.

  Elements (1)

• <html> element must have a lang attribute (1 element)

  <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• Positive tabindex

  1 element has a tabindex above 0, which scrambles the keyboard order.

  Elements (1)

• 42 images without alt text

  42 images have no alt text, which hurts accessibility and image search.

  View sourceElements (3)

• All page content should be contained by landmarks (35 elements)

  All page content should be contained by landmarks: 35 elements on the page fail this check, rated moderate by axe-core.

  Elements (3)

• 7 links without text

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

  Elements (3)

• 4 form fields without a label

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

  View source

• No page language

  The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  View source

• Headings skip levels

  Headings skip levels (h2 → h4, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

  View sourceElements (3)

• 2 H1 headlines

  There are 2 <h1> headlines (“Subscrever Newsletter” and “Subscrever Newsletter”). One clear main headline is easier for people and search engines.

• Meta description is long (180 characters)

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

  View source

• 124 internal links, 54 external

  The homepage links to 124 pages on fpb.pt and 54 external pages.

• No llms.txt

  There is no https://www.fpb.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.

• 1 page without a meta description

  https://www.fpb.pt/denuncia has no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (1)

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 101 found) and read each the way a search engine does.

• 22 small tap targets

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

• 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 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,310 words of copy

  The homepage carries about 1,310 words of visible text.

• 3 trackers load before any consent

  3

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

• 3 cookies set on arrival

  3

  Opening the homepage sets 3 cookies (measured from a US location before any click).

• 17 other companies contacted

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