Access atlantisrejser.com. Oplev Egypten med Atlantis

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value20.3 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value3,470 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.266

46/100

15%

TTI (Time to Interactive)

Value22.0 s

1/100

10%

atlantisrejser.com

84 ms

atlantisrejser.com

152 ms

atlantis

695 ms

8572.b5a75d7c.css

19 ms

shared-9a4fcf09.b93f9feb.css

1926 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Atlantisrejser.com, 94% (46 requests) were made to Sunweb.dk and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Sunweb.dk.

Content Size

1.8 MB

After Optimization

1.0 MB

In fact, the total size of Atlantisrejser.com main page is 1.8 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. 30% of websites need less resources to load. Javascripts take 862.6 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 396.1 kB

Original 446.8 kB
After minification 383.6 kB
After compression 50.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. This page needs HTML code to be minified as it can gain 63.2 kB, which is 14% 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 396.1 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 542 B

Original 86.2 kB
After minification 85.6 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. Atlantis Rejser images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 276.0 kB

Original 862.6 kB
After minification 862.6 kB
After compression 586.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 276.0 kB or 32% of the original size.

CSS Optimization

-30%

Potential reduce by 125.2 kB

Original 421.5 kB
After minification 421.5 kB
After compression 296.4 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. Atlantisrejser.com needs all CSS files to be minified and compressed as it can save up to 125.2 kB or 30% of the original size.

Requests Now

After Optimization

The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Atlantis Rejser. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts 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

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

[role]s are not contained by their required parent element

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

Form elements do not have associated labels

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

[id] attributes on active, focusable elements are not unique

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

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

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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

DA
Language Claimed

DA
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Atlantisrejser.com 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 Atlantisrejser.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

Open Graph description is not detected on the main page of Atlantis Rejser. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

Oplev Egypten med Atlantis | Sunweb – Gør eventyret dit

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

atlantisrejser.com

atlantisrejser.com

atlantis

8572.b5a75d7c.css

shared-9a4fcf09.b93f9feb.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

{{url}}

Accessibility Review

Accessibility Issues

Best Practices

Areas of Improvement

SEO Factors

Search Engine Optimization Advices

Language and Encoding

Language Detected

Language Claimed

Encoding

Social Sharing Optimization

{{og_title}}