Website review, no card needed

geostar.pt logo

geostar.pt website review

Visit site (opens in a new tab)Reviewed 18 November 202647 issues · 86 checks

This review found 47 issues worth fixing on geostar.pt, 17 of them high impact, across 86 checks. The most urgent: google Tag Manager adds 4.8 s. 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
4.8 s2.3 sMay 30Nov 144.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.7 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.7 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Oct 31, 20262.9 s
Nov 7, 20263.4 s
Nov 14, 20264.5 s
Real-visitor tap response (INP)75th percentile, phones
3.6 s0 msMay 30Nov 142.7 s
Show as table
DateReal-visitor tap response (INP)
May 30, 2026220 ms
Jun 6, 2026224 ms
Jun 13, 2026226 ms
Jun 20, 2026223 ms
Jun 27, 2026223 ms
Jul 4, 2026224 ms
Jul 11, 2026226 ms
Jul 18, 2026228 ms
Jul 25, 2026230 ms
Aug 1, 2026230 ms
Aug 8, 2026229 ms
Aug 15, 2026226 ms
Aug 22, 2026220 ms
Aug 29, 2026213 ms
Sep 5, 2026206 ms
Sep 12, 2026204 ms
Sep 19, 2026200 ms
Sep 26, 2026203 ms
Oct 3, 2026217 ms
Oct 10, 2026251 ms
Oct 17, 2026370 ms
Oct 24, 20261.9 s
Oct 31, 20263.1 s
Nov 7, 20262.9 s
Nov 14, 20262.7 s

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 geostar.pt (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix56
  • Google Tag Manager adds 4.8 s

    4.8 s

    Google Tag Manager costs a phone 4.8 s of main-thread work and 357 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 6.7 s

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

  • 5,325 HTML elements

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

  • 7 long tasks on the main thread

    7 long tasks block the main thread while loading, the longest for 5.6 s. During a long task the page ignores taps.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 708 KiB and 5.0 s of main-thread time.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    295 KiB

    About 295 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    290 KiB

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

  • Reduce unused CSS

    148 KiB

    About 148 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    22 KiB

    Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need.

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

1 checks passed
  • Server response: 494 ms

    494 ms

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

Core Web Vitals

13 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 INP: 6.6 s

    6.6 s

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

  • Total Blocking Time: 4.9 s

    4.9 s

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

  • Time to Interactive: 13.5 s

    13.5 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

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

    +1154%

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

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

    +49%

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

    Your largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Qualquer Companhia Aérea Económica Só voos diretos Todas as…”. Most of its time is element render delay (1.5 s).

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Speed Index: 4.4 s

    4.4 s

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

  • 1 image without width and height

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

2 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

100
  • 1 image in older formats

    1 image (59 KiB) is 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.

  • About 0.3 g of CO₂ per visit

    0.34 g

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

3 checks passed
  • Page weight: 1.2 MB in 32 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 32 requests on a phone: scripts 636 KiB (12), HTML 226 KiB (2) and other files 138 KiB (6). That is a lean page.

  • 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

11 to fixGoogle 6485
  • Certain ARIA roles must contain particular children (3 elements)

    Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must be contained by particular parents (3 elements)

    Certain ARIA roles must be contained by particular parents: 3 elements on the page fail this check, rated critical by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • Positive tabindex

    2 elements have a tabindex above 0, which scrambles the keyboard order.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 168 text elements with low contrast

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

  • Zoom is disabled

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

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

  • 51 form fields without a label

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

  • 3 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096
  • No structured data

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

  • 58 internal links, 6 external

    The homepage links to 58 pages on geostar.pt and 6 external pages.

7 checks passed
  • Meta description: 121 characters

    Your meta description is 121 characters: “Procuras uma agência de viagens? Temos as melhores ofertas para vários destinos e ao melhor preço de mercado. Visita-no…”.

  • One H1 headline

    Your main headline reads: “Agência de Viagens”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “A Tua Agência de Viagens Online com os Melhores Preços”.

  • Canonical URL set

    The canonical URL is https://www.netviagens.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://www.netviagens.pt/sitemap-index.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://www.netviagens.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 (3,943 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix74
  • 3 linked pages hidden from search

    https://www.netviagens.pt/voos-hotel/pesquisa/LIS-LGW/2026-12-30/2027-01-02/2adults/direct, https://www.netviagens.pt/voos-hotel/pesquisa/LIS-SSH/2026-12-30/2027-01-06/2adults and https://www.netviagens.pt/voos-hotel/pesquisa/LIS-GIG/2026-12-29/2027-01-05/2adults/direct are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 7 pages share a title

    /, https://www.netviagens.pt/area-cliente, https://www.netviagens.pt/area-cliente/dados-passageiros, https://www.netviagens.pt/area-cliente/dados-faturacao, https://www.netviagens.pt/area-cliente/proximas-viagens and https://www.netviagens.pt/area-cliente/viagens-realizadas and 1 other all use the title “A Tua Agência de Viagens Online com os Melhores Preços”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages share a meta description

    https://www.netviagens.pt/area-cliente, https://www.netviagens.pt/area-cliente/dados-passageiros, https://www.netviagens.pt/area-cliente/dados-faturacao, https://www.netviagens.pt/area-cliente/proximas-viagens, https://www.netviagens.pt/area-cliente/viagens-realizadas and https://www.netviagens.pt/area-cliente/favoritos use the same meta description. A description written for each page earns more clicks.

  • 8 links to non-canonical URLs

    Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.netviagens.pt/hoteis-baratos, whose canonical is https://www.netviagens.pt/hoteis-baratos-portugal-espanha. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://www.netviagens.pt/viagens-e-voos-baratos, https://www.netviagens.pt/hoteis-baratos, https://www.netviagens.pt/viagens-e-voos-low-cost-hotel, https://www.netviagens.pt/pacotes-de-viagens, https://www.netviagens.pt/viagens-ultima-hora-low-cost and https://www.netviagens.pt/cheque-viagem and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://www.netviagens.pt/area-cliente, https://www.netviagens.pt/area-cliente/dados-passageiros and https://www.netviagens.pt/area-cliente/favoritos took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://www.netviagens.pt/.

  • 3 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • 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.

  • A 29-field form

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

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

    The homepage carries about 578 words of visible text.

  • Urgency cues

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

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

  • Direct contact links

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

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 Meta Pixel (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.

  • 10 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Meo Empresas Meo Servicos De Comunicacoes E Multimedia S.A.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on geostar.pt, including 21 speed issues, 1 SEO issue 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