Tools & Wizards About Us
schnurrblog.de screenshot

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

schnurrblog.de

Schnurrblog – Der Katzenblog

Page Load Speed

6.4 sec in total

First Response

399 ms

Resources Loaded

3.9 sec

Page Rendered

2.1 sec

schnurrblog.de screenshot

About Website

Click here to check amazing Schnurrblog content. Otherwise, check out these important facts you probably never knew about schnurrblog.de

Schnurrblog ist ein Katzenblog. Neben tollen Geschichten und Fotos aus dem Alltag der Katerjungs Shadow, Ernie, Monti und Finn berichten wir auch was alles für die Katz sein kann.

Visit schnurrblog.de

Key Findings

We analyzed Schnurrblog.de page load time and found that the first response time was 399 ms and then it took 6 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

schnurrblog.de performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

schnurrblog.de

399 ms

schnurrblog.catfelix.de

1204 ms

reset.css

383 ms

defaults.css

381 ms

style.css

377 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Schnurrblog.de, 91% (68 requests) were made to Schnurrblog.catfelix.de and 3% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Schnurrblog.catfelix.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 346.3 kB (19%)

Content Size

1.9 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Schnurrblog.de main page is 1.9 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. 40% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 74.7 kB

  • Original 93.4 kB
  • After minification 87.4 kB
  • After compression 18.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. 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 74.7 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 111.2 kB

  • Original 1.5 MB
  • After minification 1.4 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. Schnurrblog images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 124.1 kB

  • Original 175.4 kB
  • After minification 152.7 kB
  • After compression 51.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 124.1 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 36.3 kB

  • Original 43.4 kB
  • After minification 27.2 kB
  • After compression 7.1 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. Schnurrblog.de needs all CSS files to be minified and compressed as it can save up to 36.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (57%)

Requests Now

72

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

schnurrblog.de

schnurrblog.de

399 ms

schnurrblog.catfelix.de

schnurrblog.catfelix.de

1204 ms

reset.css

reset.css

383 ms

defaults.css

defaults.css

381 ms

style.css

style.css

377 ms

scrollto-top-css.php

scrollto-top-css.php

743 ms

wp-monalisa-default.css

wp-monalisa-default.css

368 ms

jquery.js

jquery.js

494 ms

jquery-migrate.min.js

jquery-migrate.min.js

475 ms

jquery.scrollTo-1.4.3-min.js

jquery.scrollTo-1.4.3-min.js

489 ms

scrollto-top.js.php

scrollto-top.js.php

1022 ms

wpml_script.js

wpml_script.js

482 ms

superfish.js

superfish.js

580 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

586 ms

jquery.cycle.all.js

jquery.cycle.all.js

601 ms

useronline.js

useronline.js

514 ms

style.css

style.css

589 ms

hoverIntent.min.js

hoverIntent.min.js

602 ms

wp-embed.min.js

wp-embed.min.js

612 ms

scripts.js

scripts.js

617 ms

css

css

71 ms

background-over.png

background-over.png

122 ms

background.png

background.png

241 ms

logoSB.png

logoSB.png

241 ms

1.jpg

1.jpg

421 ms

2.jpg

2.jpg

430 ms

3.jpg

3.jpg

323 ms

4.jpg

4.jpg

434 ms

5.jpg

5.jpg

530 ms

smug.gif

smug.gif

334 ms

icon_heart.gif

icon_heart.gif

433 ms

cfsb_e16_03_02.jpg

cfsb_e16_03_02.jpg

663 ms

wink.gif

wink.gif

527 ms

streeties.jpg

streeties.jpg

545 ms

smile.gif

smile.gif

546 ms

lol.gif

lol.gif

545 ms

cfsb_f16_03_01.jpg

cfsb_f16_03_01.jpg

775 ms

cfsb_fm16_03_01.jpg

cfsb_fm16_03_01.jpg

784 ms

cfsb_f16_02_03.jpg

cfsb_f16_02_03.jpg

788 ms

cool.gif

cool.gif

650 ms

shocked.gif

shocked.gif

648 ms

neutral.gif

neutral.gif

756 ms

cfsb_ef16_02_02.jpg

cfsb_ef16_02_02.jpg

762 ms

cfsb_f16_02_02.jpg

cfsb_f16_02_02.jpg

870 ms

question.gif

question.gif

901 ms

cfsb_f16_02_01.jpg

cfsb_f16_02_01.jpg

923 ms

grin.gif

grin.gif

906 ms

cfsb_m16_02_01.jpg

cfsb_m16_02_01.jpg

906 ms

whatever.gif

whatever.gif

902 ms

nervous.gif

nervous.gif

988 ms

cfsb_hue16_02_01.jpg

cfsb_hue16_02_01.jpg

1032 ms

cfsb_hue16_02_03.jpg

cfsb_hue16_02_03.jpg

1117 ms

cfsb_hue16_02_02.jpg

cfsb_hue16_02_02.jpg

1036 ms

cfsb_hue16_02_04.jpg

cfsb_hue16_02_04.jpg

1127 ms

cfsb_bw16_02_01.jpg

cfsb_bw16_02_01.jpg

1040 ms

confused.gif

confused.gif

1094 ms

sdk.js

sdk.js

109 ms

cfsb_e16_01-01.jpg

cfsb_e16_01-01.jpg

1228 ms

-g5pDUSRgvxvOl5u-a_WHw.woff

-g5pDUSRgvxvOl5u-a_WHw.woff

115 ms

twitter.png

twitter.png

1018 ms

facebook.png

facebook.png

911 ms

80 ms

rss.png

rss.png

932 ms

xd_arbiter.php

xd_arbiter.php

78 ms

xd_arbiter.php

xd_arbiter.php

133 ms

email.png

email.png

907 ms

search.png

search.png

902 ms

main-bg.png

main-bg.png

836 ms

featured-next.png

featured-next.png

830 ms

featured-prev.png

featured-prev.png

877 ms

date.png

date.png

901 ms

category.png

category.png

815 ms

comments.png

comments.png

830 ms

widget-list.png

widget-list.png

817 ms

dwieeb_arrow_dark.png

dwieeb_arrow_dark.png

827 ms

Accessibility Review

schnurrblog.de accessibility score

84

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

button, link, and menuitem elements do not have accessible names.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

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

SEO Factors

schnurrblog.de SEO score

93

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

schnurrblog.de

Open Graph data is detected on the main page of Schnurrblog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: