5.9 sec in total
1.4 sec
4.4 sec
166 ms
Visit pr.goo.ne.jp now to see the best up-to-date Pr Goo content for Japan and also check out these interesting facts you probably never knew about pr.goo.ne.jp
NTTドコモからのプレスリリースです。
Visit pr.goo.ne.jpWe analyzed Pr.goo.ne.jp page load time and found that the first response time was 1.4 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
pr.goo.ne.jp performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value5.5 s
18/100
25%
Value11.4 s
5/100
10%
Value1,440 ms
15/100
30%
Value0
100/100
15%
Value11.8 s
17/100
10%
1354 ms
190 ms
181 ms
482 ms
26 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 7% of them (5 requests) were addressed to the original Pr.goo.ne.jp, 29% (20 requests) were made to Static.xx.fbcdn.net and 23% (16 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Pr.goo.ne.jp.
Page size can be reduced by 376.9 kB (43%)
877.9 kB
501.0 kB
In fact, the total size of Pr.goo.ne.jp main page is 877.9 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. 40% of websites need less resources to load. Images take 373.7 kB which makes up the majority of the site volume.
Potential reduce by 189.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 42.5 kB, which is 19% 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 189.5 kB or 83% of the original size.
Potential reduce by 4.1 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. Pr Goo images are well optimized though.
Potential reduce by 142.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 142.7 kB or 64% of the original size.
Potential reduce by 40.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. Pr.goo.ne.jp needs all CSS files to be minified and compressed as it can save up to 40.5 kB or 77% of the original size.
Number of requests can be reduced by 40 (59%)
68
28
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pr Goo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
pr.goo.ne.jp
1354 ms
1.3.css
190 ms
x.css
181 ms
style.css
482 ms
css
26 ms
goo.png
45 ms
gtm.js
140 ms
analytics.js
7 ms
collect
4 ms
collect
92 ms
collect
3 ms
collect
97 ms
1.8.js
66 ms
x.js
14 ms
x.js
28 ms
1.1.js
13 ms
script.js
165 ms
VLTraceDMD.js
518 ms
bnr_goo_no_ne.png
161 ms
bnr_goo_fb.png
321 ms
sdk.js
270 ms
124 ms
xd_arbiter.php
274 ms
xd_arbiter.php
477 ms
b.js
526 ms
like_box.php
210 ms
SwWqNEM2GQB.css
296 ms
qfDTH5pB6Ut.css
367 ms
drXqyuWvz8i.css
527 ms
3FAK8vb1hBH.css
563 ms
0cKHCb_yAjC.css
573 ms
1kPfZUdGrka.js
633 ms
cwV0x8mDYml.js
632 ms
Mpe38fuBVZ2.js
497 ms
n8qIhCw3vMx.js
585 ms
QKy94bWvcbp.js
594 ms
6q5od22S-uf.js
667 ms
7B-2ZS3Qt8r.js
698 ms
qcMicXoOToy.js
839 ms
57RpJa05x58.js
792 ms
a_62_780.js
145 ms
xsync
804 ms
ins_syncxl.js
19 ms
syncxl.html
3 ms
syncxl.js
4 ms
is
746 ms
is
376 ms
1926805_1044034692327647_839956496662899096_n.jpg
352 ms
10632718_751535438244242_6681847648693051572_n.png
413 ms
11745678_507405269413449_2575287254895656213_n.jpg
482 ms
12795350_194062864293121_5554292630957478636_n.jpg
548 ms
12004675_968736933198101_1987633703351285474_n.jpg
550 ms
10441142_593695854077700_7890808806726851067_n.jpg
551 ms
538002_4067117895997_27114963_n.jpg
570 ms
1379841_10150004552801901_469209496895221757_n.jpg
548 ms
1239047_1381161742161223_1988842856_n.jpg
609 ms
10599123_1045469145517535_7575518810021029506_n.png
1161 ms
10370819_1044846365579813_2312741725026723927_n.png
850 ms
1914545_1044035925660857_6389280138841822882_n.png
915 ms
1910401_1044023315662118_2887098291130514008_n.jpg
682 ms
12670406_1044023342328782_1383737386648029805_n.jpg
636 ms
10406425_1044023345662115_1533894185298762559_n.jpg
676 ms
1926805_1044034692327647_839956496662899096_n.jpg
704 ms
wL6VQj7Ab77.png
69 ms
s7jcwEQH7Sx.png
70 ms
QDwYpIaRyfG.png
71 ms
K00K-UgnsKu.png
69 ms
VXcANLwwL5J.js
70 ms
AmlxWlqMvlv.js
135 ms
pr.goo.ne.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
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.
pr.goo.ne.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
pr.goo.ne.jp SEO score
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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pr.goo.ne.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 Pr.goo.ne.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.
pr.goo.ne.jp
Open Graph data is detected on the main page of Pr Goo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: