Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

Page Load Speed

927 ms in total

First Response

98 ms

Resources Loaded

739 ms

Page Rendered

90 ms

schmalensee.com screenshot

About Website

Welcome to schmalensee.com homepage info - get ready to check Schmalensee best content right away, or after learning these important things about schmalensee.com

Visit schmalensee.com

Key Findings

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

Performance Metrics

schmalensee.com performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

schmalensee.com

98 ms

style.min.css

311 ms

style.css

88 ms

email-decode.min.js

19 ms

diane3.png

354 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 88% of them (7 requests) were addressed to the original Schmalensee.com, 13% (1 request) were made to . The less responsive or slowest element that took the longest time to load (354 ms) belongs to the original domain Schmalensee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 12.6 kB (2%)

Content Size

552.5 kB

After Optimization

539.8 kB

In fact, the total size of Schmalensee.com main page is 552.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 535.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 12.6 kB

  • Original 16.5 kB
  • After minification 16.5 kB
  • After compression 3.9 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 12.6 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-3%

Potential reduce by 17 B

  • Original 655 B
  • After minification 655 B
  • After compression 638 B

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.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Schmalensee. According to our analytics all requests are already optimized.

Accessibility Review

schmalensee.com accessibility score

94

Accessibility Issues

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

Document doesn't have a <title> element

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

schmalensee.com SEO score

71

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

Document doesn't have a <title> element

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

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

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