9 sec in total
1.6 sec
7.2 sec
304 ms
Click here to check amazing Epoch content for Japan. Otherwise, check out these important facts you probably never knew about epoch.jp
シルバニアファミリーなどの製品情報や企業情報を掲載。シルバニアファミリーや野球盤などの玩具・ジグソーパズル・トレーディングスポーツカードなどの製造・販売を行う、株式会社エポック社の公式サイトです。
Visit epoch.jpWe analyzed Epoch.jp page load time and found that the first response time was 1.6 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
epoch.jp performance score
name
value
score
weighting
Value8.8 s
0/100
10%
Value45.7 s
0/100
25%
Value21.0 s
0/100
10%
Value1,000 ms
27/100
30%
Value0.134
80/100
15%
Value31.0 s
0/100
10%
1561 ms
666 ms
336 ms
533 ms
712 ms
Our browser made a total of 171 requests to load all elements on the main page. We found that 89% of them (153 requests) were addressed to the original Epoch.jp, 2% (3 requests) were made to S.ytimg.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Epoch.jp.
Page size can be reduced by 595.0 kB (72%)
825.0 kB
230.0 kB
In fact, the total size of Epoch.jp main page is 825.0 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. 55% of websites need less resources to load. Javascripts take 399.6 kB which makes up the majority of the site volume.
Potential reduce by 95.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 95.9 kB or 89% of the original size.
Potential reduce by 5.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. Obviously, Epoch needs image optimization as it can save up to 5.8 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 256.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 256.7 kB or 64% of the original size.
Potential reduce by 236.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. Epoch.jp needs all CSS files to be minified and compressed as it can save up to 236.6 kB or 83% of the original size.
Number of requests can be reduced by 28 (17%)
167
139
The browser has sent 167 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Epoch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
epoch.jp
1561 ms
common.css
666 ms
globalMenu.css
336 ms
text.css
533 ms
index.css
712 ms
iframe.css
567 ms
swfobject_modified.js
918 ms
rollover.js
886 ms
smoothscroll.js
755 ms
jquery-1.4.4.min.js
1495 ms
jquery.cookie.js
887 ms
imageTabs.js
944 ms
agent_switcher.js
1063 ms
bg_body.gif
172 ms
spacer.gif
169 ms
bnr_2012toyshow.gif
197 ms
bnr_pressrelease.gif
189 ms
cm.gif
189 ms
important.gif
170 ms
top_bnr_1.gif
336 ms
top_bnr_2.gif
505 ms
top_bnr_3.gif
344 ms
top_bnr_4.gif
584 ms
category01.gif
761 ms
category06.gif
949 ms
category07.gif
503 ms
category09.gif
686 ms
category12.gif
672 ms
allitem.gif
672 ms
bn_sf.gif
977 ms
bn_aqua.gif
839 ms
bn_whip.gif
1042 ms
bn_anayuki.jpg
857 ms
bn_sw.gif
938 ms
yakyuban2015.gif
1005 ms
soccer.gif
1029 ms
bn_mario.gif
1116 ms
bn_doraemon.gif
1135 ms
bn_jigsaw.gif
1153 ms
bn_puzzle_kikou.gif
1171 ms
bu_lassen.gif
1208 ms
bn_capsule.gif
1208 ms
bn_trcard.gif
1506 ms
bn_variety.gif
1323 ms
bn_acce.gif
1507 ms
bn_darts.gif
1337 ms
bn_tetudo.gif
1372 ms
bn_kt_aiueo.gif
1539 ms
gtm.js
108 ms
NmKwHCxxCAs
164 ms
news.php
1565 ms
analytics.js
26 ms
conversion_async.js
15 ms
s_retargeting.js
573 ms
43 ms
collect
13 ms
collect
66 ms
bn_kt_pc.gif
1346 ms
bn_appli.gif
1383 ms
bn_dora_taiko_machine.gif
1733 ms
www-embed-player-vflZsBgOl.css
76 ms
www-embed-player.js
104 ms
base.js
178 ms
50 ms
bn_dora_puzzlepanic.gif
1493 ms
bn_dora_nihon5.gif
1683 ms
bn_dora_himitsu.gif
1520 ms
bn_dora_guru.gif
1388 ms
bn_dorahockey.gif
1401 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
14 ms
ad_status.js
46 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
66 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
77 ms
bn_dora_cubepzl.gif
1344 ms
bn_dora_royal50.gif
1380 ms
bn_dora_shogiigo.gif
1313 ms
bn_dora_nihon4.gif
1262 ms
bn_dora_darake.gif
1342 ms
bn_block_tower.gif
1363 ms
bi.js
494 ms
bn_dora_taiko.gif
1292 ms
bn_dora_aiueo.gif
1229 ms
bn_mario_aqs44.gif
1402 ms
bn_mario_aq234.gif
1184 ms
bn_mario_daiboukenkoopa.gif
1235 ms
bn_mario_airhockey_ws.gif
1249 ms
bn_mario_gp_race.gif
1213 ms
bn_mario_coin_adventure2.gif
1210 ms
bn_mario_daiboukengame.gif
1272 ms
bn_mario_daimeirogame.gif
1231 ms
bn_mario8_wloop.gif
1250 ms
bn_mario_luckycoin.gif
1250 ms
bn_mario_jamp.gif
1240 ms
327 ms
bn_mario8_loop.gif
1403 ms
bn_coinrush.gif
1291 ms
bn_sr.gif
1190 ms
bn_kuchu.gif
1211 ms
bn_oshiro.gif
1207 ms
bn_koopa.gif
1075 ms
bn_mario_gur.gif
1185 ms
bn_mario_kinoko.gif
1174 ms
bn_mario_wii_waku.gif
1178 ms
bn_daimeiro.gif
1215 ms
bn_mario_reversi10.gif
1183 ms
bn_mario_airhockey.gif
1292 ms
bn_mario_gura.gif
1139 ms
bn_balancegame_tg.gif
1162 ms
bn_balancegame_ug.gif
1149 ms
bn_mario_daibouken.gif
1086 ms
bn_mario_hockey.gif
1076 ms
bn_mario_slot.gif
1137 ms
bn_mario_coinjr.gif
1181 ms
bn_sw_gj.gif
1158 ms
bn_sw_vssa.gif
1172 ms
bn_sw_fah.gif
1108 ms
bn_anayuki_ice.gif
1277 ms
bn_anayuki_dond.gif
1136 ms
bn_dm_hjc.gif
1159 ms
bn_dm_shizue.gif
1141 ms
bn_dm_tanukiti.gif
1096 ms
bn_hunter.gif
1082 ms
bn_panda.gif
1129 ms
bn_ice_ex24.gif
1154 ms
bn_ice_plus.gif
1195 ms
bn_dond_sp24.gif
1136 ms
bn_dod.gif
1131 ms
bn_android_sf.gif
1117 ms
bn_iphone_sf.gif
1118 ms
bn_iphone_aquabeadsart2.gif
1149 ms
bn_iphone_bbg.gif
1120 ms
bn_iphone_acce.gif
1127 ms
bn_iphone_ice.gif
1104 ms
bn_iphone_dond.gif
1098 ms
bn_iphone_mh.gif
1105 ms
category06_s.gif
1116 ms
category07_s.gif
1111 ms
category09_s.gif
1140 ms
category12_s.gif
1115 ms
btn_pagetop_green_n.gif
1102 ms
original_bn.gif
1096 ms
epoch.gif
1045 ms
copyright_bk.gif
1082 ms
bg_header.png
1134 ms
head.gif
1262 ms
home.gif
1082 ms
sitemap.gif
1069 ms
gmenu08.png
1044 ms
gmenu01.png
1080 ms
gmenu02.png
1138 ms
gmenu03.png
1089 ms
gmenu04.png
1094 ms
gmenu05.png
1043 ms
gmenu06.png
1084 ms
gmenu07.png
1096 ms
flash_top.gif
1095 ms
flash_main.gif
1102 ms
flash_btm.gif
1070 ms
whatsnew.gif
1042 ms
bg_top.gif
1088 ms
bg_main.gif
1078 ms
bg_categorymenu.gif
1095 ms
itembox_top.gif
1093 ms
itembox_main.gif
1061 ms
itembox_btm.gif
1070 ms
dot.gif
1091 ms
bg_btm.gif
1074 ms
bg_footer.gif
1259 ms
category01_on.gif
1241 ms
icon.gif
1247 ms
btn_pagetop_green_o.gif
174 ms
epoch.jp 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.
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
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.
epoch.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
epoch.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 Epoch.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 Epoch.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.
epoch.jp
Open Graph description is not detected on the main page of Epoch. 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: