6.6 sec in total
453 ms
5.7 sec
492 ms
Welcome to eetimes.jp homepage info - get ready to check EE Times best content for Japan right away, or after learning these important things about eetimes.jp
エレクトロニクスに携わる方々に向けた総合情報サイト。世界各地の半導体や電子部品、PC、家電、スマートフォン、IoT、自動車、産業機器などに関する速報やコラム、技術解説を毎日提供しています。
Visit eetimes.jpWe analyzed Eetimes.jp page load time and found that the first response time was 453 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
eetimes.jp performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value9.0 s
1/100
25%
Value9.5 s
11/100
10%
Value1,690 ms
11/100
30%
Value0
100/100
15%
Value14.3 s
9/100
10%
453 ms
292 ms
300 ms
303 ms
313 ms
Our browser made a total of 162 requests to load all elements on the main page. We found that 20% of them (32 requests) were addressed to the original Eetimes.jp, 37% (60 requests) were made to Image.itmedia.co.jp and 14% (23 requests) were made to Dlv.itmedia.jp. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Image.itmedia.co.jp.
Page size can be reduced by 512.1 kB (26%)
1.9 MB
1.4 MB
In fact, the total size of Eetimes.jp main page is 1.9 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.3 MB which makes up the majority of the site volume.
Potential reduce by 107.3 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 107.3 kB or 82% of the original size.
Potential reduce by 35.7 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. EE Times images are well optimized though.
Potential reduce by 299.2 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 299.2 kB or 78% of the original size.
Potential reduce by 69.9 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. Eetimes.jp needs all CSS files to be minified and compressed as it can save up to 69.9 kB or 84% of the original size.
Number of requests can be reduced by 72 (45%)
160
88
The browser has sent 160 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EE Times. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
eetimes.jp
453 ms
movePC2SP.js
292 ms
base.css
300 ms
ad.css
303 ms
top.css
313 ms
prettify.css
309 ms
prettify.js
469 ms
jquery.min.js
35 ms
fpcookie
308 ms
scAccount.js
313 ms
adRequest.js
434 ms
scRequest.js
438 ms
base.js
594 ms
ad.js
465 ms
top.js
469 ms
base.js
582 ms
ad.js
584 ms
top.js
622 ms
platform.js
98 ms
jsapi
28 ms
list.json
618 ms
list.json
620 ms
list.json
725 ms
list.json
725 ms
list.json
737 ms
list.json
772 ms
list.json
773 ms
list.json
777 ms
list.json
872 ms
list.json
875 ms
parts_monoist_features.json
892 ms
masterBodyEnd.js
802 ms
smartPhoneHeadLink.js
803 ms
s_code.js
809 ms
base.css
735 ms
ad.css
735 ms
top.css
745 ms
v1
306 ms
v1
152 ms
240_news044.jpg
595 ms
top_news033.jpg
445 ms
top_news041.jpg
306 ms
top_news069.jpg
308 ms
240_news026.jpg
455 ms
240_news031.jpg
609 ms
240_news092.jpg
601 ms
240_news008.jpg
600 ms
240_news054.jpg
737 ms
240_news102.jpg
605 ms
parts_top_features_icon_1_1443443109.jpg
739 ms
news032.jpg
749 ms
news084.jpg
751 ms
news071.jpg
755 ms
news035.jpg
761 ms
news045.jpg
886 ms
news033.jpg
894 ms
news069.jpg
896 ms
news103.jpg
898 ms
news037.jpg
904 ms
news054.jpg
912 ms
news038.jpg
1034 ms
top_news049.jpg
1043 ms
top_news031.jpg
1048 ms
top_news102.jpg
1079 ms
top_news045.jpg
1079 ms
top_news069.jpg
1080 ms
top_news036.jpg
1182 ms
top_news033.jpg
1191 ms
top_news071.jpg
1195 ms
top_news023.jpg
1199 ms
top_news026.jpg
1208 ms
170_itmedia_bgw.gif
1217 ms
v1
153 ms
itmidNav_bg.gif
307 ms
v1
152 ms
v1
152 ms
itmidNav_NewEntry.gif
153 ms
v1
152 ms
itmidNav_MyPage.gif
154 ms
sdk.js
23 ms
icon_facebook.png
560 ms
icon_twitter.png
570 ms
icon_feed.png
576 ms
icon_mailmag.png
579 ms
80_mn_bgw.gif
589 ms
80_ee_bgw2.gif
601 ms
80_edn_bgw.gif
705 ms
80_smartjapan_bgw.gif
716 ms
library_logo_80.png
722 ms
modelabo_logo_80.png
726 ms
170_ee_bgw.gif
735 ms
v1
152 ms
58 ms
xd_arbiter.php
36 ms
xd_arbiter.php
41 ms
728_90.gif
303 ms
cms_pr.gif
581 ms
eetimes.js
70 ms
13 ms
default+ja.css
4 ms
default.css
16 ms
default+ja.I.js
9 ms
default.css
55 ms
popin_read-min.js
49 ms
v1
151 ms
adtxt_bg.gif
177 ms
v1
153 ms
v1
153 ms
80x60mrj.jpg
154 ms
v1
151 ms
logo.jpg
300 ms
logo.jpg
299 ms
logo.jpg
304 ms
logo.jpg
442 ms
v1
153 ms
keysight_5Gproduct_300x300_eeTimesJapan.gif
300 ms
v1
152 ms
v1
151 ms
B8807270.119397557;sz=300x250;ord=1456758741
26 ms
video_Nootbaar_LT8602_300x250_jp.jpg
6 ms
lidar.js
11 ms
sbhK2lTE.js
7 ms
v1
152 ms
cTrvNaRi.html
9 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
8 ms
B9496151.129045911;sz=300x300;click=;ord=1456758741;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=
44 ms
300x300_EFM32_Pearl-Jade_JP.jpg
49 ms
v1
159 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
25 ms
v1
153 ms
8060_01.gif
155 ms
80x60.jpg
149 ms
80x60_bridgestone.jpg
294 ms
icon02.jpg
440 ms
80x60a.jpg
299 ms
80.jpg
301 ms
icon_80_60_2_02.jpg
301 ms
icon_ibm.jpg
303 ms
v1
153 ms
colBox_rank2.gif
153 ms
top_news035.jpg
151 ms
top_news106.jpg
153 ms
top_news019.jpg
298 ms
top_news039.jpg
154 ms
top_news026.jpg
150 ms
top_news106.jpg
297 ms
top_news084.jpg
298 ms
v1
157 ms
v1
152 ms
cradle2.jpg
151 ms
60x45b.jpg
151 ms
v1
151 ms
v1
152 ms
colBoxHead_bgmynavi.gif
152 ms
ulli_book0.gif
151 ms
widgets.js
91 ms
170_itmedia_bgb.gif
155 ms
s58141026075463
79 ms
v1
151 ms
fbevents.js
29 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
125 ms
3 ms
eetimes.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.
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.
eetimes.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
eetimes.jp SEO score
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
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eetimes.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 Eetimes.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.
eetimes.jp
Open Graph data is detected on the main page of EE Times. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: