Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

alive.dk

Full-service eventbureau - Vi gør dit event til en unik oplevelse | ALIVE

Page Load Speed

7.8 sec in total

First Response

856 ms

Resources Loaded

6 sec

Page Rendered

968 ms

About Website

Visit alive.dk now to see the best up-to-date ALIVE content and also check out these interesting facts you probably never knew about alive.dk

Vi har over 20 års erfaring som eventbureau og planlægger dit event effektivt & professionelt. ALIVE er din eventarrangør fra start til slut.

Visit alive.dk

Key Findings

We analyzed Alive.dk page load time and found that the first response time was 856 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

alive.dk performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value1,750 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

alive.dk

856 ms

header_model.css

235 ms

language_swift.css

289 ms

swiper-bundle.min.css

297 ms

model_swiper.css

296 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 84% of them (71 requests) were addressed to the original Alive.dk, 11% (9 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Alive.dk.

Page Optimization Overview & Recommendations

Page size can be reduced by 249.7 kB (7%)

Content Size

3.6 MB

After Optimization

3.3 MB

In fact, the total size of Alive.dk main page is 3.6 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. 60% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 77.7 kB

  • Original 94.9 kB
  • After minification 92.2 kB
  • After compression 17.3 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 77.7 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 82.3 kB

  • Original 3.1 MB
  • After minification 3.0 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. ALIVE images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 87.5 kB

  • Original 347.1 kB
  • After minification 347.1 kB
  • After compression 259.5 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.5 kB or 25% of the original size.

CSS Optimization

-3%

Potential reduce by 2.2 kB

  • Original 68.2 kB
  • After minification 68.2 kB
  • After compression 66.0 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. Alive.dk has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 46 (61%)

Requests Now

75

After Optimization

29

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

Accessibility Review

alive.dk accessibility score

95

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.

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

alive.dk 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

alive.dk SEO score

100

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

Language and Encoding

  • Language Detected

    DA

  • Language Claimed

    DA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alive.dk can be misinterpreted by Google and other search engines. Our service has detected that Danish is used on the page, and it matches the claimed language. Our system also found out that Alive.dk 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 ALIVE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: