Tools & Wizards About Us
linqr.to screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

linqr.to

linQR.to | Recognizable Social Media QR-Codes Generator

Page Load Speed

2.2 sec in total

First Response

371 ms

Resources Loaded

1.7 sec

Page Rendered

102 ms

linqr.to screenshot

About Website

Welcome to linqr.to homepage info - get ready to check LinQR best content right away, or after learning these important things about linqr.to

Linking styled QR-codes to your Social Media profiles, including Facebook, Twitter and LinkedIn. Generate recognizable QR-codes pretty well comparable to common social media icons.

Visit linqr.to

Key Findings

We analyzed Linqr.to page load time and found that the first response time was 371 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

linqr.to performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

linqr.to

371 ms

MuseoSans_500.css

427 ms

tipsy.css

452 ms

style.css

445 ms

jquery.min.js

33 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 74% of them (43 requests) were addressed to the original Linqr.to, 7% (4 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (688 ms) belongs to the original domain Linqr.to.

Page Optimization Overview & Recommendations

Page size can be reduced by 70.0 kB (15%)

Content Size

452.3 kB

After Optimization

382.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Linqr.to main page is 452.3 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 248.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 29.2 kB

  • Original 37.5 kB
  • After minification 36.8 kB
  • After compression 8.4 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 29.2 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 5.8 kB

  • Original 156.3 kB
  • After minification 150.5 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. LinQR images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 27.3 kB

  • Original 248.4 kB
  • After minification 242.9 kB
  • After compression 221.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 27.3 kB or 11% of the original size.

CSS Optimization

-77%

Potential reduce by 7.8 kB

  • Original 10.1 kB
  • After minification 7.5 kB
  • After compression 2.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. Linqr.to needs all CSS files to be minified and compressed as it can save up to 7.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (27%)

Requests Now

55

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

linqr.to

linqr.to

371 ms

MuseoSans_500.css

MuseoSans_500.css

427 ms

tipsy.css

tipsy.css

452 ms

style.css

style.css

445 ms

jquery.min.js

jquery.min.js

33 ms

jquery.timeago.js

jquery.timeago.js

443 ms

jquery.tipsy.js

jquery.tipsy.js

443 ms

jquery.cycle.min.js

jquery.cycle.min.js

544 ms

linqr.js

linqr.js

525 ms

widgets.js

widgets.js

29 ms

in.js

in.js

31 ms

all.js

all.js

31 ms

ga.js

ga.js

37 ms

195 ms

default.jpg

default.jpg

35 ms

default.jpg

default.jpg

226 ms

texture.jpg

texture.jpg

100 ms

logo.png

logo.png

139 ms

logo_hover.png

logo_hover.png

94 ms

logo_clicksmash.png

logo_clicksmash.png

95 ms

facebook.png

facebook.png

100 ms

facebooklike.png

facebooklike.png

141 ms

twitter.png

twitter.png

199 ms

linkedin.png

linkedin.png

199 ms

youtube.png

youtube.png

199 ms

wordpress.png

wordpress.png

211 ms

blogger.png

blogger.png

206 ms

myspace.png

myspace.png

217 ms

orkut.png

orkut.png

304 ms

hyves.png

hyves.png

301 ms

vimeo.png

vimeo.png

305 ms

flickr.png

flickr.png

307 ms

advanced.png

advanced.png

308 ms

arrow_down_light.png

arrow_down_light.png

312 ms

zoom_in.png

zoom_in.png

386 ms

qr-4400.png

qr-4400.png

414 ms

no_user_image.png

no_user_image.png

415 ms

qr-4646.png

qr-4646.png

441 ms

qr-4647.png

qr-4647.png

442 ms

qr-5054.png

qr-5054.png

415 ms

qr-4866.png

qr-4866.png

492 ms

qr-5010.png

qr-5010.png

534 ms

tip_0.png

tip_0.png

509 ms

tip_1.png

tip_1.png

605 ms

tip_2.png

tip_2.png

593 ms

tip_3.png

tip_3.png

656 ms

ad.png

ad.png

688 ms

MuseoSans_500-webfont.woff

MuseoSans_500-webfont.woff

665 ms

__utm.gif

__utm.gif

48 ms

all.js

all.js

44 ms

arrow_up.gif

arrow_up.gif

571 ms

trans.png

trans.png

653 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

58 ms

settings

settings

76 ms

no_user_image.png

no_user_image.png

108 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

3 ms

embeds

embeds

22 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

16 ms

Accessibility Review

linqr.to accessibility score

80

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

linqr.to best practices score

58

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

Browser errors were logged to the console

SEO Factors

linqr.to SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

linqr.to

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