12.6 sec in total
1.1 sec
10.8 sec
670 ms
Click here to check amazing Citizen content for Japan. Otherwise, check out these important facts you probably never knew about citizen.jp
シチズンウオッチ オフィシャルサイトです。
Visit citizen.jpWe analyzed Citizen.jp page load time and found that the first response time was 1.1 sec and then it took 11.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
citizen.jp performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value12.0 s
0/100
25%
Value8.1 s
20/100
10%
Value660 ms
45/100
30%
Value0.613
10/100
15%
Value12.7 s
13/100
10%
1124 ms
347 ms
509 ms
1025 ms
540 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 98% of them (124 requests) were addressed to the original Citizen.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Citizen.jp.
Page size can be reduced by 210.6 kB (36%)
580.3 kB
369.6 kB
In fact, the total size of Citizen.jp main page is 580.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 318.0 kB which makes up the majority of the site volume.
Potential reduce by 19.4 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 19.4 kB or 74% of the original size.
Potential reduce by 27.8 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. Citizen images are well optimized though.
Potential reduce by 134.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 134.3 kB or 67% of the original size.
Potential reduce by 29.1 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. Citizen.jp needs all CSS files to be minified and compressed as it can save up to 29.1 kB or 84% of the original size.
Number of requests can be reduced by 46 (37%)
126
80
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Citizen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
citizen.jp
1124 ms
import.css
347 ms
skitter.styles.css
509 ms
jquery-1.6.4.min.js
1025 ms
default.js
540 ms
citIndexSwf.js
747 ms
topMenuSwf.js
761 ms
jquery.skitter.min.js
1266 ms
jquery.easing.1.3.js
1475 ms
jquery.animate-colors-min.js
1351 ms
swfAnimationConverter.min.js
1365 ms
top.js
1390 ms
top.js
1708 ms
jquery.cookie.js
1609 ms
divide_switch.js
1684 ms
basic.css
1541 ms
index.css
1768 ms
print.css
1489 ms
ga.js
193 ms
fbds.js
207 ms
bg_body01.jpg
386 ms
bg_body02.jpg
995 ms
bg_fn01.jpg
517 ms
logo_fn01.gif
393 ms
btn_fn01_def.gif
392 ms
btn_fn02_def.gif
391 ms
btn_fn03_def.gif
725 ms
btn_fn04_def.gif
728 ms
btn_fn05_def.gif
729 ms
btn_fn06_def.gif
764 ms
btn_fn07_def.gif
900 ms
btn_fn-search01.gif
1054 ms
atari_flash.gif
883 ms
head_fn01.gif
896 ms
head_fn01-01.gif
926 ms
bnr_fn-brand01_def.gif
1231 ms
head_fn01-02.gif
1135 ms
bnr_fn-brand07_def.gif
1339 ms
bnr_fn-brand03_def.gif
1397 ms
head_fn01-03.gif
1258 ms
bnr_fn-brand05_def.gif
1483 ms
head_fn01-04.gif
1473 ms
bnr_fn-brand10_def.gif
1573 ms
bnr_fn-brand10_01_def.gif
1752 ms
bnr_fn-brand10_02_def.gif
1862 ms
bnr_fn-brand10_03_def.gif
1893 ms
icn_close01_def.gif
1829 ms
bnr_fn-brand06_def.gif
2026 ms
head_fn02.gif
1887 ms
bnr_fn-brand08_def.gif
2242 ms
bnr_fn-brand09_def.gif
2357 ms
bg_main_frame.jpg
2379 ms
bg_fb-u06-bottom.gif
2391 ms
bg_fb-u06-top.gif
2245 ms
head_fb06.gif
2345 ms
btn_search_cat-gps.gif
2768 ms
__utm.gif
26 ms
btn_search_cat.gif
2576 ms
search_notes.gif
2523 ms
head_fb06-02.gif
2514 ms
btn_search_item.gif
2684 ms
itemlist_14_def.gif
2431 ms
itemlist_13_def.gif
2533 ms
itemlist_03_def.gif
2554 ms
itemlist_04_def.gif
2549 ms
itemlist_05_def.gif
2552 ms
itemlist_06_def.gif
2418 ms
itemlist_07_def.gif
2419 ms
itemlist_08_def.gif
2524 ms
itemlist_09_def.gif
2562 ms
itemlist_10_def.gif
2573 ms
itemlist_11_def.gif
2542 ms
bg_fb-u03-01_top.gif
2337 ms
bg_fb-u03-01_btm.gif
2327 ms
head_fb02.gif
2473 ms
bullet_link_listpage.gif
2430 ms
bg_fb-head02.gif
2553 ms
head_fb08.gif
2342 ms
line_fb-u05-01_h.gif
2333 ms
head_fb04-04.gif
2324 ms
pic_satellitewave-f100.jpg
2879 ms
special_radius_frame.png
2294 ms
bullet_link_strong.gif
2293 ms
pic_attesa_gps.jpg
2826 ms
pic_xc.jpg
2827 ms
head_fb04-03.gif
2296 ms
pho_special_sub_betterstartsnow.jpg
2424 ms
pho_special_sub_20140327.jpg
2591 ms
pho_special_sub_20150511.jpg
2618 ms
pho_special_sub_20130530_2.jpg
3005 ms
head_fb04.gif
2616 ms
head_fb04-01.gif
2668 ms
icn_fb-rss01.gif
2370 ms
pho_product_20150610.jpg
2768 ms
pho_product_20160107.jpg
2766 ms
pho_product_20160210.jpg
2729 ms
pho_product_20160203.jpg
2962 ms
head_fb04-02.gif
2534 ms
bg_fb-u05-type02_top.gif
2692 ms
bg_fb-u05-type02_btm.gif
2696 ms
bg_fb-u05-type03_top.gif
2736 ms
bg_fb-u05-type03_btm.gif
2724 ms
bg_footer01.jpg
2715 ms
bullet_link_footer.gif
2854 ms
copyright.gif
2716 ms
txt_catchcopy.gif
3672 ms
bnr_fn-brand01_cur.gif
2695 ms
bnr_fn-brand07_cur.gif
2723 ms
bnr_fn-brand03_cur.gif
2719 ms
bnr_fn-brand05_cur.gif
2839 ms
bnr_fn-brand10_cur.gif
2714 ms
icn_close01_cur.gif
2735 ms
bnr_fn-brand06_cur.gif
2708 ms
bnr_fn-brand08_cur.gif
2902 ms
bnr_fn-brand09_cur.gif
2989 ms
itemlist_14_cur.gif
2853 ms
itemlist_13_cur.gif
2715 ms
itemlist_03_cur.gif
2709 ms
itemlist_04_cur.gif
2730 ms
itemlist_05_cur.gif
2502 ms
itemlist_06_cur.gif
2513 ms
itemlist_07_cur.gif
2483 ms
itemlist_08_cur.gif
2500 ms
itemlist_09_cur.gif
2535 ms
itemlist_10_cur.gif
2461 ms
itemlist_11_cur.gif
2469 ms
bg_splash_blue.jpg
2481 ms
citizen.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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
citizen.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
General
Impact
Issue
Detected JavaScript libraries
citizen.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Citizen.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Citizen.jp 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.
citizen.jp
Open Graph description is not detected on the main page of Citizen. 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: