6.1 sec in total
817 ms
4.7 sec
507 ms
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.netWe 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 75% of websites can load faster.
60cards.net performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
817 ms
69 ms
134 ms
259 ms
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 size can be reduced by 1.3 MB (23%)
5.8 MB
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.
Potential reduce by 31.9 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.
Potential reduce by 516.3 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. 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.
Potential reduce by 467.7 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 467.7 kB or 68% of the original size.
Potential reduce by 311.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.
Number of requests can be reduced by 43 (42%)
103
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.
www.60cards.net
817 ms
css
69 ms
template.css
134 ms
addons.css
259 ms
jquery-ui.min.css
259 ms
jquery-ui.theme.min.css
252 ms
jquery.bxslider.css
256 ms
colorbox.min.css
255 ms
jquery.min.js
387 ms
amplify.min.js
376 ms
handlebars.min.js
516 ms
underscore-min.js
379 ms
jquery-ui.min.js
661 ms
simple_basket.js
377 ms
simple_favourites.js
530 ms
jquery.fetchproducts.js
529 ms
simple_ajax.js
514 ms
tinythumb.js
528 ms
jquery.bxslider.min.js
653 ms
jquery.cookie.min.js
652 ms
jquery.colorbox-min.js
654 ms
fX6vVTOxe9g
201 ms
headerA.png
238 ms
logo.png
357 ms
arrow-down-mini.png
490 ms
facebook.png
491 ms
twitter.png
489 ms
menu_home.png
490 ms
menu_eshop.png
492 ms
menu_experts.png
595 ms
menu_community.png
594 ms
Sale%20pokemon.png
1741 ms
Bronbron.png
1730 ms
Flareon1.png
1741 ms
Archeops.png
1739 ms
blog_header_2.jpg
1728 ms
VIRIzion.png
1739 ms
max.png
2217 ms
Mewtwo-lucario.png
1972 ms
Pokemon%20cave.jpg
1981 ms
Vileplume-60cards.jpg
2108 ms
swan2.png
2474 ms
Raichu.png
2113 ms
Jol.png
2351 ms
Untitled%209.jpg
2596 ms
Josh%20Marking.png
2616 ms
latestBlogEntries_h2.png
2236 ms
latestNews_h3.png
2339 ms
likebox.php
114 ms
hp-banner-eshop_en.png
2298 ms
ODelI1aHBYDBqgeIAH2zlDLXPPWpYIJRcQ99gLLWTOQ.woff
123 ms
toadOcfmlt9b38dHJxOBGOHJdKliW2M9IhUT0esa8kM.woff
193 ms
hp-banner-ec_en.png
2373 ms
hp-banner-60cc_en.png
2381 ms
33ebd5b07dc7e407752fe773eed20635.jpg
2396 ms
more_arrow.png
2497 ms
704afe073992cbe4813cae2f7715336f.jpg
2515 ms
YQe3dSsMbL6.css
164 ms
ikPBP94Hp80.css
313 ms
Vqr3k1iJZIS.js
391 ms
b94UUzHjapV.js
531 ms
0wM5s1Khldu.js
514 ms
TTCre3391I0.js
512 ms
www-embed-player-vflQrT_sR.css
340 ms
www-embed-player.js
559 ms
base.js
807 ms
featuredCards_h2.png
2380 ms
m_3947.jpg
2764 ms
m_3731.jpg
2862 ms
m_3829.jpg
2753 ms
latestBlogEntries_h3.png
2465 ms
sdk.js
317 ms
analytics.js
292 ms
1642.js
9 ms
widget_v2.132.js
16 ms
s
284 ms
u
350 ms
__$$__stringtable_lang_cs.js
121 ms
pro-banner.png
2258 ms
xybreakthrough.jpg
2262 ms
small%20greninja.png
2387 ms
video_h2.png
2388 ms
footer_logo.png
2384 ms
arrow_up.png
2404 ms
overlay.png
2388 ms
collect
205 ms
141 ms
12592688_906014149496993_6510042528480710200_n.jpg
160 ms
10592890_631374140294330_3215171016997754004_n.jpg
165 ms
149375_226608664107333_330371021_n.jpg
194 ms
10500360_1650780385149031_5878096921071400057_n.jpg
209 ms
1464637_545001685597897_1587447675_n.jpg
217 ms
12509359_523397284502384_3486881041508301607_n.jpg
218 ms
599336_334840223305191_200872561_n.jpg
216 ms
10301191_10205958180266024_7284770730864352663_n.jpg
215 ms
wL6VQj7Ab77.png
103 ms
s7jcwEQH7Sx.png
102 ms
xd_arbiter.php
94 ms
xd_arbiter.php
172 ms
I6-MnjEovm5.js
19 ms
f6T91Deal_q.js
21 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
634 ms
ad_status.js
606 ms
avatar_simple_visitor.png
143 ms
bx_loader.gif
1374 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
142 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
169 ms
controls.png
1381 ms
aL63HcygAAVYuCCsAAA==
2 ms
60cards.net accessibility score
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
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
<html> element does not have a [lang] attribute
60cards.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
60cards.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
EN
CS
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.
60cards.net
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: