Tools & Wizards About Us
janfsauer.com screenshot

Report Summary

  • 85

    Performance

    Renders faster than
    88% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

janfsauer.com

Adventures in global business

Page Load Speed

2.4 sec in total

First Response

468 ms

Resources Loaded

1.4 sec

Page Rendered

538 ms

janfsauer.com screenshot

About Website

Visit janfsauer.com now to see the best up-to-date Janfsauer content and also check out these interesting facts you probably never knew about janfsauer.com

Adventures in global business building - by Jan Sauer. I write about innovation, strategy, culture, and technology.

Visit janfsauer.com

Key Findings

We analyzed Janfsauer.com page load time and found that the first response time was 468 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

janfsauer.com performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

janfsauer.com

468 ms

style.min.css

364 ms

mediaelementplayer-legacy.min.css

453 ms

wp-mediaelement.min.css

451 ms

all.min.css

501 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 43% of them (16 requests) were addressed to the original Janfsauer.com, 41% (15 requests) were made to C0.wp.com and 5% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source I0.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.9 kB (24%)

Content Size

240.4 kB

After Optimization

183.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Janfsauer.com main page is 240.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 78.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 56.2 kB

  • Original 72.6 kB
  • After minification 69.8 kB
  • After compression 16.4 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 56.2 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 57.5 kB
  • After minification 57.5 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. Janfsauer images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 361 B

  • Original 78.3 kB
  • After minification 78.3 kB
  • After compression 77.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 367 B

  • Original 32.1 kB
  • After minification 32.1 kB
  • After compression 31.7 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. Janfsauer.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (86%)

Requests Now

21

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

janfsauer.com

janfsauer.com

468 ms

style.min.css

style.min.css

364 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

453 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

451 ms

all.min.css

all.min.css

501 ms

bootstrap.min.css

bootstrap.min.css

500 ms

front.css

front.css

501 ms

css

css

244 ms

all.min.css

all.min.css

500 ms

style.css

style.css

498 ms

jetpack.css

jetpack.css

471 ms

css

css

463 ms

drew-hays-tGYrlchfObE-unsplash.63a35ac9aece4da698a754f0316068c4.jpg

drew-hays-tGYrlchfObE-unsplash.63a35ac9aece4da698a754f0316068c4.jpg

1030 ms

jquery.min.js

jquery.min.js

335 ms

jquery-migrate.min.js

jquery-migrate.min.js

599 ms

mo_openid_jquery.cookie.min.js

mo_openid_jquery.cookie.min.js

391 ms

mo-openid-social_login.js

mo-openid-social_login.js

391 ms

frontend-gtag.min.js

frontend-gtag.min.js

427 ms

popper.min.js

popper.min.js

427 ms

bootstrap.min.js

bootstrap.min.js

427 ms

front.js

front.js

427 ms

tiled-gallery.min.js

tiled-gallery.min.js

602 ms

infinity.min.js

infinity.min.js

603 ms

photon.min.js

photon.min.js

604 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

626 ms

wp-polyfill.min.js

wp-polyfill.min.js

628 ms

hooks.min.js

hooks.min.js

676 ms

i18n.min.js

i18n.min.js

677 ms

jquery.form.min.js

jquery.form.min.js

691 ms

jetpack-carousel.min.js

jetpack-carousel.min.js

693 ms

production.min.js

production.min.js

424 ms

intersection-observer.js

intersection-observer.js

423 ms

lazy-images.js

lazy-images.js

423 ms

e-202240.js

e-202240.js

711 ms

js

js

605 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

168 ms

analytics.js

analytics.js

38 ms

Accessibility Review

janfsauer.com accessibility score

100

Accessibility Issues

Best Practices

janfsauer.com 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

SEO Factors

janfsauer.com SEO score

91

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Janfsauer.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Janfsauer.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

janfsauer.com

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