14.1 sec in total
1.3 sec
12.4 sec
422 ms
Click here to check amazing Popkart content. Otherwise, check out these important facts you probably never knew about popkart.com
《跑跑卡丁车》是世纪天成代理,NEXON出品的休闲赛车竞速网游。游戏涵盖了当下年轻人最喜欢的竞速、漂移、冒险等玩法。曾创休闲网游最高在线记录!总用户注册达3亿!
Visit popkart.comWe analyzed Popkart.com page load time and found that the first response time was 1.3 sec and then it took 12.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
popkart.com performance score
name
value
score
weighting
Value5.3 s
8/100
10%
Value13.5 s
0/100
25%
Value8.6 s
17/100
10%
Value50 ms
100/100
30%
Value0.975
2/100
15%
Value9.1 s
33/100
10%
1307 ms
212 ms
227 ms
691 ms
779 ms
Our browser made a total of 146 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Popkart.com, 47% (68 requests) were made to Img5.tiancitycdn.com and 12% (17 requests) were made to Image.tiancity.com. The less responsive or slowest element that took the longest time to load (5.8 sec) relates to the external source Img5.tiancitycdn.com.
Page size can be reduced by 139.5 kB (2%)
6.4 MB
6.3 MB
In fact, the total size of Popkart.com main page is 6.4 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. 50% of websites need less resources to load. Images take 6.3 MB which makes up the majority of the site volume.
Potential reduce by 72.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. This page needs HTML code to be minified as it can gain 14.9 kB, which is 17% 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 72.2 kB or 82% of the original size.
Potential reduce by 62.1 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. Popkart images are well optimized though.
Potential reduce by 4.4 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.
Potential reduce by 741 B
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. Popkart.com has all CSS files already compressed.
Number of requests can be reduced by 14 (10%)
141
127
The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Popkart. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
popkart.com
1307 ms
212 ms
227 ms
normalize.min.css
691 ms
animate.min.css
779 ms
jquery.slider.css
1090 ms
style240502.css
631 ms
jquery-1.7.2.min.js
692 ms
gnb-utf8.js
495 ms
layout.aspx
1035 ms
menu.js
593 ms
layout.aspx
1046 ms
layout.aspx
1050 ms
layout.aspx
1121 ms
layout.aspx
1127 ms
layout.aspx
1158 ms
layout.aspx
1232 ms
layout.aspx
1253 ms
layout.aspx
1247 ms
layout.aspx
1339 ms
layout.aspx
1346 ms
layout.aspx
1384 ms
copyright.min.js
667 ms
jquery.easing.min.js
1254 ms
common-2.0.0.min.js
991 ms
jquery.slider.min.js
2103 ms
jquery.marquee.min.js
1330 ms
mian240502.js
592 ms
240415.jpg
439 ms
240312.jpg
1081 ms
kr231012.jpg
1649 ms
230824.jpg
1008 ms
230905-1.jpg
1078 ms
230905-2.jpg
573 ms
230905-3.jpg
667 ms
utf8
734 ms
icon.png
257 ms
layout.aspx
399 ms
layout.aspx
208 ms
20240424111935503ef6efbf0643c5bcccc9f765eb5e92.gif
1645 ms
20240424111949deadfa6129fa4003988ea23444dbc0af.gif
1286 ms
20231227163907e500d25842fe4864ab6350d7d38d1bdc.jpg
940 ms
2023122716392223e21e55f8164c01be8efff703a1e8c5.jpg
1730 ms
logo.png
296 ms
sprite.png
294 ms
nav-qrcode.jpg
303 ms
sprite.png
230 ms
bg-mask.png
1023 ms
navbtn.png
1905 ms
dwonbtnA.png
1019 ms
left-nav.jpg
1776 ms
zone.png
765 ms
20240430094652d624174988f0413185684f01bde3f8c9.jpg
1156 ms
2024042414491855d2c2887cec432398ea8ec35c785f33.jpg
715 ms
20240425092858b6a1b1d9b49f48e2844055a0fc619a9d.jpg
939 ms
20240424144944ec699feda4894247b59f579f0894bffe.jpg
1614 ms
20240417145416d8a7fe8ed87b4dd3a169e8edd551664a.jpg
1280 ms
20230712161205bf26df0e64a840e5ab6857d8c62ddb3e.jpg
2388 ms
20220309102228905e48b57091422285b920e737dafec0.jpg
1530 ms
bg-grey.jpg
1744 ms
2024043009445091ce5ff4707b471fb28e3a60420cf745.jpg
1563 ms
copyRightDataUTF8-240228.js
281 ms
tcg_download.js
281 ms
utf8
1505 ms
cs.jpg
316 ms
index.php
1114 ms
kartlist
1161 ms
kartevent
1192 ms
cls.jpg
297 ms
fs2.jpg
285 ms
xmxd.jpg
734 ms
car240425-title-1.png
817 ms
car240425-1.png
1360 ms
car240425-title-2.png
935 ms
car240425-2.png
1092 ms
car240328-title-1.png
1199 ms
car240328-1.png
1651 ms
car240328-title-2.png
1517 ms
car240328-2.png
2436 ms
car240314-title-1.png
2691 ms
car240314-1.png
1655 ms
role240502-title.png
2696 ms
role240502.png
2289 ms
role240425-title.png
2072 ms
role240425.png
1954 ms
role240411-title.png
2600 ms
role240411.png
2605 ms
role240404-title.png
2935 ms
role240404.png
3664 ms
role240328-title.png
2934 ms
role240328.png
4723 ms
map240425-title.png
4675 ms
map240425.png
3713 ms
map240328-title-1.png
3193 ms
map240328-1.png
3685 ms
map240328-title-2.png
3905 ms
map240328-2.png
3982 ms
map240328-title-3.png
3980 ms
map240328-3.png
4404 ms
map240328-title-4.png
4154 ms
nt_icon.png
537 ms
ta.js
742 ms
link_01.png
240 ms
link_02.png
243 ms
link_03.png
274 ms
link_04.png
840 ms
link_05.png
563 ms
map240328-4.png
3992 ms
item240502-title.png
3994 ms
item240502.png
3986 ms
item240425-title-1.png
4461 ms
item240425-1.png
4571 ms
item240425-title-2.png
4144 ms
item240425-2.png
4115 ms
dy1
932 ms
dy1
942 ms
dy1
958 ms
dy1
1068 ms
dy1
964 ms
dy1
689 ms
dy1
1103 ms
dy1
1181 ms
dy1
1474 ms
dy1
1375 ms
dy1
1377 ms
dy1
1478 ms
dy1
1567 ms
dy1
1743 ms
dy1
1633 ms
dy1
1786 ms
item240411-title-1.png
3801 ms
item240411-1.png
3746 ms
item240411-title-2.png
3903 ms
item240411-2.png
5142 ms
pet240425-title.png
4244 ms
pet240425.png
4993 ms
item240314-title-5.png
4105 ms
item240314-5.png
4291 ms
pet240208-title.png
3719 ms
pet240208.png
4193 ms
pet240201-title.png
4190 ms
pet240201.png
3544 ms
pet240104-title.png
4575 ms
pet240104.png
3653 ms
bg-data.png
5793 ms
car240425.jpg
3890 ms
popkart.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
popkart.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
popkart.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Popkart.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Popkart.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.
popkart.com
Open Graph description is not detected on the main page of Popkart. 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: