Website review, no card needed
ogma.pt website review
Visit site (opens in a new tab)Reviewed 18 November 202636 issues · 78 checks
This review found 36 issues worth fixing on ogma.pt, 15 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.9 s |
| Jun 6, 2026 | 5.2 s |
| Jun 13, 2026 | 5.3 s |
| Jun 20, 2026 | 5.1 s |
| Jun 27, 2026 | 5.4 s |
| Jul 4, 2026 | 5.3 s |
| Jul 11, 2026 | 5.2 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 5.0 s |
| Aug 1, 2026 | 4.9 s |
| Aug 8, 2026 | 4.9 s |
| Aug 15, 2026 | 5.0 s |
| Aug 22, 2026 | 5.0 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.9 s |
| Sep 26, 2026 | 4.9 s |
| Oct 3, 2026 | 4.9 s |
| Oct 10, 2026 | 5.0 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 5.0 s |
| Oct 31, 2026 | 5.2 s |
| Nov 7, 2026 | 5.2 s |
| Nov 14, 2026 | 5.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 106 ms |
| Jun 6, 2026 | 108 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 106 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 107 ms |
| Jul 18, 2026 | 110 ms |
| Jul 25, 2026 | 109 ms |
| Aug 1, 2026 | 109 ms |
| Aug 8, 2026 | 109 ms |
| Aug 15, 2026 | 104 ms |
| Aug 22, 2026 | 106 ms |
| Aug 29, 2026 | 102 ms |
| Sep 5, 2026 | 105 ms |
| Sep 12, 2026 | 104 ms |
| Sep 19, 2026 | 102 ms |
| Sep 26, 2026 | 103 ms |
| Oct 3, 2026 | 100 ms |
| Oct 10, 2026 | 101 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 106 ms |
| Oct 31, 2026 | 111 ms |
| Nov 7, 2026 | 112 ms |
| Nov 14, 2026 | 111 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
Speed
Use efficient cache lifetimes
3.9 s · 1.5 MB68 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Improve image delivery
2.6 s · 588 KiB4 images could be 588 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.
Render-blocking requests
2.4 s33 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Google CDN adds 350 ms
350 msGoogle CDN costs a phone 350 ms of main-thread work and 739 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.
Reduce unused JavaScript
392 KiBAbout 392 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 964 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3 third-party services on the page
3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and JSDelivr CDN), adding 775 KiB and 387 ms of main-thread time.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 141 ms. During a long task the page ignores taps.
Reduce unused CSS
35 KiBAbout 35 KiB of CSS is downloaded but never applied on this page.
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: 114 ms
114 msYour server sent the HTML in 114 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 LCP: 5.1 s
5.1 sReal visitors wait 5.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.9 s
4.9 sReal visitors see the first content after 4.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.9 s
3.9 sReal visitors wait 3.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 14.4 s
14.4 sVisually, the page fills in at 14.4 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 6.5 s
6.5 sYour largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Um legado construído por pessoas. Um futuro moldado pelo pr…”. Most of its time is element render delay (8.6 s).
Time to Interactive: 13.5 s
13.5 sThe page becomes fully interactive after 13.5 s. Good is under 3.8 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 106 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.9 s to 5.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 112 ms
112 msReal visitors wait 112 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Total Blocking Time: 130 ms
130 msScripts block the page for only 130 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.047
0.047The layout barely moves while loading (CLS 0.047, good is under 0.1).
Images and page weight
Page weight: 2.6 MB in 79 requests
2.6 MBYour homepage downloads 2.6 MB in 79 requests on a phone: images 948 KiB (8), scripts 896 KiB (29) and fonts 370 KiB (3). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (646 KiB) 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.
3 images far larger than shown
406 KiB3 images are downloaded at several times the size a phone draws them, for example img_9406.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 406 KiB.
3 images below the first screen load straight away
3 images further down the page (646 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.75 g of CO₂e: 90.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
47 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: 47 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (11 characters)
Your title is only 11 characters: “Home - OGMA”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
77 internal links, 17 external
The homepage links to 77 pages on ogma.pt and 17 external pages.
6 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “Um legado construído por pessoas. Um futuro moldado pelo propósito. Carreiras e Oportunidades Perfil da empresa Na OGMA…”.
One H1 headline
Your main headline reads: “Um legado construído por pessoas. Um futuro moldado pelo propósito.”.
Canonical URL set
The canonical URL is https://www.ogma.pt/.
Structured data in place
Structured data found: Airline, Article, ImageObject, Organization and Person.
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.ogma.pt/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. 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.ogma.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 (587 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://www.ogma.pt/en all use the title “Home - OGMA”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without an H1
https://www.ogma.pt/sobre-nos, https://www.ogma.pt/sobre-nos/perfil-da-empresa, https://www.ogma.pt/servicos, https://www.ogma.pt/academia, https://www.ogma.pt/contactos and https://www.ogma.pt/carreiras-e-oportunidades and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages slow to respond
https://www.ogma.pt/sobre-nos, https://www.ogma.pt/sobre-nos/perfil-da-empresa, https://www.ogma.pt/servicos, https://www.ogma.pt/academia, https://www.ogma.pt/contactos and https://www.ogma.pt/en and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
5 checks passed
Linked pages load
9 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 9 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 17 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 “Access to font at 'https://ogmadev.chitas.cloud/wp-content/uploads/elementor/google-fonts/fonts/roboto-kfo7cnqeu92fr1me…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Only about 246 words
The homepage has only about 246 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
2 short forms
2 short forms (3 fields at most) are right on the homepage, asking for an email.
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
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 ogma.pt, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Vodafone Portugal - Communicacoes Pessoais S.A.
Company
- Founded
- 1918
- Headquarters
- Alverca do Ribatejo e Sobralinho
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on ogma.pt, including 16 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.