Tools & Wizards About Us
qwal.ly screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

qwal.ly

Qwally | Say hello to your community's full potential.

Page Load Speed

2.2 sec in total

First Response

115 ms

Resources Loaded

1.6 sec

Page Rendered

501 ms

qwal.ly screenshot

About Website

Welcome to qwal.ly homepage info - get ready to check Qwal best content right away, or after learning these important things about qwal.ly

Qwally simplifies bureaucracy and support, making your community easier and more desirable to do business in. Qwally Platform, our business engagement software and CRM helps government or business sup...

Visit qwal.ly

Key Findings

We analyzed Qwal.ly page load time and found that the first response time was 115 ms and then it took 2.1 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

qwal.ly performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value2,820 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value17.9 s

4/100

10%

Network Requests Diagram

qwal.ly

115 ms

pwr.min.css

214 ms

child.min.css

229 ms

pwr-burger.min.css

391 ms

scroll-shadow.min.css

240 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 Qwal.ly, 8% (3 requests) were made to 6256149.fs1.hubspotusercontent-na1.net and 5% (2 requests) were made to No-cache.hubspot.com. The less responsive or slowest element that took the longest time to load (884 ms) relates to the external source 6256149.fs1.hubspotusercontent-na1.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 117.0 kB (41%)

Content Size

285.2 kB

After Optimization

168.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qwal.ly main page is 285.2 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. 65% of websites need less resources to load. HTML takes 116.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 100.5 kB

  • Original 116.8 kB
  • After minification 111.9 kB
  • After compression 16.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. 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 100.5 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 2.5 kB

  • Original 84.4 kB
  • After minification 81.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. Qwal images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 7.3 kB

  • Original 56.1 kB
  • After minification 56.1 kB
  • After compression 48.9 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 7.3 kB or 13% of the original size.

CSS Optimization

-24%

Potential reduce by 6.7 kB

  • Original 27.9 kB
  • After minification 27.9 kB
  • After compression 21.2 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. Qwal.ly needs all CSS files to be minified and compressed as it can save up to 6.7 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (65%)

Requests Now

31

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qwal.ly

qwal.ly

115 ms

pwr.min.css

pwr.min.css

214 ms

child.min.css

child.min.css

229 ms

pwr-burger.min.css

pwr-burger.min.css

391 ms

scroll-shadow.min.css

scroll-shadow.min.css

240 ms

js

js

85 ms

embed.js

embed.js

104 ms

pwr.min.js

pwr.min.js

261 ms

child.min.js

child.min.js

296 ms

project.js

project.js

223 ms

pwr-burger.min.js

pwr-burger.min.js

604 ms

scroll-shadow.min.js

scroll-shadow.min.js

564 ms

web-interactives-embed.js

web-interactives-embed.js

40 ms

project.js

project.js

258 ms

pwr-grid.min.js

pwr-grid.min.js

564 ms

pwr-blog-listing.min.js

pwr-blog-listing.min.js

614 ms

_dateformat.min.js

_dateformat.min.js

567 ms

v2.js

v2.js

564 ms

6256149.js

6256149.js

690 ms

index.js

index.js

570 ms

interactive-175163522838.png

interactive-175163522838.png

302 ms

Icon%20%2825%29.png

Icon%20%2825%29.png

501 ms

interactive-175191999553.png

interactive-175191999553.png

244 ms

Qwally_Workmark_Digital.svg

Qwally_Workmark_Digital.svg

247 ms

Qwally_Workmark_Digital_White.svg

Qwally_Workmark_Digital_White.svg

166 ms

Qwally_Platform_Concept_opt-1.svg

Qwally_Platform_Concept_opt-1.svg

221 ms

qwally-hero-img.svg

qwally-hero-img.svg

173 ms

Frame%20420%20%281%29.png

Frame%20420%20%281%29.png

884 ms

Icon%20%2835%29.png

Icon%20%2835%29.png

788 ms

regular.woff

regular.woff

299 ms

500.woff

500.woff

128 ms

700.woff

700.woff

262 ms

500.woff

500.woff

206 ms

regular.woff

regular.woff

129 ms

6256149.js

6256149.js

251 ms

banner.js

banner.js

167 ms

collectedforms.js

collectedforms.js

243 ms

Accessibility Review

qwal.ly accessibility score

98

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

Links do not have a discernible name

Best Practices

qwal.ly 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

High

Page has valid source maps

SEO Factors

qwal.ly SEO score

86

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qwal.ly can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Qwal.ly 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

qwal.ly

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