Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

webdriver.io

WebdriverIO · Next-gen browser and mobile automation test framework for Node.js | WebdriverIO

Page Load Speed

2.5 sec in total

First Response

306 ms

Resources Loaded

1.5 sec

Page Rendered

619 ms

webdriver.io screenshot

About Website

Welcome to webdriver.io homepage info - get ready to check Webdriver best content for United States right away, or after learning these important things about webdriver.io

Next-gen browser and mobile automation test framework for Node.js

Visit webdriver.io

Key Findings

We analyzed Webdriver.io page load time and found that the first response time was 306 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

webdriver.io performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

webdriver.io

306 ms

screen.css

231 ms

68747470733a2f2f636f766572616c6c732e696f2f7265706f732f63616d6d652f7765626472697665726a732f62616467652e706e673f6272616e63683d6d617374657226

215 ms

github-btn.html

96 ms

profil.png

195 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 25% of them (14 requests) were addressed to the original Webdriver.io, 13% (7 requests) were made to Apis.google.com and 9% (5 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (973 ms) belongs to the original domain Webdriver.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 415.1 kB (50%)

Content Size

825.3 kB

After Optimization

410.2 kB

In fact, the total size of Webdriver.io main page is 825.3 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. 50% of websites need less resources to load. Images take 704.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 20.4 kB

  • Original 28.4 kB
  • After minification 27.3 kB
  • After compression 8.0 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 20.4 kB or 72% of the original size.

Image Optimization

-48%

Potential reduce by 335.8 kB

  • Original 704.0 kB
  • After minification 368.2 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, Webdriver needs image optimization as it can save up to 335.8 kB or 48% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 37.7 kB

  • Original 62.7 kB
  • After minification 62.7 kB
  • After compression 25.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 37.7 kB or 60% of the original size.

CSS Optimization

-70%

Potential reduce by 21.2 kB

  • Original 30.3 kB
  • After minification 30.2 kB
  • After compression 9.1 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. Webdriver.io needs all CSS files to be minified and compressed as it can save up to 21.2 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (33%)

Requests Now

49

After Optimization

33

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

Accessibility Review

webdriver.io accessibility score

91

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

webdriver.io 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

webdriver.io SEO score

97

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 Webdriver.io 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 Webdriver.io 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 Webdriver. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: