Tools & Wizards About Us
stemmle.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

stemmle.com

Augenheilkunde und Augenchirurgie in Zürich | augenarzt-praxis stemmle

Page Load Speed

4.4 sec in total

First Response

328 ms

Resources Loaded

3.9 sec

Page Rendered

187 ms

stemmle.com screenshot

About Website

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

Die Augenarztpraxis Stemmle in Zürich ist stets bestrebt, Sie sowohl fachlich als auch persönlich optimal zu betreuen. Wie können wir Ihnen helfen?

Visit stemmle.com

Key Findings

We analyzed Stemmle.com page load time and found that the first response time was 328 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

stemmle.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value220 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

stemmle.com

328 ms

1560 ms

style.css

100 ms

bazz-callback-widget-pro-public.css

195 ms

styles.css

288 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that all of those requests were addressed to Stemmle.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Stemmle.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.4 kB (13%)

Content Size

441.5 kB

After Optimization

385.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stemmle.com main page is 441.5 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. 35% of websites need less resources to load. Images take 203.5 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 53.4 kB

  • Original 66.3 kB
  • After minification 64.8 kB
  • After compression 12.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 53.4 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 552 B

  • Original 203.5 kB
  • After minification 202.9 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. Stemmle images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.2 kB

  • Original 135.2 kB
  • After minification 135.2 kB
  • After compression 134.0 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

-4%

Potential reduce by 1.3 kB

  • Original 36.5 kB
  • After minification 36.5 kB
  • After compression 35.2 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. Stemmle.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (54%)

Requests Now

24

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stemmle.com

stemmle.com

328 ms

1560 ms

style.css

style.css

100 ms

bazz-callback-widget-pro-public.css

bazz-callback-widget-pro-public.css

195 ms

styles.css

styles.css

288 ms

common.css

common.css

289 ms

style.css

style.css

291 ms

borlabs-cookie_1_en.css

borlabs-cookie_1_en.css

289 ms

jquery.min.js

jquery.min.js

387 ms

jquery-migrate.min.js

jquery-migrate.min.js

297 ms

borlabs-cookie-prioritize.min.js

borlabs-cookie-prioritize.min.js

385 ms

bazz-callback-widget-pro-public.js

bazz-callback-widget-pro-public.js

383 ms

index.js

index.js

416 ms

index.js

index.js

470 ms

frontend.js

frontend.js

470 ms

script.min.js

script.min.js

678 ms

borlabs-cookie.min.js

borlabs-cookie.min.js

483 ms

3629930866.png

3629930866.png

97 ms

logo.svg

logo.svg

100 ms

navigation-arrow.svg

navigation-arrow.svg

98 ms

augenarzt-augenchirurgie-stemmle-zuerich.jpg

augenarzt-augenchirurgie-stemmle-zuerich.jpg

477 ms

scroll-down-arrow-white.svg

scroll-down-arrow-white.svg

164 ms

pattern.svg

pattern.svg

193 ms

phone.svg

phone.svg

196 ms

close.svg

close.svg

197 ms

open-sans-v13-latin-italic.woff

open-sans-v13-latin-italic.woff

299 ms

open-sans-v13-latin-300italic.woff

open-sans-v13-latin-300italic.woff

287 ms

open-sans-v13-latin-600italic.woff

open-sans-v13-latin-600italic.woff

288 ms

open-sans-v13-latin-700italic.woff

open-sans-v13-latin-700italic.woff

288 ms

open-sans-v13-latin-regular.woff

open-sans-v13-latin-regular.woff

302 ms

open-sans-v13-latin-600.woff

open-sans-v13-latin-600.woff

329 ms

open-sans-v13-latin-700.woff

open-sans-v13-latin-700.woff

333 ms

scroll-down-arrow-white.svg

scroll-down-arrow-white.svg

98 ms

Accessibility Review

stemmle.com accessibility score

81

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

Form elements do not have associated labels

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

stemmle.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

stemmle.com SEO score

86

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 doesn't use 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 Stemmle.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 Stemmle.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

stemmle.com

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