Tools & Wizards About Us
qwal.ly screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

qwal.ly

Qwally — We Accelerate Small Business

Page Load Speed

1.9 sec in total

First Response

55 ms

Resources Loaded

923 ms

Page Rendered

911 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

We Accelerate Small Business. You want to break down barriers for your business community. We give you the tools and insights to do it.

Visit qwal.ly

Key Findings

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

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value3,160 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.639

9/100

15%

TTI (Time to Interactive)

Value23.0 s

1/100

10%

Network Requests Diagram

qwal.ly

55 ms

js

138 ms

css2

72 ms

plyr.css

80 ms

shell.js

93 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 58% of them (19 requests) were addressed to the original Qwal.ly, 15% (5 requests) were made to Pro.fontawesome.com and 6% (2 requests) were made to Cdn.plyr.io. The less responsive or slowest element that took the longest time to load (260 ms) belongs to the original domain Qwal.ly.

Page Optimization Overview & Recommendations

Page size can be reduced by 371.8 kB (17%)

Content Size

2.1 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qwal.ly main page is 2.1 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 35.1 kB

  • Original 41.3 kB
  • After minification 30.1 kB
  • After compression 6.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 11.2 kB, which is 27% 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 35.1 kB or 85% of the original size.

Image Optimization

-8%

Potential reduce by 121.9 kB

  • Original 1.5 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. Qwal images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 231 B

  • Original 650 B
  • After minification 650 B
  • After compression 419 B

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 231 B or 36% of the original size.

CSS Optimization

-36%

Potential reduce by 214.5 kB

  • Original 591.0 kB
  • After minification 591.0 kB
  • After compression 376.5 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 214.5 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (32%)

Requests Now

28

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 28 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 6 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

qwal.ly

qwal.ly

55 ms

js

js

138 ms

css2

css2

72 ms

plyr.css

plyr.css

80 ms

shell.js

shell.js

93 ms

all.css

all.css

92 ms

tailwind.css

tailwind.css

195 ms

hero.css

hero.css

69 ms

plyr.js

plyr.js

124 ms

alpine.min.js

alpine.min.js

59 ms

ejjfkuaqwf

ejjfkuaqwf

139 ms

Qwally%20Logo%20LIGHT.svg

Qwally%20Logo%20LIGHT.svg

54 ms

Qwally%20Logo.svg

Qwally%20Logo.svg

126 ms

BizCareMockup.png

BizCareMockup.png

57 ms

BizCare%20Portal.png

BizCare%20Portal.png

127 ms

BizCare%20SBNav.png

BizCare%20SBNav.png

260 ms

GovDash%20Home.png

GovDash%20Home.png

150 ms

Mobile%20AL%20Logo%20Color.svg

Mobile%20AL%20Logo%20Color.svg

133 ms

KCMO%20Logo%20Color.svg

KCMO%20Logo%20Color.svg

128 ms

Wichita%20Logo%20Color.svg

Wichita%20Logo%20Color.svg

146 ms

Manor%20Logo%20Color.svg

Manor%20Logo%20Color.svg

140 ms

Brookline_Logo_Blue.svg

Brookline_Logo_Blue.svg

159 ms

Rochester_Logo_Color.svg

Rochester_Logo_Color.svg

144 ms

get-konnected-logo-r.svg

get-konnected-logo-r.svg

147 ms

Mobile-Chamber-new-color.svg

Mobile-Chamber-new-color.svg

148 ms

Mobile_Logo.svg

Mobile_Logo.svg

150 ms

mobilemayor.png

mobilemayor.png

193 ms

fa-solid-900.woff

fa-solid-900.woff

32 ms

fa-regular-400.woff

fa-regular-400.woff

34 ms

fa-light-300.woff

fa-light-300.woff

64 ms

fa-brands-400.woff

fa-brands-400.woff

65 ms

clarity.js

clarity.js

19 ms

c.gif

c.gif

7 ms

Accessibility Review

qwal.ly accessibility score

85

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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

High

Page has valid source maps

SEO Factors

qwal.ly SEO score

83

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

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: