4.6 sec in total
932 ms
3.3 sec
359 ms
Welcome to cncn.jp homepage info - get ready to check Cncn best content for Japan right away, or after learning these important things about cncn.jp
チケットはCNプレイガイドチケットサイトでご予約を!全国のコンサート・野球・サッカー等のスポーツ・演劇・ステージ・イベント・映画などのチケットの先行予約やチケット発売情報からイベントツアー(旅行)まで情報公開中!
Visit cncn.jpWe analyzed Cncn.jp page load time and found that the first response time was 932 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
cncn.jp performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value10.3 s
0/100
25%
Value9.9 s
10/100
10%
Value190 ms
91/100
30%
Value0.077
95/100
15%
Value11.0 s
21/100
10%
932 ms
320 ms
330 ms
655 ms
339 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 64% of them (74 requests) were addressed to the original Cncn.jp, 9% (10 requests) were made to Abs.twimg.com and 5% (6 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cnplayguide.com.
Page size can be reduced by 265.8 kB (16%)
1.7 MB
1.4 MB
In fact, the total size of Cncn.jp main page is 1.7 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 48.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 17.4 kB, which is 29% 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 48.5 kB or 82% of the original size.
Potential reduce by 180.0 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, Cncn needs image optimization as it can save up to 180.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 13.5 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 13.5 kB or 45% of the original size.
Potential reduce by 23.8 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. Cncn.jp needs all CSS files to be minified and compressed as it can save up to 23.8 kB or 86% of the original size.
Number of requests can be reduced by 33 (29%)
114
81
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cncn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
cncn.jp
932 ms
style_n.css
320 ms
list.css
330 ms
top.css
655 ms
text_moto.css
339 ms
ecl_new.js
749 ms
Search.js
476 ms
flash.js
350 ms
sp_check_img.php
352 ms
fm_chokuhan.gif
857 ms
bnr_wmf2016right.gif
854 ms
bnr_ak-69fm.gif
854 ms
bar_bmp2_6_337.jpg
1272 ms
tel3.gif
781 ms
aa_shadw.png
153 ms
aa_header.jpg
311 ms
aa_header_logo.jpg
166 ms
aa_nav00.jpg
192 ms
aa_nav01.jpg
336 ms
aa_nav02.jpg
164 ms
aa_nav03.jpg
305 ms
aa_nav04.jpg
330 ms
aa_nav05.jpg
490 ms
aa_nav06.jpg
377 ms
aa_serch.jpg
473 ms
btn_serch.gif
477 ms
btn_serch_more.jpg
490 ms
btn_top_signin.gif
498 ms
aa_re00.jpg
565 ms
CNI23511_s.jpg
628 ms
CNI10003_s.jpg
634 ms
lin_gray.gif
649 ms
CNK59510_s.jpg
656 ms
ico010001.gif
662 ms
CNI13443_s.jpg
748 ms
CNI13765_s.jpg
777 ms
CNI14440_s.jpg
787 ms
CNI12900_s.jpg
838 ms
CNI12497_s.jpg
839 ms
CNK59521_s.jpg
841 ms
CNK58855_s.jpg
933 ms
CNK59132_s.jpg
927 ms
CNK59073_s.jpg
943 ms
marines_s.gif
977 ms
lions_s.jpg
981 ms
top_fm.gif
990 ms
top_asahi.gif
1077 ms
shim.gif
1116 ms
aa_pr02.jpg
1099 ms
bar_totem_s.jpg
1111 ms
jquery.min.js
8 ms
widgets.js
85 ms
ajs.php
341 ms
bar_kageki_160.gif
1003 ms
bar_yogaku_s.gif
1007 ms
bar_dinnershow_s.gif
1076 ms
bar_soccer_160.gif
1164 ms
bar_baseball_160.gif
1059 ms
aa_pr03.jpg
1055 ms
bar_big.jpg
1033 ms
bar_tas.jpg
1030 ms
biginter_logo_cn.jpg
1045 ms
2135093_1.gif
666 ms
1st.js
341 ms
imp
375 ms
imp
377 ms
lg.php
161 ms
ski.gif
961 ms
bar_OTM2.gif
1044 ms
ACPC_yk.gif
1052 ms
bar_saiyou_s.gif
1035 ms
bar_tabikatsu.png
1024 ms
aa_welcom.jpg
979 ms
aa_right01_btn.jpg
961 ms
aa_right02_btn_on.jpg
1046 ms
aa_right03_btn.jpg
1031 ms
aa_right04_btn.jpg
1031 ms
aa_new01.jpg
1065 ms
aa_new02.jpg
946 ms
aa_janl00.jpg
966 ms
aa_janl01.jpg
1052 ms
i_mark.png
172 ms
adsby.png
336 ms
segmentation.js
23 ms
timeline.5d8406ab2e764a871ed41bd9aa0b693f.js
128 ms
ico_tri_r.gif
1001 ms
aa_janl02.jpg
1012 ms
aa_janl03.jpg
1004 ms
cnt
321 ms
aa_janl04.jpg
983 ms
aa_janl05.jpg
965 ms
aa_snav00.jpg
1058 ms
syndication
87 ms
522319216637014017
225 ms
ico_tri_b.gif
1019 ms
1f3b6.png
28 ms
2728.png
21 ms
203c.png
17 ms
1f3b5.png
20 ms
1f4ab.png
22 ms
2744.png
22 ms
1f3a4.png
21 ms
1f4fa.png
24 ms
1f389.png
23 ms
1f382.png
21 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
31 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
132 ms
TW-logo_normal.jpeg
101 ms
CeneMcrWAAAtjv-.jpg:large
155 ms
CemnYxUXIAU_49X.jpg:large
104 ms
CemW5_9WIAI7WUv.jpg:large
166 ms
CeYvqL8UEAA_yGz.jpg:small
156 ms
CeYtCc8VIAATOPp.jpg
228 ms
jot
22 ms
beacon.html
10 ms
cncn.jp 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
cncn.jp 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
cncn.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 uses legible font sizes
Tap targets are not sized appropriately
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cncn.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Cncn.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
cncn.jp
Open Graph description is not detected on the main page of Cncn. 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: