Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

tuborg.ua

Tuborg - Tuborg Beer | Explore the world through musical journeys

Page Load Speed

2.2 sec in total

First Response

80 ms

Resources Loaded

1.8 sec

Page Rendered

345 ms

tuborg.ua screenshot

About Website

Click here to check amazing Tuborg content for Ukraine. Otherwise, check out these important facts you probably never knew about tuborg.ua

Join our discovery journey with a Tuborg beer in your hand and great music in your ears. Always stay open for more

Visit tuborg.ua

Key Findings

We analyzed Tuborg.ua page load time and found that the first response time was 80 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

tuborg.ua performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value1,460 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.714

7/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

tuborg.ua

80 ms

tuborg.ua

168 ms

400 ms

300 ms

cbgCompPack.js

40 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 18% of them (3 requests) were addressed to the original Tuborg.ua, 71% (12 requests) were made to Tuborg.com and 6% (1 request) were made to Compliance-pack.carlsberggroup.com. The less responsive or slowest element that took the longest time to load (528 ms) relates to the external source Tuborg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 86.2 kB (31%)

Content Size

280.0 kB

After Optimization

193.9 kB

In fact, the total size of Tuborg.ua main page is 280.0 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. 20% of websites need less resources to load. Javascripts take 206.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 56.0 kB

  • Original 71.8 kB
  • After minification 63.9 kB
  • After compression 15.8 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. This page needs HTML code to be minified as it can gain 7.9 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 56.0 kB or 78% of the original size.

JavaScript Optimization

-15%

Potential reduce by 30.1 kB

  • Original 206.5 kB
  • After minification 206.5 kB
  • After compression 176.4 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 30.1 kB or 15% of the original size.

CSS Optimization

-7%

Potential reduce by 130 B

  • Original 1.7 kB
  • After minification 1.7 kB
  • After compression 1.6 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. Tuborg.ua has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 5 (71%)

Requests Now

7

After Optimization

2

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

Accessibility Review

tuborg.ua accessibility score

91

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tuborg.ua 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

tuborg.ua SEO score

96

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 Tuborg.ua 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 Tuborg.ua 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 PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: