15.4 sec in total
733 ms
14.4 sec
294 ms
Welcome to jeecard.com homepage info - get ready to check Jeecard best content for Taiwan right away, or after learning these important things about jeecard.com
大型中文游戏,提供最新网络游戏、手机游戏、单机游戏、电视游戏、网页游戏资讯,好玩的游戏排行、游戏专区、游戏攻略等服务,焦耳游戏网
Visit jeecard.comWe analyzed Jeecard.com page load time and found that the first response time was 733 ms and then it took 14.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
jeecard.com performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value3.0 s
78/100
25%
Value4.9 s
65/100
10%
Value1,210 ms
20/100
30%
Value0.029
100/100
15%
Value3.9 s
88/100
10%
733 ms
477 ms
1276 ms
3634 ms
2577 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 83% of them (115 requests) were addressed to the original Jeecard.com, 7% (10 requests) were made to Static.xx.fbcdn.net and 2% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Jeecard.com.
Page size can be reduced by 910.2 kB (38%)
2.4 MB
1.5 MB
In fact, the total size of Jeecard.com main page is 2.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. 65% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 43.5 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 13.7 kB, which is 25% 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 43.5 kB or 81% of the original size.
Potential reduce by 188.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. Obviously, Jeecard needs image optimization as it can save up to 188.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 533.9 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 533.9 kB or 72% of the original size.
Potential reduce by 144.4 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. Jeecard.com needs all CSS files to be minified and compressed as it can save up to 144.4 kB or 85% of the original size.
Number of requests can be reduced by 33 (24%)
136
103
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jeecard. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
jeecard.com
733 ms
477 ms
jquery.js
1276 ms
jquery.tools.min.js
3634 ms
jquery-ui-1.10.3.custom.min.js
2577 ms
web_function.js
433 ms
jquery.pngFix.pack.js
448 ms
jquery.pngFix.js
454 ms
jquery.block.js
1085 ms
jquery.defaultvalue.js
889 ms
plusone.js
59 ms
jquery.ui.widget.js
1133 ms
jquery.iframe-transport.js
1319 ms
jquery.fileupload_n.js
2006 ms
selectivizr.js
1776 ms
jquery.custom_slide_list.js
2573 ms
all.js
26 ms
font.js
1962 ms
jquery_cookie.js
2206 ms
css.php
2614 ms
font.css
2459 ms
slick.css
2659 ms
slick.js
3533 ms
facebook_login.js
3001 ms
cb=gapi.loaded_0
34 ms
20160302080118509.jpeg
3177 ms
20160229095458674.jpeg
4300 ms
20160217105314957.jpeg
1926 ms
pro_top1.png
431 ms
20151020122311112.png
434 ms
20140423124409900.png
668 ms
pro_top2.png
893 ms
20160125074540807.jpeg
1118 ms
20160125074537240.jpeg
1124 ms
pro_top3.png
1324 ms
20160125074529428.jpeg
1761 ms
20160125074525881.jpeg
1798 ms
20140423124706326.png
1751 ms
20140423124707383.png
2193 ms
20140423124858581.png
2205 ms
20140423124859678.png
2230 ms
20140423125743780.png
2356 ms
20140423125743961.png
2652 ms
20140423125648259.png
2660 ms
20140423125648757.png
2657 ms
20140423125409882.png
2808 ms
20140423125409561.png
3089 ms
20140423124453299.png
3110 ms
20140423124454446.png
3119 ms
20140423124523222.png
3238 ms
20140423124524741.png
3542 ms
20140423125045887.png
3539 ms
20140423125045307.png
3603 ms
20140423125122310.png
3669 ms
20140423125123749.png
3979 ms
20140423125149321.png
3990 ms
20140423125149195.png
4024 ms
20140423125211513.png
4098 ms
20140423125212256.png
4408 ms
20140423125245181.png
4420 ms
20140423125245349.png
4458 ms
analytics.js
14 ms
collect
42 ms
163 ms
ping
167 ms
collect
81 ms
xd_arbiter.php
44 ms
xd_arbiter.php
69 ms
20140423125346731.png
4116 ms
20140423125347510.png
4131 ms
like_box.php
193 ms
4P2PlI2Xj1w.css
40 ms
edHKvLIRWb_.css
43 ms
q68gy-v_YMF.js
50 ms
ehA1CqzHyzE.js
62 ms
0wM5s1Khldu.js
61 ms
1bNoFZUdlYZ.js
60 ms
20140423125513743.png
4071 ms
12274433_1662042574038899_1875866913843668672_n.png
32 ms
wL6VQj7Ab77.png
6 ms
s7jcwEQH7Sx.png
4 ms
I6-MnjEovm5.js
6 ms
pQrUxxo5oQp.js
8 ms
20140423125513276.png
3967 ms
20140423125535988.png
3732 ms
20140423125535835.png
3766 ms
20140423125628125.png
3662 ms
20140423125628778.png
3234 ms
20140703104621444.png
3418 ms
20140703104613599.png
3504 ms
20140423125805459.png
3397 ms
20140423125805731.png
3126 ms
20140423125842954.png
3227 ms
20140423125842591.png
3423 ms
20140423125919771.png
3253 ms
20140423125920691.png
3088 ms
title_classified.png
3086 ms
news_bg.png
3090 ms
title_prepaid.png
3052 ms
prepaid_pic.png
3378 ms
about_1_10.png
2965 ms
index_step_1.png
3047 ms
index_step_2.png
2998 ms
index_step_3.png
2957 ms
index_step_4.png
2749 ms
index_step_5.png
2961 ms
amy_index_9_1_footer_03.jpg
3420 ms
card_list_1_03_s.png
3182 ms
B_card_list_1_06.jpg
2862 ms
B_card_list_1_08.jpg
2981 ms
papper_03.png
2901 ms
pappp_03.png
2834 ms
pappp_07.png
2974 ms
pappp_06.png
2896 ms
card_list_03.jpg
2935 ms
btn_2.png
2929 ms
car_icon.png
2884 ms
wait_bg.png
2892 ms
like_list.png
2963 ms
B_card_list_1_3.jpg
3140 ms
slider_down_bottom.png
2929 ms
B_card_list_1_5.jpg
3177 ms
B_card_list_1_07.jpg
3135 ms
B_card_list_1_09.jpg
3153 ms
title_pro.png
2951 ms
p_btn.png
2953 ms
btn_more.png
3099 ms
icon_3.png
3174 ms
footer_icon_1.png
3129 ms
footer_icon_2.png
2948 ms
footer_icon_3.png
2926 ms
footer_icon_4.png
2941 ms
banner_left.png
3100 ms
banner_right.png
3171 ms
dot_s.png
3131 ms
dot_o.png
2913 ms
colorbox.css
218 ms
sdk.js
4 ms
widget_v2.135.js
176 ms
jeecard.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
<frame> or <iframe> elements do not have a title
jeecard.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
jeecard.com SEO score
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 uses legible font sizes
![]()
ZH
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jeecard.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 Jeecard.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.
jeecard.com
Open Graph data is detected on the main page of Jeecard. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: