3.4 sec in total
1.2 sec
2 sec
197 ms
Visit qlr.us now to see the best up-to-date Qlr content for Sri Lanka and also check out these interesting facts you probably never knew about qlr.us
This domain may be for sale!
Visit qlr.usWe analyzed Qlr.us page load time and found that the first response time was 1.2 sec 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.
qlr.us performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value3.2 s
73/100
25%
Value2.9 s
95/100
10%
Value140 ms
95/100
30%
Value0.224
56/100
15%
Value3.2 s
94/100
10%
1212 ms
87 ms
139 ms
165 ms
163 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 44% of them (14 requests) were addressed to the original Qlr.us, 13% (4 requests) were made to Pagead2.googlesyndication.com and 13% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Qlr.us.
Page size can be reduced by 200.5 kB (71%)
283.9 kB
83.4 kB
In fact, the total size of Qlr.us main page is 283.9 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. 40% of websites need less resources to load. Javascripts take 138.5 kB which makes up the majority of the site volume.
Potential reduce by 37.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. This page needs HTML code to be minified as it can gain 13.6 kB, which is 30% 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 37.0 kB or 81% of the original size.
Potential reduce by 217 B
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. Qlr images are well optimized though.
Potential reduce by 87.6 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 87.6 kB or 63% of the original size.
Potential reduce by 75.6 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. Qlr.us needs all CSS files to be minified and compressed as it can save up to 75.6 kB or 82% of the original size.
Number of requests can be reduced by 18 (60%)
30
12
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qlr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
qlr.us
1212 ms
column.css
87 ms
form.css
139 ms
main_min.css
165 ms
default-theme.css
163 ms
select2.css
175 ms
fg.menu.css
198 ms
jquery-ui-1.8.23.custom.css
190 ms
jquery.min.js
42 ms
jquery-ui.min.js
48 ms
jquery.select2.js
259 ms
jquery.fg.menu.js
237 ms
jquery.wookmark.js
261 ms
ZeroClipboard.js
261 ms
show_ads.js
5 ms
paper.png
99 ms
ca-pub-8775695350394699.js
71 ms
zrt_lookup.html
68 ms
show_ads_impl.js
70 ms
analytics.js
32 ms
select2.png
105 ms
collect
66 ms
ads
242 ms
osd.js
20 ms
ads
210 ms
m_js_controller.js
22 ms
abg.js
48 ms
favicon
66 ms
googlelogo_color_112x36dp.png
65 ms
nessie_icon_tiamat_white.png
50 ms
s
37 ms
x_button_blue2.png
25 ms
qlr.us accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
qlr.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
qlr.us SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qlr.us 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 Qlr.us 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.
qlr.us
Open Graph description is not detected on the main page of Qlr. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: