Tools & Wizards About Us
qrtag.fr screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

qrtag.fr

SBE Direct, Identifier & Sécuriser les biens et les personnes en entreprise

Page Load Speed

2.9 sec in total

First Response

348 ms

Resources Loaded

2.1 sec

Page Rendered

407 ms

qrtag.fr screenshot

About Website

Visit qrtag.fr now to see the best up-to-date Qrtag content and also check out these interesting facts you probably never knew about qrtag.fr

Tout pour identifier et sécuriser vos biens en entreprise: étiquettes d'inventaire, étiquettes sécurisées, traçabilité, RFID, plaques de firme, hologrammes, systèmes antivol, papiers sécurisés, c...

Visit qrtag.fr

Key Findings

We analyzed Qrtag.fr page load time and found that the first response time was 348 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

qrtag.fr performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value17.3 s

0/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value3,190 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

qrtag.fr

348 ms

sbedirect.fr

271 ms

722 ms

gtm.js

119 ms

theme-937c3b.css

254 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Qrtag.fr, 35% (9 requests) were made to Fonts.gstatic.com and 27% (7 requests) were made to Sbedirect.com. The less responsive or slowest element that took the longest time to load (729 ms) relates to the external source Sbedirect.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 260.7 kB (27%)

Content Size

967.4 kB

After Optimization

706.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qrtag.fr main page is 967.4 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. 55% of websites need less resources to load. Javascripts take 497.2 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 259.3 kB

  • Original 292.4 kB
  • After minification 216.0 kB
  • After compression 33.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 76.4 kB, which is 26% 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 259.3 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 13.7 kB
  • After minification 13.7 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. Qrtag images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.0 kB

  • Original 497.2 kB
  • After minification 497.2 kB
  • After compression 496.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 300 B

  • Original 164.1 kB
  • After minification 164.1 kB
  • After compression 163.8 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. Qrtag.fr has all CSS files already compressed.

Requests Breakdown

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

Requests Now

13

After Optimization

4

  • Images
  • JavaScript
  • CSS

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qrtag. 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

qrtag.fr

qrtag.fr

348 ms

sbedirect.fr

sbedirect.fr

271 ms

722 ms

gtm.js

gtm.js

119 ms

theme-937c3b.css

theme-937c3b.css

254 ms

head-5b2626.js

head-5b2626.js

248 ms

js

js

193 ms

api.js

api.js

41 ms

bottom-977925.js

bottom-977925.js

729 ms

css

css

54 ms

css

css

69 ms

css

css

76 ms

css

css

77 ms

recaptcha__en.js

recaptcha__en.js

69 ms

blank.png

blank.png

132 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

258 ms

bg-edito.jpg

bg-edito.jpg

117 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

21 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

52 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

76 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

79 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

79 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

77 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

80 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

78 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

77 ms

Accessibility Review

qrtag.fr accessibility score

80

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

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

Best Practices

qrtag.fr 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

qrtag.fr SEO score

85

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qrtag.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Qrtag.fr 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

qrtag.fr

Open Graph description is not detected on the main page of Qrtag. 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: