Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

jollydays.com

Deine Nr. 1 für Erlebnisse | Jollydays

Page Load Speed

10.5 sec in total

First Response

265 ms

Resources Loaded

9.6 sec

Page Rendered

657 ms

jollydays.com screenshot

About Website

Click here to check amazing Jollydays content for Austria. Otherwise, check out these important facts you probably never knew about jollydays.com

Ausgefallene Geschenke und Geschenkideen für jeden Anlass findest du bei jollydays.at - Österreichs größtem Erlebnisportal. Hier ist für jeden das Richtige dabei

Visit jollydays.com

Key Findings

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

Performance Metrics

jollydays.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

jollydays.com

265 ms

www.jollydays.at

726 ms

351 ms

703 ms

css

47 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Jollydays.com, 45% (51 requests) were made to Jollydays.at and 6% (7 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Jollydays.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 854.3 kB (49%)

Content Size

1.8 MB

After Optimization

901.6 kB

In fact, the total size of Jollydays.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. 55% of websites need less resources to load. Javascripts take 793.5 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 195.7 kB

  • Original 223.8 kB
  • After minification 191.5 kB
  • After compression 28.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. This page needs HTML code to be minified as it can gain 32.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 195.7 kB or 87% of the original size.

Image Optimization

-11%

Potential reduce by 82.8 kB

  • Original 738.7 kB
  • After minification 655.9 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. Obviously, Jollydays needs image optimization as it can save up to 82.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 575.8 kB

  • Original 793.5 kB
  • After minification 569.2 kB
  • After compression 217.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 575.8 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (39%)

Requests Now

102

After Optimization

62

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

Accessibility Review

jollydays.com accessibility score

75

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

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

jollydays.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

jollydays.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    DE

  • Language Claimed

    DE

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jollydays.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Jollydays.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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