3.1 sec in total
319 ms
2.5 sec
302 ms
Visit qrs.ly now to see the best up-to-date QR S content for United States and also check out these interesting facts you probably never knew about qrs.ly
ll➤ Create non-expiring free QR codes with our online QR code generator ➤ No sign-up required ✓ QR codes for websites, images, menus, Instagram & more.
Visit qrs.lyWe analyzed Qrs.ly page load time and found that the first response time was 319 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
qrs.ly performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value3.6 s
61/100
25%
Value6.4 s
41/100
10%
Value12,840 ms
0/100
30%
Value0.038
100/100
15%
Value20.7 s
2/100
10%
319 ms
477 ms
155 ms
438 ms
37 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Qrs.ly, 31% (38 requests) were made to Img.qrstuff.com and 25% (31 requests) were made to Qrstuff.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Img.qrstuff.com.
Page size can be reduced by 1.1 MB (51%)
2.1 MB
1.0 MB
In fact, the total size of Qrs.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. 80% 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. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 123.2 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 123.2 kB or 82% of the original size.
Potential reduce by 49.3 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. QR S images are well optimized though.
Potential reduce by 645.4 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 645.4 kB or 62% of the original size.
Potential reduce by 258.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. Qrs.ly needs all CSS files to be minified and compressed as it can save up to 258.4 kB or 82% of the original size.
Number of requests can be reduced by 46 (39%)
117
71
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of QR S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
qrs.ly
319 ms
www.qrstuff.com
477 ms
all-24954e40a4.min.css
155 ms
all-0ca6eeb48b.min.js
438 ms
adsbygoogle.js
37 ms
js
62 ms
widgets.js
34 ms
all.js
91 ms
analytics.js
22 ms
collect
10 ms
collect
46 ms
ga-audiences
47 ms
fbevents.js
48 ms
g-feature-codes.png
634 ms
ir
170 ms
back.gif
159 ms
button-dbc-create.png
159 ms
button-dbc-modify.png
160 ms
button-dbc-create-again.png
251 ms
upload-cloud-file.svg
252 ms
upload-cloud-doc.svg
249 ms
button-visualead-linkedin.png
626 ms
button-visualead-twitter.png
625 ms
button-visualead-facebook.png
627 ms
button-visualead-youtube.png
523 ms
button-visualead-contact-details.png
624 ms
button-visualead-google-maps.png
335 ms
default_qrcode.png
625 ms
button-download.png
631 ms
button-print.png
734 ms
button-email.png
727 ms
button-zazzle.png
733 ms
button-visualead.jpg
734 ms
qrdroid-front.png
732 ms
g-feature-scans.png
733 ms
g-feature-edit.png
732 ms
space.gif
731 ms
top.gif
733 ms
g-login-ajax.gif
733 ms
g-social-media.png
730 ms
subscribe1.png
894 ms
g-close.png
810 ms
g-warning.png
804 ms
inputbutton1.gif
801 ms
inputbutton2.gif
802 ms
dbc-sample.png
970 ms
inputbutton3-unsubscribed.gif
874 ms
inputbutton3-subscribed.gif
876 ms
panel3-head.gif
880 ms
download-button.png
893 ms
inputbutton4-output-type.gif
956 ms
button-batch-off.png
957 ms
1118337034.png
1033 ms
1456347837.png
976 ms
0965900037.png
976 ms
0470616687.png
1081 ms
1460920295.png
1099 ms
1118167783.png
1052 ms
0910965900.png
1060 ms
zapper-front.png
1060 ms
zapperi-front.png
1107 ms
zapperw-front.png
1131 ms
drinktracker1-front.png
1145 ms
analyticspro-front.png
1144 ms
scannerpro-front.png
1151 ms
calculatorpro-front.png
1173 ms
blog.png
1184 ms
subscribe.png
1212 ms
account.gif
1227 ms
ir
158 ms
ir
158 ms
ir
158 ms
ir
157 ms
ir
157 ms
ir
191 ms
ca-pub-7324999811165292.js
144 ms
zrt_lookup.html
266 ms
show_ads_impl.js
227 ms
538284599658414
123 ms
generate-style-code.png
650 ms
generate-style-plus.png
720 ms
preview-bg.png
723 ms
DUKxjCxqlkE
241 ms
RI1fqzFoMKI
536 ms
colorpicker_background_qr.png
718 ms
colorpicker_overlay.png
718 ms
colorpicker_select.gif
717 ms
colorpicker_indic.gif
718 ms
upload-cloud-file.svg
733 ms
upload-cloud-doc.svg
743 ms
button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js
46 ms
221 ms
0sTQzbapM8j.js
193 ms
ping
284 ms
like.php
432 ms
160 ms
tweet_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html
84 ms
ads
335 ms
osd.js
43 ms
ads
313 ms
www-player-vflMqr8uC.css
35 ms
www-embed-player.js
34 ms
base.js
55 ms
id
223 ms
YubHWiCUdycrt9r0pwxtCFMvWBBxMHmgtw0lFaZzSbY.js
181 ms
ad_status.js
282 ms
jot
337 ms
logo_ringo-vflOpz8ZI.png
230 ms
Iv-bqISgsE7.js
286 ms
lH1ibRl5GKq.png
296 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
199 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
214 ms
log
205 ms
adServer.bs
214 ms
m_window_focus_non_hydra.js
187 ms
osd_listener.js
189 ms
m_qs_click_protection.js
204 ms
adServer.bs
154 ms
log
125 ms
bottom1.gif
606 ms
52 ms
bottomlogo.gif
498 ms
transparent.png
18 ms
qrs.ly accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA progressbar elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
Links do not have a discernible name
qrs.ly best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
qrs.ly SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Qrs.ly 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 Qrs.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.
qrs.ly
Open Graph data is detected on the main page of QR S. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: