Report Summary

  • 97

    Performance

    Renders faster than
    94% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

john-uebersax.com

John Uebersax Home Page

Page Load Speed

924 ms in total

First Response

152 ms

Resources Loaded

668 ms

Page Rendered

104 ms

john-uebersax.com screenshot

About Website

Welcome to john-uebersax.com homepage info - get ready to check John Uebersax best content for United States right away, or after learning these important things about john-uebersax.com

Home Page of John Uebersax

Visit john-uebersax.com

Key Findings

We analyzed John-uebersax.com page load time and found that the first response time was 152 ms and then it took 772 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

john-uebersax.com performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.1 s

100/100

25%

SI (Speed Index)

Value1.1 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.134

80/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

Network Requests Diagram

john-uebersax.com

152 ms

john-uebersax.com

280 ms

peaks.jpg

179 ms

dropbox-icon.png

186 ms

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

Page Optimization Overview & Recommendations

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

Content Size

71.9 kB

After Optimization

62.4 kB

In fact, the total size of John-uebersax.com main page is 71.9 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 63.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 7.1 kB

  • Original 8.5 kB
  • After minification 3.4 kB
  • After compression 1.5 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 5.1 kB, which is 60% 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 7.1 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 2.4 kB

  • Original 63.3 kB
  • After minification 60.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. John Uebersax images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

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

Accessibility Review

john-uebersax.com accessibility score

56

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

john-uebersax.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

john-uebersax.com SEO score

67

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise John-uebersax.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that John-uebersax.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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