Tools & Wizards About Us
qr.gl screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

qr.gl

Welcome To QR.CR | QR.CR - The Best QR Code System

Page Load Speed

3.5 sec in total

First Response

402 ms

Resources Loaded

2.8 sec

Page Rendered

233 ms

qr.gl screenshot

About Website

Welcome to qr.gl homepage info - get ready to check QR best content for Belize right away, or after learning these important things about qr.gl

QR.CR ~ Home of the Worlds Best QR Code System

Visit qr.gl

Key Findings

We analyzed Qr.gl page load time and found that the first response time was 402 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

qr.gl performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.703

7/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

qr.gl

402 ms

qr.cr

721 ms

jotify.js

82 ms

master_main.css

256 ms

videowrapper.css

237 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Qr.gl, 84% (47 requests) were made to Qr.cr and 4% (2 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (735 ms) relates to the external source Qr.cr.

Page Optimization Overview & Recommendations

Page size can be reduced by 281.3 kB (13%)

Content Size

2.2 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qr.gl main page is 2.2 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 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 20.6 kB

  • Original 25.9 kB
  • After minification 25.1 kB
  • After compression 5.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 20.6 kB or 80% of the original size.

Image Optimization

-11%

Potential reduce by 200.1 kB

  • Original 1.9 MB
  • After minification 1.7 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. Obviously, QR needs image optimization as it can save up to 200.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-19%

Potential reduce by 57.0 kB

  • Original 297.4 kB
  • After minification 297.4 kB
  • After compression 240.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 57.0 kB or 19% of the original size.

CSS Optimization

-5%

Potential reduce by 3.6 kB

  • Original 69.9 kB
  • After minification 69.9 kB
  • After compression 66.3 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. Qr.gl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (47%)

Requests Now

49

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qr.gl

qr.gl

402 ms

qr.cr

qr.cr

721 ms

jotify.js

jotify.js

82 ms

master_main.css

master_main.css

256 ms

videowrapper.css

videowrapper.css

237 ms

form.css

form.css

241 ms

button.css

button.css

240 ms

animate.css

animate.css

243 ms

bubble.css

bubble.css

245 ms

style.css

style.css

320 ms

jquery.js

jquery.js

404 ms

jquery-ui.js

jquery-ui.js

572 ms

ddslick.js

ddslick.js

331 ms

modernizr.mq.js

modernizr.mq.js

328 ms

global.js

global.js

449 ms

jscolor.min.js

jscolor.min.js

400 ms

jquery.ui.touch-punch.js

jquery.ui.touch-punch.js

412 ms

master.js

master.js

415 ms

jquery-ui.css

jquery-ui.css

479 ms

jquery-ui-timepicker-addon.css

jquery-ui-timepicker-addon.css

484 ms

jquery-ui-timepicker-addon.js

jquery-ui-timepicker-addon.js

607 ms

firebase-app.js

firebase-app.js

28 ms

firebase-messaging.js

firebase-messaging.js

199 ms

wow.min.js

wow.min.js

493 ms

css

css

32 ms

Q55.png

Q55.png

112 ms

Editor.jpg

Editor.jpg

115 ms

statistics.jpg

statistics.jpg

169 ms

livecoupon.jpg

livecoupon.jpg

169 ms

QR-LOGO-TEST.jpg

QR-LOGO-TEST.jpg

113 ms

font-awesome.min.css

font-awesome.min.css

40 ms

tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvy1a6o3mp.ttf

tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvy1a6o3mp.ttf

19 ms

tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvLFG6o3mp.ttf

tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvLFG6o3mp.ttf

22 ms

icons.svg

icons.svg

269 ms

static6.jpg

static6.jpg

89 ms

public_controller.php

public_controller.php

471 ms

static6.jpg

static6.jpg

735 ms

icons.woff

icons.woff

170 ms

5b744dcede068_merchantlogo.png

5b744dcede068_merchantlogo.png

85 ms

5babe4a2e5796_merchantlogo.png

5babe4a2e5796_merchantlogo.png

80 ms

5b119ded47287_merchantlogo.png

5b119ded47287_merchantlogo.png

82 ms

5b74f7544bc61_merchantlogo.png

5b74f7544bc61_merchantlogo.png

316 ms

5aeb8eb27e7df_merchantlogo.png

5aeb8eb27e7df_merchantlogo.png

84 ms

5b6205a726a85_merchantlogo.png

5b6205a726a85_merchantlogo.png

264 ms

5b4eb26e5e350_merchantlogo.png

5b4eb26e5e350_merchantlogo.png

241 ms

5b4f7f83e8798_merchantlogo.png

5b4f7f83e8798_merchantlogo.png

241 ms

5d2f760d01fdd_merchantlogo.png

5d2f760d01fdd_merchantlogo.png

243 ms

5b1434e7758ec_merchantlogo.png

5b1434e7758ec_merchantlogo.png

401 ms

5bc8da8563aa2_merchantlogo.png

5bc8da8563aa2_merchantlogo.png

324 ms

5b118daf0bc05_merchantlogo.png

5b118daf0bc05_merchantlogo.png

414 ms

5b0f079280fce_merchantlogo.png

5b0f079280fce_merchantlogo.png

352 ms

5b1d77dc7465f_merchantlogo.png

5b1d77dc7465f_merchantlogo.png

372 ms

5b1188d96e73f_merchantlogo.png

5b1188d96e73f_merchantlogo.png

413 ms

dash.png

dash.png

411 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

22 ms

iubenda.js

iubenda.js

71 ms

Accessibility Review

qr.gl accessibility score

58

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

qr.gl best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

qr.gl SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qr.gl 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 Qr.gl 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

qr.gl

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