Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

weyersberg.ws

aw : Portfolio Of Angela Weyersberg

Page Load Speed

1.1 sec in total

First Response

160 ms

Resources Loaded

744 ms

Page Rendered

220 ms

weyersberg.ws screenshot

About Website

Welcome to weyersberg.ws homepage info - get ready to check Weyersberg best content right away, or after learning these important things about weyersberg.ws

Visit weyersberg.ws

Key Findings

We analyzed Weyersberg.ws page load time and found that the first response time was 160 ms and then it took 964 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

weyersberg.ws performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.097

90/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

weyersberg.ws

160 ms

styles.css

97 ms

swfobject.js

117 ms

mt.js

94 ms

nav-bg.gif

13 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 148.0 kB (20%)

Content Size

739.4 kB

After Optimization

591.3 kB

In fact, the total size of Weyersberg.ws main page is 739.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. Images take 680.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 8.6 kB

  • Original 10.8 kB
  • After minification 9.7 kB
  • After compression 2.3 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 1.2 kB, which is 11% 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 8.6 kB or 79% of the original size.

Image Optimization

-15%

Potential reduce by 103.3 kB

  • Original 680.7 kB
  • After minification 577.4 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. Obviously, Weyersberg needs image optimization as it can save up to 103.3 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 21.5 kB

  • Original 29.2 kB
  • After minification 22.2 kB
  • After compression 7.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 21.5 kB or 74% of the original size.

CSS Optimization

-78%

Potential reduce by 14.7 kB

  • Original 18.7 kB
  • After minification 16.6 kB
  • After compression 4.0 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. Weyersberg.ws needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 78% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

22

After Optimization

22

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

Accessibility Review

weyersberg.ws accessibility score

66

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

weyersberg.ws best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

weyersberg.ws SEO score

69

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weyersberg.ws 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 Weyersberg.ws 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 Weyersberg. 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: