Tools & Wizards About Us
mrplayingcard.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

mrplayingcard.com

Custom Playing Cards | Mr. Playing Card

Page Load Speed

294 ms in total

First Response

40 ms

Resources Loaded

254 ms

Page Rendered

0 ms

mrplayingcard.com screenshot

About Website

Click here to check amazing Mr Playing Card content. Otherwise, check out these important facts you probably never knew about mrplayingcard.com

Mr. Playing Card produces the highest quality playing cards on the planet. We are a custom playing card printer that serves a wide variety of customers. Whether you are ordering playing cards for the ...

Visit mrplayingcard.com

Key Findings

We analyzed Mrplayingcard.com page load time and found that the first response time was 40 ms and then it took 254 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

mrplayingcard.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value2,340 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

mrplayingcard.com

40 ms

mrplayingcard.com

40 ms

gtm.js

123 ms

796820.js

145 ms

javascript;base64,dmFyIHNjcmlwdCA9IGRvY3VtZW50LmNyZWF0ZUVsZW1lbnQoInNjcmlwdCIpO3NjcmlwdC5zcmMgPSAiaHR0cHM6Ly9kYXNoYm9hcmQubGlua2dyYXBoLmNvbS9zY3JpcHRzL2R5bmFtaWNfb3B0aW1pemF0aW9uLmpzIjtzY3JpcHQuZGF0YXNldC51dWlkID0gIjIxOTE4MTM5LTgxZmItNDFlNi04Y2I2LTFmZmQ0ZGU3MDBjYyI7c2NyaXB0LmlkID0gInNhLWR5bmFtaWMtb3B0aW1pemF0aW9uLWxvYWRlciI7ZG9jdW1lbnQuaGVhZC5hcHBlbmRDaGlsZChzY3JpcHQpOw==

10 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 82% of them (18 requests) were addressed to the original Mrplayingcard.com, 5% (1 request) were made to Googletagmanager.com and 5% (1 request) were made to Secure.7-companycompany.com. The less responsive or slowest element that took the longest time to load (145 ms) relates to the external source Secure.7-companycompany.com.

Page Optimization Overview & Recommendations

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

Content Size

790.4 kB

After Optimization

670.9 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Mrplayingcard.com main page is 790.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. 65% of websites need less resources to load. Javascripts take 603.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 119.3 kB

  • Original 159.3 kB
  • After minification 158.8 kB
  • After compression 40.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. 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 119.3 kB or 75% of the original size.

JavaScript Optimization

-0%

Potential reduce by 213 B

  • Original 603.2 kB
  • After minification 603.2 kB
  • After compression 603.0 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 0 B

  • Original 28.0 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.

Requests Breakdown

Number of requests can be reduced by 17 (89%)

Requests Now

19

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

mrplayingcard.com

mrplayingcard.com

40 ms

mrplayingcard.com

mrplayingcard.com

40 ms

gtm.js

gtm.js

123 ms

796820.js

796820.js

145 ms

javascript;base64,dmFyIHNjcmlwdCA9IGRvY3VtZW50LmNyZWF0ZUVsZW1lbnQoInNjcmlwdCIpO3NjcmlwdC5zcmMgPSAiaHR0cHM6Ly9kYXNoYm9hcmQubGlua2dyYXBoLmNvbS9zY3JpcHRzL2R5bmFtaWNfb3B0aW1pemF0aW9uLmpzIjtzY3JpcHQuZGF0YXNldC51dWlkID0gIjIxOTE4MTM5LTgxZmItNDFlNi04Y2I2LTFmZmQ0ZGU3MDBjYyI7c2NyaXB0LmlkID0gInNhLWR5bmFtaWMtb3B0aW1pemF0aW9uLWxvYWRlciI7ZG9jdW1lbnQuaGVhZC5hcHBlbmRDaGlsZChzY3JpcHQpOw==

javascript;base64,dmFyIHNjcmlwdCA9IGRvY3VtZW50LmNyZWF0ZUVsZW1lbnQoInNjcmlwdCIpO3NjcmlwdC5zcmMgPSAiaHR0cHM6Ly9kYXNoYm9hcmQubGlua2dyYXBoLmNvbS9zY3JpcHRzL2R5bmFtaWNfb3B0aW1pemF0aW9uLmpzIjtzY3JpcHQuZGF0YXNldC51dWlkID0gIjIxOTE4MTM5LTgxZmItNDFlNi04Y2I2LTFmZmQ0ZGU3MDBjYyI7c2NyaXB0LmlkID0gInNhLWR5bmFtaWMtb3B0aW1pemF0aW9uLWxvYWRlciI7ZG9jdW1lbnQuaGVhZC5hcHBlbmRDaGlsZChzY3JpcHQpOw==

10 ms

57300b64a4d0def5.css

57300b64a4d0def5.css

13 ms

polyfills-0d1b80a048d4787e.js

polyfills-0d1b80a048d4787e.js

41 ms

webpack-1476a750b6b4fe3c.js

webpack-1476a750b6b4fe3c.js

40 ms

framework-ee9b4b0cb5f81426.js

framework-ee9b4b0cb5f81426.js

55 ms

main-be129ed33fff77bf.js

main-be129ed33fff77bf.js

40 ms

_app-061c2415ac3b2896.js

_app-061c2415ac3b2896.js

40 ms

c7001e45-41c5c7f64a49c335.js

c7001e45-41c5c7f64a49c335.js

90 ms

bc42faac-a51f08fb79fcc200.js

bc42faac-a51f08fb79fcc200.js

103 ms

3060-aeeba01e1be07259.js

3060-aeeba01e1be07259.js

90 ms

4130-c602e15de0a35bfd.js

4130-c602e15de0a35bfd.js

89 ms

9789-cdaabc631bd74010.js

9789-cdaabc631bd74010.js

89 ms

6805-75f09b3c5f369a03.js

6805-75f09b3c5f369a03.js

112 ms

index-cd36e64afccf6061.js

index-cd36e64afccf6061.js

108 ms

_buildManifest.js

_buildManifest.js

108 ms

_ssgManifest.js

_ssgManifest.js

108 ms

dynamic_optimization.js

dynamic_optimization.js

136 ms

_error-df6c058a6a42faa5.js

_error-df6c058a6a42faa5.js

24 ms

Accessibility Review

mrplayingcard.com accessibility score

90

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

[id] attributes on active, focusable elements are not unique

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

mrplayingcard.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

mrplayingcard.com SEO score

100

Search Engine Optimization Advices

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 Mrplayingcard.com 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 Mrplayingcard.com 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

mrplayingcard.com

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