5.4 sec in total
1.3 sec
3.7 sec
358 ms
Welcome to prtimes.jp homepage info - get ready to check PR TIMES best content for Japan right away, or after learning these important things about prtimes.jp
プレスリリースをPR TIMESで配信して、効果的なPRを実現。上場企業の54.5%(2,169/3,978社)が利用する現在シェアNo.1のプレスリリース配信代行サービス。話題のベンチャー~グローバル企業のニュースリリースが集まる生活者も要注目のサイトです。プレスリリースの受信は無料です。
Visit prtimes.jpWe analyzed Prtimes.jp page load time and found that the first response time was 1.3 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
prtimes.jp performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value3.9 s
52/100
25%
Value4.8 s
68/100
10%
Value990 ms
28/100
30%
Value0
100/100
15%
Value11.5 s
18/100
10%
1291 ms
789 ms
504 ms
38 ms
346 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 52% of them (66 requests) were addressed to the original Prtimes.jp, 6% (8 requests) were made to I.ytimg.com and 6% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Prtimes.jp.
Page size can be reduced by 1.9 MB (58%)
3.2 MB
1.4 MB
In fact, the total size of Prtimes.jp main page is 3.2 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. 60% of websites need less resources to load. CSS take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 133.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. This page needs HTML code to be minified as it can gain 19.8 kB, which is 12% 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 133.9 kB or 83% of the original size.
Potential reduce by 132.2 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, PR TIMES needs image optimization as it can save up to 132.2 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 682.4 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 682.4 kB or 67% of the original size.
Potential reduce by 916.5 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. Prtimes.jp needs all CSS files to be minified and compressed as it can save up to 916.5 kB or 88% of the original size.
Number of requests can be reduced by 49 (40%)
122
73
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PR 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 40 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
prtimes.jp
1291 ms
style.css
789 ms
modernizr.custom.js
504 ms
outbrain.js
38 ms
googleana.js
346 ms
googleana2.js
360 ms
bookmark_button.js
367 ms
conversion.js
24 ms
jquery.min.js
44 ms
jquery-ui-1.10.4.min.js
690 ms
jquery.transit.min.js
192 ms
widgets.js
4 ms
platform.js
71 ms
jquery.cookie.js
216 ms
common.js
717 ms
common.js
362 ms
jquery.flexslider-min.js
358 ms
iframe_api
45 ms
index.js
396 ms
release.js
687 ms
common_parts.js
689 ms
css
52 ms
analytics.js
165 ms
195339.js
168 ms
mqdefault.jpg
152 ms
button-only@2x.png
194 ms
mqdefault.jpg
143 ms
mqdefault.jpg
140 ms
mqdefault.jpg
140 ms
mqdefault.jpg
140 ms
mqdefault.jpg
141 ms
mqdefault.jpg
141 ms
mqdefault.jpg
142 ms
logo.png
178 ms
icon.png
163 ms
still7.jpg
998 ms
heading.png
192 ms
d8859-300-114568-1.jpg
192 ms
d16946-3-105816-1.jpg
404 ms
d15600-2-729855-0.jpg
402 ms
d12501-19-541667-1.jpg
402 ms
d9999-41-424059-1.jpg
402 ms
d4741-20-689651-0.jpg
401 ms
d84-550-629727-5.jpg
608 ms
d15536-9-915856-3.jpg
609 ms
d12784-14-760208-1.jpg
599 ms
d17006-3-408036-3.jpeg
608 ms
d17276-3-483500-1.jpg
607 ms
d11770-29-788589-3.jpg
817 ms
d17718-1-726226-2.jpg
823 ms
d2703-624-368191-1.jpg
824 ms
118x78.png
824 ms
banner_top-service.png
829 ms
top_bnr_su_free.png
1207 ms
d15425-6-705783-1.jpg
940 ms
d84-550-629727-5.jpg
941 ms
d7006-2162-599444-2.jpg
953 ms
d4367-342-305050-1.jpg
959 ms
d17874-1-762222-1.jpg
1104 ms
d7303-319-292756-1.jpg
1106 ms
d10721-6-162859-0.jpg
1140 ms
d15834-11-106290-1.jpg
1143 ms
d17319-3-545152-0.jpg
1163 ms
68x45.png
1270 ms
d2360-611-607787-3.jpg
1276 ms
d7006-2151-935509-0.jpg
1194 ms
d112-609-121599-2.jpg
1199 ms
d5816-104-294692-2.jpg
1201 ms
collect
30 ms
d13649-8-830044-1.jpg
1208 ms
d4829-819-194110-1.jpg
1283 ms
63 ms
472 ms
d5720-197-362789-3.jpg
1266 ms
collect
191 ms
d5816-105-569131-1.jpg
1319 ms
d5358-9-119299-0.jpg
1328 ms
184 ms
cb=gapi.loaded_0
199 ms
cb=gapi.loaded_1
217 ms
fastbutton
306 ms
like.php
267 ms
platform.js
242 ms
sdk.js
296 ms
www-widgetapi.js
217 ms
pta.js
540 ms
bi.js
646 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
72 ms
d10908-65-396623-0.jpg
1107 ms
d6612-46-399835-19.jpg
1124 ms
d7396-41-435563-1.jpg
1214 ms
d11353-12-557982-0.jpg
1221 ms
d5720-196-214060-1.jpg
1278 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
36 ms
postmessageRelay
52 ms
DSpd5N1WKUg
94 ms
-1cfYrhulAt.js
351 ms
LVx-xkvaJ0b.png
385 ms
api.js
76 ms
core:rpc:shindig.random:shindig.sha1.js
157 ms
2536007149-postmessagerelay.js
76 ms
cb=gapi.loaded_0
88 ms
cb=gapi.loaded_1
72 ms
grlryt2bdKIyfMSOhzd1eA.woff
158 ms
www-embed-player-vflZsBgOl.css
70 ms
www-embed-player.js
109 ms
base.js
149 ms
d5738-136-446148-1.jpg
1092 ms
d12840-6-307256-1.jpg
1095 ms
d11414-245-306598-3.jpg
1074 ms
d5069-318-801163-1.jpg
1176 ms
89 ms
d8880-27-102649-0.jpg
1172 ms
jot
182 ms
xd_arbiter.php
189 ms
xd_arbiter.php
312 ms
reset.css
20 ms
entry-button.css
37 ms
bbtn-s_v3.png
43 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
26 ms
ad_status.js
34 ms
close-window-icon.png
1022 ms
old_ico.png
1013 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
10 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
40 ms
3fd1bd10.js
567 ms
338 ms
pn
341 ms
prtimes.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.
prtimes.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
prtimes.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prtimes.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 Prtimes.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.
prtimes.jp
Open Graph data is detected on the main page of PR TIMES. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: