Tools & Wizards About Us
qwil.io screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

qwil.io

Qwil - Everything you need to communicate with your clients

Page Load Speed

1.7 sec in total

First Response

9 ms

Resources Loaded

1.1 sec

Page Rendered

633 ms

qwil.io screenshot

About Website

Click here to check amazing Qwil content. Otherwise, check out these important facts you probably never knew about qwil.io

Chat, video, signature, document management made easy and secure. The all-in one professional platform for client interactions and collaboration.

Visit qwil.io

Key Findings

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

Performance Metrics

qwil.io performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value1,710 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

Network Requests Diagram

qwil.io

9 ms

qwil.io

33 ms

js

105 ms

hotjar-3731045.js

308 ms

font-awesome.min.css

90 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 22% of them (15 requests) were addressed to the original Qwil.io, 41% (28 requests) were made to Demo.arcade.software and 9% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (588 ms) relates to the external source Cdn.arcade.software.

Page Optimization Overview & Recommendations

Page size can be reduced by 267.6 kB (15%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qwil.io main page is 1.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 60.5 kB

  • Original 73.2 kB
  • After minification 60.3 kB
  • After compression 12.8 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 12.9 kB, which is 18% 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 60.5 kB or 83% of the original size.

Image Optimization

-12%

Potential reduce by 203.2 kB

  • Original 1.6 MB
  • After minification 1.4 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. Obviously, Qwil needs image optimization as it can save up to 203.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-5%

Potential reduce by 871 B

  • Original 16.8 kB
  • After minification 16.7 kB
  • After compression 16.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

-11%

Potential reduce by 3.0 kB

  • Original 27.5 kB
  • After minification 27.5 kB
  • After compression 24.4 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. Qwil.io needs all CSS files to be minified and compressed as it can save up to 3.0 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (72%)

Requests Now

60

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qwil.io

qwil.io

9 ms

qwil.io

qwil.io

33 ms

js

js

105 ms

hotjar-3731045.js

hotjar-3731045.js

308 ms

font-awesome.min.css

font-awesome.min.css

90 ms

aquamarine8.css

aquamarine8.css

13 ms

cookiealert.css

cookiealert.css

74 ms

animate-in.js

animate-in.js

50 ms

jquery-3.3.1.slim.min.js

jquery-3.3.1.slim.min.js

74 ms

popper.min.js

popper.min.js

101 ms

bootstrap.min.js

bootstrap.min.js

116 ms

smooth-scroll.js

smooth-scroll.js

64 ms

cookiealert.js

cookiealert.js

77 ms

snippet.js

snippet.js

117 ms

css

css

81 ms

css

css

105 ms

css

css

106 ms

css

css

106 ms

css

css

107 ms

fbevents.js

fbevents.js

191 ms

Q42ztIqFT3YA1kWLNfro

Q42ztIqFT3YA1kWLNfro

306 ms

logo4.jpg

logo4.jpg

181 ms

insight.min.js

insight.min.js

116 ms

k1.jpg

k1.jpg

194 ms

k2.jpg

k2.jpg

210 ms

k3.jpg

k3.jpg

193 ms

k4.jpg

k4.jpg

247 ms

globalblock.png

globalblock.png

211 ms

SJP-logo-1.png

SJP-logo-1.png

218 ms

Schroders%20NEW.png

Schroders%20NEW.png

339 ms

saranac.jpg

saranac.jpg

349 ms

logo3.png

logo3.png

355 ms

lftracker_v1_kn9Eq4RzNYK4RlvP.js

lftracker_v1_kn9Eq4RzNYK4RlvP.js

95 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

70 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

90 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

96 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

51 ms

insight_tag_errors.gif

insight_tag_errors.gif

64 ms

71ca9c13eb6a6b4b.css

71ca9c13eb6a6b4b.css

11 ms

e5a51cc845eaa471.css

e5a51cc845eaa471.css

57 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

37 ms

864-b4c7b98ab03e029f.js

864-b4c7b98ab03e029f.js

29 ms

8573-7926a02d67ab79b2.js

8573-7926a02d67ab79b2.js

30 ms

9993-5c0b78e50ee9bb98.js

9993-5c0b78e50ee9bb98.js

30 ms

4238.60abd40211ac40d1.js

4238.60abd40211ac40d1.js

28 ms

354-770d2be55c53acfb.js

354-770d2be55c53acfb.js

54 ms

1662.c516794905fab695.js

1662.c516794905fab695.js

53 ms

3770.89bad80ad50ecd76.js

3770.89bad80ad50ecd76.js

33 ms

webpack-1a97ffa436dcc717.js

webpack-1a97ffa436dcc717.js

59 ms

framework-71aa685ca3b767ed.js

framework-71aa685ca3b767ed.js

54 ms

main-d810f0b83e7cbe4c.js

main-d810f0b83e7cbe4c.js

58 ms

_app-9e3e1d86a67a6e4a.js

_app-9e3e1d86a67a6e4a.js

72 ms

8eec4907-c9e54c3f91dcad26.js

8eec4907-c9e54c3f91dcad26.js

65 ms

3743-fbb8aa6b722ecd55.js

3743-fbb8aa6b722ecd55.js

67 ms

8421-c1fb0aec42ec2731.js

8421-c1fb0aec42ec2731.js

65 ms

8858-cdb25ff0480a9944.js

8858-cdb25ff0480a9944.js

77 ms

3205-8de1932fb02e2855.js

3205-8de1932fb02e2855.js

67 ms

6233-d0de8afeb4598c8d.js

6233-d0de8afeb4598c8d.js

74 ms

9123-ca9d36310a31e70d.js

9123-ca9d36310a31e70d.js

66 ms

3641-89db6308e6f76eed.js

3641-89db6308e6f76eed.js

75 ms

5542-37cdf0726a45c25e.js

5542-37cdf0726a45c25e.js

78 ms

5513-1c263704de449fe8.js

5513-1c263704de449fe8.js

73 ms

%5Bpid%5D-1fd266968f5fe95f.js

%5Bpid%5D-1fd266968f5fe95f.js

79 ms

_buildManifest.js

_buildManifest.js

78 ms

_ssgManifest.js

_ssgManifest.js

78 ms

css2

css2

19 ms

bg-01.png

bg-01.png

454 ms

40064b4d-d8ac-41b9-a750-b0bcabb4af8d.png

40064b4d-d8ac-41b9-a750-b0bcabb4af8d.png

588 ms

tr.lfeeder.com

tr.lfeeder.com

89 ms

Accessibility Review

qwil.io accessibility score

80

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

Image elements do not have [alt] attributes

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

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

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

qwil.io SEO score

80

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

qwil.io

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