Access atrium.gr.

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value42.7 s

0/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value36.9 s

0/100

10%

atrium.gr

279 ms

atrium.gr

347 ms

1084 ms

gtm.js

69 ms

trp-language-switcher.css

172 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Atrium.gr, 85% (46 requests) were made to Atriumhotels.gr and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Atriumhotels.gr.

Content Size

25.1 MB

After Optimization

24.5 MB

In fact, the total size of Atrium.gr main page is 25.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 24.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 326.7 kB

Original 395.5 kB
After minification 376.7 kB
After compression 68.7 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 326.7 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 225.5 kB

Original 24.4 MB
After minification 24.2 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Atrium images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 87.3 kB

Original 309.3 kB
After minification 309.3 kB
After compression 222.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 87.3 kB or 28% of the original size.

CSS Optimization

-9%

Potential reduce by 2.0 kB

Original 23.7 kB
After minification 23.7 kB
After compression 21.7 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Atrium.gr has all CSS files already compressed.

Requests Now

After Optimization

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Atrium. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Atrium.gr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Atrium.gr main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph data is detected on the main page of Atrium. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: