Tools & Wizards About Us
heineken.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

heineken.com

Welcome to the world of Heineken® | Heineken.com

Page Load Speed

3.5 sec in total

First Response

277 ms

Resources Loaded

1.3 sec

Page Rendered

1.9 sec

heineken.com screenshot

About Website

Click here to check amazing Heineken content for United States. Otherwise, check out these important facts you probably never knew about heineken.com

Welcome to the official Heineken® website. Discover our story. Explore our beer products. And enjoy responsibly.

Visit heineken.com

Key Findings

We analyzed Heineken.com page load time and found that the first response time was 277 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

heineken.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value6.5 s

38/100

10%

TBT (Total Blocking Time)

Value1,990 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

heineken.com

277 ms

www.heineken.com

127 ms

agegateway

576 ms

gateway.min.css

19 ms

VisitorIdentification.js

6 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 80% of them (12 requests) were addressed to the original Heineken.com, 13% (2 requests) were made to Google-analytics.com and 7% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (576 ms) belongs to the original domain Heineken.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 92.4 kB (42%)

Content Size

218.3 kB

After Optimization

125.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Heineken.com main page is 218.3 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. 25% of websites need less resources to load. Images take 89.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 16.7 kB

  • Original 23.4 kB
  • After minification 22.0 kB
  • After compression 6.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 16.7 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 89.4 kB
  • After minification 89.4 kB

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. Heineken images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 33.6 kB

  • Original 55.2 kB
  • After minification 54.7 kB
  • After compression 21.6 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 33.6 kB or 61% of the original size.

CSS Optimization

-84%

Potential reduce by 42.1 kB

  • Original 50.3 kB
  • After minification 50.3 kB
  • After compression 8.2 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.com needs all CSS files to be minified and compressed as it can save up to 42.1 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

10

After Optimization

7

  • Images
  • JavaScript
  • CSS

The browser has sent 10 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.

Network Requests Diagram

heineken.com

heineken.com

277 ms

www.heineken.com

www.heineken.com

127 ms

agegateway

agegateway

576 ms

gateway.min.css

gateway.min.css

19 ms

VisitorIdentification.js

VisitorIdentification.js

6 ms

gateway.min.js

gateway.min.js

11 ms

futura-condensed-bold.woff

futura-condensed-bold.woff

33 ms

futura-condensed.woff

futura-condensed.woff

40 ms

bg-agegateway.jpg

bg-agegateway.jpg

118 ms

logo.svg

logo.svg

332 ms

smiling-e-white.png

smiling-e-white.png

253 ms

gtm.js

gtm.js

61 ms

world.svg

world.svg

8 ms

analytics.js

analytics.js

17 ms

collect

collect

13 ms

Accessibility Review

heineken.com 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.com best practices score

92

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

Page has valid source maps

SEO Factors

heineken.com SEO score

83

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Heineken.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Heineken.com 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

heineken.com

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: