Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

hisky.de

hisky.de – das etwas andere Laufblog – Laufen macht kreativ haben Sie gesagt!?

Page Load Speed

5.9 sec in total

First Response

295 ms

Resources Loaded

3.9 sec

Page Rendered

1.7 sec

hisky.de screenshot

About Website

Click here to check amazing Hisky content for Germany. Otherwise, check out these important facts you probably never knew about hisky.de

Webblog aus Kitzingen. Kurioses, lustiges und was man sonst im Web so findet. Weinfestbilder und Partybilder von 2002 bis heute!

Visit hisky.de

Key Findings

We analyzed Hisky.de page load time and found that the first response time was 295 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

hisky.de performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value2,260 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

hisky.de

295 ms

1086 ms

wp-emoji-release.min.js

277 ms

styles.css

273 ms

nivo-lightbox.css

185 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 88% of them (91 requests) were addressed to the original Hisky.de, 3% (3 requests) were made to S.gravatar.com and 3% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Hisky.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 641.9 kB (52%)

Content Size

1.2 MB

After Optimization

581.9 kB

In fact, the total size of Hisky.de main page is 1.2 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 434.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 91.4 kB

  • Original 112.9 kB
  • After minification 107.7 kB
  • After compression 21.5 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 91.4 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 13.4 kB

  • Original 390.6 kB
  • After minification 377.2 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. Hisky images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 295.3 kB

  • Original 434.6 kB
  • After minification 396.5 kB
  • After compression 139.3 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 295.3 kB or 68% of the original size.

CSS Optimization

-85%

Potential reduce by 241.8 kB

  • Original 285.7 kB
  • After minification 232.4 kB
  • After compression 43.9 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. Hisky.de needs all CSS files to be minified and compressed as it can save up to 241.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (47%)

Requests Now

91

After Optimization

48

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

Accessibility Review

hisky.de accessibility score

83

Accessibility Issues

ARIA

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.

Impact

Issue

High

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

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

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

hisky.de 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hisky.de SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    EN

  • Encoding

    UTF-8

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