Analyze PR TIMES|プレスリリース・ニュースリリースNo.1配信サービス

プレスリリースをPR TIMESで配信して、効果的なPRを実現。上場企業の43.52%(1,680社/3,860社)が利用する現在シェアNo.1のプレスリリース配信代行サービス。話題のベンチャー~グローバル企業のニュースリリースが集まる生活者も要注目のサイトです。プレスリリースの受信は無料です。

Page load speed analysis

  • 60/100

    Normal result
  • 6

    Successful tests
  • 2

    Failed tests
  • First response

    1.3 sec

  • Resources loaded

    3.7 sec

  • Page rendered

    358 ms

  • Total page load time

    5.4 sec

Welcome to homepage info - get ready to check PR TIMES best content for Japan right away, or after learning these important things about

We analyzed 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.

Page optimization

  • HTML 160.5 kB
    Images 1.0 MB
    Javascripts 1.0 MB
    CSS 1.0 MB

    In fact, the total size of 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. 65% of websites need less resources to load. CSS take 1.0 MB which makes up the majority of the site volume.

    • Original 160.5 kB
    • After minification 140.7 kB
    • After compression 26.6 kB

    HTML optimization

    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.

    • Original 1.0 MB
    • After optimization 876.3 kB

    Image optimization

    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.

    • Original 1.0 MB
    • After minification 945.4 kB
    • After compression 304.7 kB

    JavaScript optimization

    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 732.0 kB or 71% of the original size.

    • Original 1.0 MB
    • After minification 713.7 kB
    • After compression 120.9 kB

    CSS optimization

    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. needs all CSS files to be minified and compressed as it can save up to 916.5 kB or 88% of the original size.

Network requests diagram

  • style.css
  • modernizr.custom.js
  • outbrain.js
  • googleana.js
  • googleana2.js
  • bookmark_button.js
  • conversion.js
  • jquery.min.js
  • jquery-ui-1.10.4.min.js
  • jquery.transit.min.js
  • widgets.js
  • platform.js
  • jquery.cookie.js
  • common.js
  • common.js
  • jquery.flexslider-min.js
  • iframe_api
  • index.js
  • release.js
  • common_parts.js
  • css
  • analytics.js
  • 195339.js
  • mqdefault.jpg
  • button-only@2x.png
  • mqdefault.jpg
  • mqdefault.jpg
  • mqdefault.jpg
  • mqdefault.jpg
  • mqdefault.jpg
  • mqdefault.jpg
  • mqdefault.jpg
  • logo.png
  • icon.png
  • still7.jpg
  • heading.png
  • d8859-300-114568-1.jpg
  • d16946-3-105816-1.jpg
  • d15600-2-729855-0.jpg
  • d12501-19-541667-1.jpg
  • d9999-41-424059-1.jpg
  • d4741-20-689651-0.jpg
  • d84-550-629727-5.jpg
  • d15536-9-915856-3.jpg
  • d12784-14-760208-1.jpg
  • d17006-3-408036-3.jpeg
  • d17276-3-483500-1.jpg
  • d11770-29-788589-3.jpg
  • d17718-1-726226-2.jpg
  • d2703-624-368191-1.jpg
  • 118x78.png
  • banner_top-service.png
  • top_bnr_su_free.png
  • d15425-6-705783-1.jpg
  • d84-550-629727-5.jpg
  • d7006-2162-599444-2.jpg
  • d4367-342-305050-1.jpg
  • d17874-1-762222-1.jpg
  • d7303-319-292756-1.jpg
  • d10721-6-162859-0.jpg
  • d15834-11-106290-1.jpg
  • d17319-3-545152-0.jpg
  • 68x45.png
  • d2360-611-607787-3.jpg
  • d7006-2151-935509-0.jpg
  • d112-609-121599-2.jpg
  • d5816-104-294692-2.jpg
  • collect
  • d13649-8-830044-1.jpg
  • d4829-819-194110-1.jpg
  • d5720-197-362789-3.jpg
  • collect
  • d5816-105-569131-1.jpg
  • d5358-9-119299-0.jpg
  • cb=gapi.loaded_0
  • cb=gapi.loaded_1
  • fastbutton
  • like.php
  • platform.js
  • sdk.js
  • www-widgetapi.js
  • pta.js
  • bi.js
  • button.831500944bc3eb7ea5276ccdc3f71d2e.js
  • d10908-65-396623-0.jpg
  • d6612-46-399835-19.jpg
  • d7396-41-435563-1.jpg
  • d11353-12-557982-0.jpg
  • d5720-196-214060-1.jpg
  • tweet_button.6a78875565a912489e9aef879c881358.ja.html
  • postmessageRelay
  • DSpd5N1WKUg
  • -1cfYrhulAt.js
  • LVx-xkvaJ0b.png
  • api.js
  • core:rpc:shindig.random:shindig.sha1.js
  • 2536007149-postmessagerelay.js
  • cb=gapi.loaded_0
  • cb=gapi.loaded_1
  • grlryt2bdKIyfMSOhzd1eA.woff
  • www-embed-player-vflZsBgOl.css
  • www-embed-player.js
  • base.js
  • d5738-136-446148-1.jpg
  • d12840-6-307256-1.jpg
  • d11414-245-306598-3.jpg
  • d5069-318-801163-1.jpg
  • d8880-27-102649-0.jpg
  • jot
  • xd_arbiter.php
  • xd_arbiter.php
  • reset.css
  • entry-button.css
  • bbtn-s_v3.png
  • yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
  • ad_status.js
  • close-window-icon.png
  • old_ico.png
  • 2UX7WLTfW3W8TclTUvlFyQ.woff
  • RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
  • 3fd1bd10.js
  • pn

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, 6% (8 requests) were made to and 6% (8 requests) were made to The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain

Additional info on


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.











Possible request optimization













Normal result

IP address uses IP addresses which are currently shared with 16 other domains. The more sites share the same stack of IP addresses, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Normal result

IP Trace

DNS records

Type Host Target/ip TTL Other
A 55
A 55
A 55
A 55
NS 300

HTTPS certificate

SSL Certificate has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Poor result

Visitor World Map

Country of origin for 96.8% of all visits is Japan. It lies approximately 6720 miles away from the server location (United States) and such a long distance can negatively affect website speed, as it takes some time for data to travel back and forth between those places. That’s why one of the best ways to speed up page load time for the majority of users is moving the server to Japan or just closer to the user base.

Poor result

Good result

Social Sharing Optimization

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:

Language and encoding

Normal result


JA ja language flag


N/A  language flag





Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.

Share this report in social media

Analyze another website