Website review, no card needed

conventodoespinheiro.com logo

conventodoespinheiro.com website review

Visit site (opens in a new tab)Reviewed 19 October 202652 issues · 99 checks

This review found 52 issues worth fixing on conventodoespinheiro.com, 24 of them high impact, across 99 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

Real-visitor load time (LCP)75th percentile, phones
2.5 s1.8 sApr 25Oct 102.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.2 s
May 2, 20262.1 s
May 9, 20262.1 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.1 s
Aug 1, 20262.0 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.2 s
Sep 19, 20262.3 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
128 ms102 msApr 25Oct 10114 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026110 ms
May 2, 2026108 ms
May 9, 2026108 ms
May 16, 2026113 ms
May 23, 2026113 ms
May 30, 2026109 ms
Jun 6, 2026107 ms
Jun 13, 2026105 ms
Jun 20, 2026111 ms
Jun 27, 2026115 ms
Jul 4, 2026114 ms
Jul 11, 2026121 ms
Jul 18, 2026119 ms
Jul 25, 2026125 ms
Aug 1, 2026125 ms
Aug 8, 2026120 ms
Aug 15, 2026121 ms
Aug 22, 2026120 ms
Aug 29, 2026118 ms
Sep 5, 2026120 ms
Sep 12, 2026117 ms
Sep 19, 2026112 ms
Sep 26, 2026113 ms
Oct 3, 2026112 ms
Oct 10, 2026114 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

Full-page screenshot of conventodoespinheiro.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. conventodoespinheiro.com at 0.9 s0.9 s
  2. conventodoespinheiro.com at 1.8 s1.8 s
  3. conventodoespinheiro.com at 2.7 s2.7 s
  4. conventodoespinheiro.com at 3.6 s3.6 s
  5. conventodoespinheiro.com at 4.5 s4.5 s
  6. conventodoespinheiro.com at 5.4 s5.4 s
  7. conventodoespinheiro.com at 6.3 s6.3 s
  8. conventodoespinheiro.com at 7.2 s7.2 s

Speed

11 to fix30
  • Improve image delivery

    11.1 s · 6.8 MB

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

  • Use efficient cache lifetimes

    5.4 s · 968 KiB

    27 files are served with short cache lifetimes, so returning visitors download them again (968 KiB).

  • Reduce unused JavaScript

    2.6 s · 430 KiB

    About 430 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.

  • Mobile performance score: 30

    30/100

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

  • Main-thread work: 4.4 s

    A phone's processor spends 4.4 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 4,186 HTML elements

    The page has 4,186 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (paraty.es, Google Tag Manager and Clarity and others), adding 9.6 MB and 1.5 s of main-thread time.

  • paraty.es adds 823 ms

    823 ms

    paraty.es costs a phone 823 ms of main-thread work and 8.9 MB 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.

  • Reduce unused CSS

    920 ms · 205 KiB

    About 205 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 920 ms faster on a phone.

  • Google Tag Manager adds 484 ms

    484 ms

    Google Tag Manager costs a phone 484 ms of main-thread work and 512 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.

  • Legacy JavaScript

    300 ms · 19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • 16 long tasks on the main thread

    16 long tasks block the main thread while loading, the longest for 201 ms. During a long task the page ignores taps.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 202 ms

    202 ms

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

Core Web Vitals

12 to fix33
  • 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.

  • Real-user CLS: 0.26

    0.26

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

  • Largest Contentful Paint: 42.0 s

    42.0 s

    Your largest element takes 42.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Convento do Espinheiro: paisagem com jardins, edifício cont…”.

  • Time to Interactive: 42.8 s

    42.8 s

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

  • Speed Index: 14.0 s

    14.0 s

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

  • Cumulative Layout Shift: 0.415

    0.415

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user LCP: 3.1 s

    3.1 s

    Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 2.1 s

    2.1 s

    Real visitors see the first content after 2.1 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.

  • Total Blocking Time: 417 ms

    417 ms

    Scripts block taps and scrolling for 417 ms in total while the page loads. Good is under 200 ms.

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

1 checks passed
  • Real-user INP: 130 ms

    130 ms

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

Images and page weight

1 to fix70
  • Page weight: 12.0 MB in 138 requests

    12.0 MB

    Your homepage downloads 12.0 MB in 138 requests on a phone: images 8.4 MB (45), fonts 1.9 MB (15) and scripts 1.1 MB (30). Under 2 MB keeps phones on slow connections fast.

  • About 3.4 g of CO₂ per visit

    3.39 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.39 g of CO₂e: 407.3 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

15 to fixGoogle 6283
  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • 17 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • 2 tap targets too small

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

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

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

    All page content should be contained by landmarks: 7 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.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate 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.

  • 16 links without text

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

  • 11 form fields without a label

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

  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (4 elements)

    Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

2 to fixGoogle 8595
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 69 internal links, 14 external

    The homepage links to 69 pages on conventodoespinheiro.com and 14 external pages.

7 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Hotel 5 estrelas em Évora, instalado num convento do século XV. Desfrute de uma estadia inesquecível, spa, gastronomia …”.

  • One H1 headline

    Your main headline reads: “Um convento do século XV. Uma estadia única em Évora.”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Hotel de Luxo em Évora | Convento do Espinheiro”.

  • Canonical URL set

    The canonical URL is https://www.conventodoespinheiro.com/.

  • Structured data in place

    Structured data found: Hotel.

  • 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.conventodoespinheiro.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.conventodoespinheiro.com/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 (1,028 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://www.conventodoespinheiro.com/False, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 11 pages without an H1

    https://www.conventodoespinheiro.com/quartos.html, https://www.conventodoespinheiro.com/ofertas.html, https://www.conventodoespinheiro.com/spa.html, https://www.conventodoespinheiro.com/restaurantes.html, https://www.conventodoespinheiro.com/vouchers.html and https://www.conventodoespinheiro.com/minhas-reservas.html and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 8883
  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 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 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    118 of 127 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 9-field form

    Your longest form asks for 9 fields (0 required). Every extra field lowers completion.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

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

4 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies (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.

  • 18 other companies contacted

    Loading the homepage contacts 18 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 conventodoespinheiro.com, 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 Tag Manager | Hotjar
Hosting
Google Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on conventodoespinheiro.com, including 23 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