Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 49

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

wyndigo.com

Wyndigo Home 3.0

Page Load Speed

2.9 sec in total

First Response

305 ms

Resources Loaded

2.4 sec

Page Rendered

191 ms

About Website

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

A Wyndigo é uma marca da Powering Yourself, empresa criada em 2010 por dois jovens portugueses e que se dedica ao desenvolvimento de equipamentos de microgeração de energia e de soluções de engenharia...

Visit wyndigo.com

Key Findings

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

Performance Metrics

wyndigo.com performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.3 s

100/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

wyndigo.com

305 ms

css

34 ms

css

47 ms

style.css

201 ms

skeleton.css

185 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 73% of them (27 requests) were addressed to the original Wyndigo.com, 19% (7 requests) were made to Fonts.gstatic.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.7 sec) belongs to the original domain Wyndigo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 236.8 kB (16%)

Content Size

1.4 MB

After Optimization

1.2 MB

In fact, the total size of Wyndigo.com main page is 1.4 MB. 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 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 7.3 kB

  • Original 9.8 kB
  • After minification 7.5 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 2.2 kB, which is 23% 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.3 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 12.8 kB

  • Original 1.2 MB
  • After minification 1.1 MB

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. Wyndigo images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 96.9 kB

  • Original 129.0 kB
  • After minification 100.3 kB
  • After compression 32.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 96.9 kB or 75% of the original size.

CSS Optimization

-87%

Potential reduce by 119.7 kB

  • Original 138.1 kB
  • After minification 89.6 kB
  • After compression 18.3 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. Wyndigo.com needs all CSS files to be minified and compressed as it can save up to 119.7 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

27

After Optimization

9

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

Accessibility Review

wyndigo.com accessibility score

49

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

Image elements do not have [alt] attributes

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

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

wyndigo.com SEO score

92

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

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wyndigo.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Wyndigo.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 data is detected on the main page of Wyndigo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: