pergolux.com.br website review

Not measured in this review.

• 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: 361 ms

  361 ms

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

• Tap response (INP) got 85% slower for real visitors

  +85%

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

• Real-user TTFB: 1.0 s

  1.0 s

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

• Page weight: 3.0 MB

  3.0 MB

  Your homepage downloads 3.0 MB on a phone, 278 KiB of it images (9%). Under 2 MB keeps phones on slow connections fast.

• About 0.8 g of CO₂ per visit

  0.84 g

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

• 20 text elements with low contrast

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

  Elements (3)

• Hidden but focusable

  1 element hidden from screen readers can still receive keyboard focus.

  Elements (1)

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

  Elements (1)

• 1 link without text

  1 visible link has no text or label, so screen readers cannot say where it goes.

  Elements (1)

• Headings skip levels

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

  View sourceElements (1)

• 2 H1 headlines

  There are 2 <h1> headlines (“Black Friday PERGOLUX” and “Comece pelo configurador.”). One clear main headline is easier for people and search engines.

  View source

• Meta description is long (216 characters)

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

  View source

• Structured data has 1 problem

  Structured data found (OnlineStore, Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

  View source

• No robots.txt

  There is no robots.txt at pergolux.com.br/robots.txt, the first file search crawlers ask for.

• 49 internal links, 2 external

  The homepage links to 49 pages on pergolux.com.br and 2 external pages.

• No llms.txt

  There is no https://pergolux.com.br/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 pages without a meta description

  https://pergolux.com.br/pages/awning-configurator and https://pergolux.com.br/policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (2)

• 1 page without an H1

  https://pergolux.com.br/collections/pergolas-bioclimaticas-pergolux has no <h1> headline, so visitors and search engines get no clear main topic.

• 1 page slow to respond

  https://pergolux.com.br/pages/awning-configurator took over 3 s to send its HTML from our server.

• 14 internal pages checked

  We fetched 14 pages linked from your homepage and read each the way a search engine does.

• 1 broken image

  1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187052842&tm=gtm002&Ver=2&mid=c7dbbf5b-877a-4d5a-8d9c-07b76792354f&bo=1&sid=5c589e40dd1e11f1bd6445d3bf79906e&vid=5c58b490dd1e11f199f76d54a6ae5e18&vids=1&msclkid=N&pi=9.

• 7 small tap targets

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

• 6 JavaScript errors while loading

  6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

  The homepage carries about 675 words of visible text.

• Urgency cues

  The page uses urgency cues (a countdown or limited-time wording).

• 7 trackers load before any consent

  7

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.

• 26 cookies set on arrival

  26

  Opening the homepage sets 26 cookies, 3 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.

• 38 other companies contacted

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