Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

heineken.gr

Καλώς ήρθατε στον κόσμο της Heineken® | Heineken.com

Page Load Speed

2.4 sec in total

First Response

272 ms

Resources Loaded

2.1 sec

Page Rendered

0 ms

About Website

Visit heineken.gr now to see the best up-to-date Heineken content and also check out these interesting facts you probably never knew about heineken.gr

Καλώς ήρθατε στον επίσημο ιστότοπο της Heineken®. Ανακαλύψτε την ιστορία μας. Εξερευνήστε τα προϊόντα μας. Και απολαύστε υπεύθυνα.

Visit heineken.gr

Key Findings

We analyzed Heineken.gr page load time and found that the first response time was 272 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

heineken.gr performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

60/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value1,170 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

heineken.gr

272 ms

444 ms

home

454 ms

agegateway

634 ms

style.3276ab6a.css

19 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 9% of them (1 request) were addressed to the original Heineken.gr, 55% (6 requests) were made to Heineken.com and 18% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (634 ms) relates to the external source Heineken.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 205.8 kB (67%)

Content Size

307.5 kB

After Optimization

101.8 kB

In fact, the total size of Heineken.gr main page is 307.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 5% of websites need less resources to load. CSS take 199.5 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 15.1 kB

  • Original 21.2 kB
  • After minification 20.3 kB
  • After compression 6.1 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 15.1 kB or 71% of the original size.

JavaScript Optimization

-21%

Potential reduce by 18.6 kB

  • Original 86.8 kB
  • After minification 86.8 kB
  • After compression 68.2 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 18.6 kB or 21% of the original size.

CSS Optimization

-86%

Potential reduce by 172.1 kB

  • Original 199.5 kB
  • After minification 197.9 kB
  • After compression 27.5 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. Heineken.gr needs all CSS files to be minified and compressed as it can save up to 172.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (43%)

Requests Now

7

After Optimization

4

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

Accessibility Review

heineken.gr accessibility score

96

Accessibility Issues

Names and labels

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.

Impact

Issue

High

Links do not have a discernible name

Best Practices

heineken.gr best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

heineken.gr SEO score

75

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

Mobile Friendly

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/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EL

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Heineken.gr can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it does not match the claimed English language. Our system also found out that Heineken.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 description is not detected on the main page of Heineken. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: