Tools & Wizards About Us
franziskauhlig.de screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

franziskauhlig.de

www.franziskauhlig.de

Page Load Speed

2.7 sec in total

First Response

412 ms

Resources Loaded

1.8 sec

Page Rendered

514 ms

franziskauhlig.de screenshot

About Website

Visit franziskauhlig.de now to see the best up-to-date Franziskauhlig content and also check out these interesting facts you probably never knew about franziskauhlig.de

Visit franziskauhlig.de

Key Findings

We analyzed Franziskauhlig.de page load time and found that the first response time was 412 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

franziskauhlig.de performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.387

27/100

15%

TTI (Time to Interactive)

Value9.7 s

29/100

10%

Network Requests Diagram

franziskauhlig.de

412 ms

www.franziskauhlig.de

645 ms

pre_tumblelog.js

12 ms

reset.css

36 ms

styles.css

37 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Franziskauhlig.de, 18% (11 requests) were made to Static.tumblr.com and 18% (11 requests) were made to 40.media.tumblr.com. The less responsive or slowest element that took the longest time to load (645 ms) belongs to the original domain Franziskauhlig.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 569.4 kB (26%)

Content Size

2.2 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 110.5 kB

  • Original 134.5 kB
  • After minification 111.5 kB
  • After compression 24.0 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 23.0 kB, which is 17% 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 110.5 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 44.2 kB

  • Original 1.4 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. Franziskauhlig images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 394.9 kB

  • Original 598.6 kB
  • After minification 586.4 kB
  • After compression 203.7 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 394.9 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 19.8 kB

  • Original 24.2 kB
  • After minification 19.2 kB
  • After compression 4.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. Franziskauhlig.de needs all CSS files to be minified and compressed as it can save up to 19.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (33%)

Requests Now

58

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

franziskauhlig.de

franziskauhlig.de

412 ms

www.franziskauhlig.de

www.franziskauhlig.de

645 ms

pre_tumblelog.js

pre_tumblelog.js

12 ms

reset.css

reset.css

36 ms

styles.css

styles.css

37 ms

css

css

45 ms

jquery.min.js

jquery.min.js

61 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

12 ms

jquery.isotope.min.js

jquery.isotope.min.js

32 ms

batchimageload.js

batchimageload.js

32 ms

jquery.scrollto-min.js

jquery.scrollto-min.js

32 ms

jquery.client.js

jquery.client.js

32 ms

infinite-scroll-tags.js

infinite-scroll-tags.js

36 ms

functions-tags-infinite.min.js

functions-tags-infinite.min.js

111 ms

pinit.js

pinit.js

34 ms

index.js

index.js

36 ms

JpjDi.gif

JpjDi.gif

121 ms

tumblr_o2yuguCZa61rnj1leo1_400.jpg

tumblr_o2yuguCZa61rnj1leo1_400.jpg

207 ms

tumblr_o2yuev1taA1rnj1leo1_400.jpg

tumblr_o2yuev1taA1rnj1leo1_400.jpg

228 ms

tumblr_o2yu4gvKkf1rnj1leo1_400.jpg

tumblr_o2yu4gvKkf1rnj1leo1_400.jpg

117 ms

tumblr_o2yucvNqNX1rnj1leo1_400.jpg

tumblr_o2yucvNqNX1rnj1leo1_400.jpg

366 ms

tumblr_o2yu6gmpgt1rnj1leo1_400.jpg

tumblr_o2yu6gmpgt1rnj1leo1_400.jpg

275 ms

tumblr_o2yalqHdk01rnj1leo1_400.jpg

tumblr_o2yalqHdk01rnj1leo1_400.jpg

497 ms

tumblr_o2yalqHdk01rnj1leo4_400.jpg

tumblr_o2yalqHdk01rnj1leo4_400.jpg

439 ms

tumblr_o2yalqHdk01rnj1leo5_400.jpg

tumblr_o2yalqHdk01rnj1leo5_400.jpg

438 ms

tumblr_o2y6k7JETM1rnj1leo2_400.png

tumblr_o2y6k7JETM1rnj1leo2_400.png

371 ms

tumblr_o2y65wLzDC1rnj1leo1_400.jpg

tumblr_o2y65wLzDC1rnj1leo1_400.jpg

353 ms

tumblr_o2y5kbywas1rnj1leo1_r1_400.jpg

tumblr_o2y5kbywas1rnj1leo1_r1_400.jpg

451 ms

tumblr_o2y5hn9kAH1rnj1leo1_400.jpg

tumblr_o2y5hn9kAH1rnj1leo1_400.jpg

578 ms

tumblr_n30ixaJOot1rnj1leo1_400.jpg

tumblr_n30ixaJOot1rnj1leo1_400.jpg

452 ms

tumblr_o2yalqHdk01rnj1leo3_400.jpg

tumblr_o2yalqHdk01rnj1leo3_400.jpg

255 ms

tumblr_o2y6crHnxN1rnj1leo1_400.jpg

tumblr_o2y6crHnxN1rnj1leo1_400.jpg

352 ms

tumblr_n30irrPmoP1rnj1leo1_400.jpg

tumblr_n30irrPmoP1rnj1leo1_400.jpg

182 ms

tumblr_static_header_img_3.jpg

tumblr_static_header_img_3.jpg

113 ms

arrow-sprite.png

arrow-sprite.png

97 ms

sprite.png

sprite.png

97 ms

tumblr_o2y9xrgsYT1rnj1leo1_400.jpg

tumblr_o2y9xrgsYT1rnj1leo1_400.jpg

98 ms

tumblr_o2y6k7JETM1rnj1leo3_400.jpg

tumblr_o2y6k7JETM1rnj1leo3_400.jpg

97 ms

tumblr_o2y6k7JETM1rnj1leo1_400.png

tumblr_o2y6k7JETM1rnj1leo1_400.png

211 ms

tumblr_o2y6crHnxN1rnj1leo2_400.jpg

tumblr_o2y6crHnxN1rnj1leo2_400.jpg

201 ms

tumblr_n30jswnQPR1rnj1leo1_400.jpg

tumblr_n30jswnQPR1rnj1leo1_400.jpg

349 ms

tumblr_n30jswnQPR1rnj1leo2_400.jpg

tumblr_n30jswnQPR1rnj1leo2_400.jpg

97 ms

tumblr_n30jswnQPR1rnj1leo3_400.jpg

tumblr_n30jswnQPR1rnj1leo3_400.jpg

98 ms

plusone.js

plusone.js

198 ms

impixu

impixu

209 ms

impixu

impixu

123 ms

analytics.html

analytics.html

121 ms

pinit_main.js

pinit_main.js

86 ms

login_check.html

login_check.html

27 ms

avatar_dc200d8f1157_40.png

avatar_dc200d8f1157_40.png

129 ms

iframe_logo.png

iframe_logo.png

57 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

6 ms

rapid-3.36.js

rapid-3.36.js

46 ms

rapidworker-1.2.js

rapidworker-1.2.js

44 ms

ga.js

ga.js

36 ms

analytics.js

analytics.js

63 ms

cs.js

cs.js

79 ms

yql

yql

163 ms

__utm.gif

__utm.gif

23 ms

cedexis.radar.js

cedexis.radar.js

4 ms

Accessibility Review

franziskauhlig.de accessibility score

92

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

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

SEO Factors

franziskauhlig.de SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

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 Franziskauhlig.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 Franziskauhlig.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

franziskauhlig.de

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