Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 55

    SEO

    Google-friendlier than
    30% of websites

60cards.net

Pokémon Trading Card Game Community / 60Cards

Page Load Speed

6.1 sec in total

First Response

817 ms

Resources Loaded

4.7 sec

Page Rendered

507 ms

60cards.net screenshot

About Website

Visit 60cards.net now to see the best up-to-date 60Cards content for Pakistan and also check out these interesting facts you probably never knew about 60cards.net

Visit 60cards.net

Key Findings

We analyzed 60cards.net page load time and found that the first response time was 817 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 70% of websites can load faster.

Performance Metrics

60cards.net performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value0.6 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

www.60cards.net

817 ms

css

69 ms

template.css

134 ms

addons.css

259 ms

jquery-ui.min.css

259 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 61% of them (66 requests) were addressed to the original 60cards.net, 9% (10 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain 60cards.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (22%)

Content Size

5.8 MB

After Optimization

4.5 MB

In fact, the total size of 60cards.net main page is 5.8 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. 70% of websites need less resources to load. Images take 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 31.9 kB

  • Original 41.0 kB
  • After minification 37.0 kB
  • After compression 9.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 31.9 kB or 78% of the original size.

Image Optimization

-11%

Potential reduce by 516.3 kB

  • Original 4.7 MB
  • After minification 4.2 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, 60Cards needs image optimization as it can save up to 516.3 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

-67%

Potential reduce by 435.8 kB

  • Original 654.0 kB
  • After minification 647.2 kB
  • After compression 218.3 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 435.8 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 311.6 kB

  • Original 372.2 kB
  • After minification 348.5 kB
  • After compression 60.6 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. 60cards.net needs all CSS files to be minified and compressed as it can save up to 311.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (42%)

Requests Now

103

After Optimization

60

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

Accessibility Review

60cards.net accessibility score

68

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

Document doesn't have a <title> element

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

Best Practices

60cards.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

60cards.net SEO score

55

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    CS

  • Encoding

    UTF-8

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

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