5.5 sec in total
329 ms
4.1 sec
1.1 sec
Welcome to qr1.at homepage info - get ready to check QR 1 best content for Germany right away, or after learning these important things about qr1.at
Individuelle QR Codes erstellen ✅ Viele QR Code Typen ✅ Mit Vorlagen & Logos ✅ Frei wählbare Farben & Rahmen ▶ Jetzt generieren
Visit qr1.atWe analyzed Qr1.at page load time and found that the first response time was 329 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
qr1.at performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value3.3 s
71/100
25%
Value3.0 s
94/100
10%
Value30 ms
100/100
30%
Value0.009
100/100
15%
Value3.7 s
90/100
10%
329 ms
1360 ms
454 ms
411 ms
338 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 97% of them (86 requests) were addressed to the original Qr1.at, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Qr1.at.
Page size can be reduced by 323.7 kB (32%)
1.0 MB
688.5 kB
In fact, the total size of Qr1.at main page is 1.0 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. 45% of websites need less resources to load. Images take 558.6 kB which makes up the majority of the site volume.
Potential reduce by 84.6 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 20.4 kB, which is 20% 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 84.6 kB or 82% of the original size.
Potential reduce by 7.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. QR 1 images are well optimized though.
Potential reduce by 181.1 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 181.1 kB or 63% of the original size.
Potential reduce by 50.1 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. Qr1.at needs all CSS files to be minified and compressed as it can save up to 50.1 kB or 79% of the original size.
Number of requests can be reduced by 35 (41%)
86
51
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of QR 1. 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 as a result speed up the page load time.
qr1.at
329 ms
qr1.at
1360 ms
jquery.js
454 ms
style.css
411 ms
common.js
338 ms
foundation.min.js
546 ms
jquery.qrcode.js
323 ms
qrcode.js
521 ms
bpopup.js
522 ms
checkbox.js
523 ms
generator.js
524 ms
jquery.chosen.js
527 ms
logo-qr.png
156 ms
icon-help-46.png
146 ms
approval-48.png
149 ms
arrowdown.png
147 ms
link-icon-white.png
149 ms
icon-text.png
191 ms
vcard-icon.png
213 ms
icon-trackable.png
214 ms
icon-mobile-website.png
213 ms
ajax-loader.gif
230 ms
icon-eps48.png
229 ms
icon-pdf_48.png
289 ms
icon-svg48.png
302 ms
icon-png48.png
314 ms
iphone-weiss-jungidee.jpg
799 ms
icon-info48.png
340 ms
big-arrow.png
340 ms
icon-check64.png
393 ms
designer-qr-code-thumb.png
644 ms
zazzle-products.jpg
524 ms
iphone-frame.png
569 ms
qr-code-marketing400.jpg
680 ms
pdf_icon_48.png
498 ms
qr-manager-dashboard.png
709 ms
charts.png
769 ms
vector-formats.png
686 ms
pin128.png
744 ms
qr-map.png
909 ms
qr-code-notification.png
797 ms
dummy
766 ms
qr-codes-details.png
787 ms
scheduled-redirects.gif
816 ms
landingpage-templates-cut-de.jpg
960 ms
darganddrop-de.gif
981 ms
OpenSans-Regular-webfont.woff
967 ms
OpenSans-Semibold-webfont.woff
818 ms
OpenSans-Light-webfont.woff
949 ms
OpenSans-Bold-webfont.woff
891 ms
OpenSans-ExtraBold-webfont.woff
923 ms
export-json.png
993 ms
csv128.png
1006 ms
waypoints.min.js
955 ms
piwik.js
942 ms
general_foundicons.woff
1116 ms
OpenSans-Italic-webfont.woff
1143 ms
OpenSans-SemiboldItalic-webfont.woff
1137 ms
OpenSans-LightItalic-webfont.woff
1139 ms
OpenSans-BoldItalic-webfont.woff
1077 ms
OpenSans-ExtraBoldItalic-webfont.woff
1063 ms
zip128.png
1052 ms
wl-subdomain-de.png
1133 ms
icon-question.png
1130 ms
paypal-logo-100px.png
1068 ms
arrow-down.png
972 ms
external-link.png
947 ms
icon-download.png
905 ms
dashed-line.png
906 ms
yes.png
872 ms
amex.png
878 ms
icon-mastercard.png
861 ms
icon-visa.png
828 ms
facebook-icon.png
798 ms
twitter-icon.png
854 ms
youtube-icon.png
857 ms
google-icon.png
857 ms
question-icon-gray.png
829 ms
arrow-up.png
808 ms
facebook_circle_gray.svg
776 ms
twitter_circle_gray.svg
793 ms
youtube_circle_gray.svg
742 ms
google_circle_gray.svg
748 ms
waypoints-sticky.min.js
638 ms
analytics.js
194 ms
piwik.php
650 ms
chosen-sprite.png
498 ms
collect
21 ms
collect
59 ms
qr1.at accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
qr1.at 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
qr1.at SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qr1.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Qr1.at 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.
qr1.at
Open Graph data is detected on the main page of QR 1. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: