Website review, no card needed
aktor.gr website review
Visit site (opens in a new tab)Reviewed 20 October 202641 issues · 80 checks
This review found 41 issues worth fixing on aktor.gr, 17 of them high impact, across 80 checks. The most urgent: render-blocking requests. 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.8 s |
| May 9, 2026 | 3.8 s |
| May 16, 2026 | 3.8 s |
| May 23, 2026 | 3.9 s |
| May 30, 2026 | 3.8 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 4.2 s |
| Jul 11, 2026 | 4.5 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.7 s |
| Aug 1, 2026 | 4.6 s |
| Aug 8, 2026 | 4.3 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 4.0 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 111 ms |
| May 9, 2026 | 111 ms |
| May 16, 2026 | 110 ms |
| May 23, 2026 | 108 ms |
| May 30, 2026 | 108 ms |
| Jun 6, 2026 | 109 ms |
| Jun 13, 2026 | 109 ms |
| Jun 20, 2026 | 109 ms |
| Jun 27, 2026 | 110 ms |
| Jul 4, 2026 | 113 ms |
| Jul 11, 2026 | 116 ms |
| Jul 18, 2026 | 116 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 117 ms |
| Aug 8, 2026 | 116 ms |
| Aug 15, 2026 | 119 ms |
| Aug 22, 2026 | 117 ms |
| Aug 29, 2026 | 117 ms |
| Sep 5, 2026 | 119 ms |
| Sep 12, 2026 | 116 ms |
| Sep 19, 2026 | 117 ms |
| Sep 26, 2026 | 116 ms |
| Oct 3, 2026 | 114 ms |
| Oct 10, 2026 | 116 ms |
| Oct 17, 2026 | 117 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
Render-blocking requests
3.1 s42 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Improve image delivery
1.6 s · 321 KiB8 images could be 321 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Reduce unused JavaScript
1.0 s · 685 KiBAbout 685 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.0 s faster on a phone.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 910 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 59
59/100Your mobile performance score is 59 (desktop: 75). Pages that score under 90 lose visitors before the first paint.
inbroker.com adds 318 ms
318 msinbroker.com costs a phone 318 ms of main-thread work and 706 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.
1,953 HTML elements
The page has 1,953 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
4 third-party services on the page
4 third-party services load with your homepage (inbroker.com, JSDelivr CDN and Google Fonts and others), adding 762 KiB and 337 ms of main-thread time.
Use efficient cache lifetimes
250 ms · 42 KiB7 files are served with short cache lifetimes, so returning visitors download them again (42 KiB).
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 190 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 5 KiB5 KiB could be saved by minifying JavaScript.
Reduce unused CSS
71 KiBAbout 71 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 207 ms
207 msYour server sent the HTML in 207 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.0 s
5.0 sReal visitors wait 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.6 s
2.6 sReal visitors wait 2.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 15.6 s
15.6 sYour largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 15.7 s
15.7 sThe page becomes fully interactive after 15.7 s. Good is under 3.8 s.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
Real-user CLS: 0.24
0.24For real visitors the layout shifts by 0.24 (75th percentile). Good is under 0.1.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 213 ms
213 msScripts block taps and scrolling for 213 ms in total while the page loads. Good is under 200 ms.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 111 ms to 117 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.8 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.4 MB in 109 requests
3.4 MBYour homepage downloads 3.4 MB in 109 requests on a phone: images 2.1 MB (26), scripts 1.0 MB (36) and stylesheets 128 KiB (40). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
0.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
30 images without alt text
30 images have no alt text, which hurts accessibility and image search.
Invalid ARIA attributes
3 elements use ARIA attributes their role does not allow, which confuses screen readers.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
11 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 14 WCAG 2.2 A/AA and best-practice rules on the phone render: 11 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
320 internal links, 10 external
The homepage links to 320 pages on aktor.gr and 10 external pages.
8 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Ανακαλύψτε τον Όμιλο Aktor, πρωτοπόρο στους τομείς των κατασκευών, της ενέργειας, των παραχωρήσεων, των ακινήτων και τη…”.
One H1 headline
Your main headline reads: “ΜΙΑ ΝΕΑ ΕΠΟΧΗ ΕΞΕΛΙΞΗΣ”.
Title: 35 characters
Your title is a healthy 35 characters: “Όμιλος Aktor | Ηγέτης στις Υποδομές”.
Canonical URL set
The canonical URL is https://aktor.gr/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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://aktor.gr/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.
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.
llms.txt published
The site publishes https://aktor.gr/llms.txt (4 KiB, 26 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://aktor.gr/ependytes and https://aktor.gr/el/ependytes all use the title “Όμιλος Aktor | Ενημέρωση Επενδυτών”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://aktor.gr/en/projects and https://aktor.gr/lng have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://aktor.gr/ependytes and https://aktor.gr/el/ependytes use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://aktor.gr/el/ependytes, whose canonical is https://aktor.gr/ependytes. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://aktor.gr/en/projects has 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 75 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was 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
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 25 words
The homepage has only about 25 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie, 1 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.
1 other company contacted
Loading the homepage contacts 1 host 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 aktor.gr, 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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on aktor.gr, including 18 speed issues, 1 SEO issue and 6 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.