Tools & Wizards About Us
freeprice.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

freeprice.jp

【 レンタルサーバー使用レポ 】使ってわかった用途別選び方完全ガイド

Page Load Speed

5.4 sec in total

First Response

930 ms

Resources Loaded

4.2 sec

Page Rendered

338 ms

freeprice.jp screenshot

About Website

Visit freeprice.jp now to see the best up-to-date Freeprice content for Japan and also check out these interesting facts you probably never knew about freeprice.jp

レンタルサーバーの使用レポートと比較ランキング、用途別の選び方、基礎知識などをご紹介します。

Visit freeprice.jp

Key Findings

We analyzed Freeprice.jp page load time and found that the first response time was 930 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

freeprice.jp performance score

0

Network Requests Diagram

freeprice.jp

930 ms

common.css

713 ms

style.css

735 ms

Mst.js

576 ms

analyze.js

766 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 80% of them (20 requests) were addressed to the original Freeprice.jp, 12% (3 requests) were made to Hdqlk.analytics.qlook.net and 4% (1 request) were made to Www24.a8.net. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Freeprice.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 67.2 kB (24%)

Content Size

281.5 kB

After Optimization

214.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Freeprice.jp main page is 281.5 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. Only 10% of websites need less resources to load. Images take 213.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 19.8 kB

  • Original 24.9 kB
  • After minification 23.3 kB
  • After compression 5.1 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 19.8 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 11.7 kB

  • Original 213.5 kB
  • After minification 201.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. Freeprice images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 6.4 kB

  • Original 8.7 kB
  • After minification 7.4 kB
  • After compression 2.3 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 6.4 kB or 74% of the original size.

CSS Optimization

-85%

Potential reduce by 29.3 kB

  • Original 34.5 kB
  • After minification 28.2 kB
  • After compression 5.2 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. Freeprice.jp needs all CSS files to be minified and compressed as it can save up to 29.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (33%)

Requests Now

24

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freeprice. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Network Requests Diagram

freeprice.jp

freeprice.jp

930 ms

common.css

common.css

713 ms

style.css

style.css

735 ms

Mst.js

Mst.js

576 ms

analyze.js

analyze.js

766 ms

bgt

bgt

1141 ms

0.gif

0.gif

920 ms

counter.png

counter.png

448 ms

head_bg.jpg

head_bg.jpg

183 ms

top_logo.jpg

top_logo.jpg

713 ms

menu01.gif

menu01.gif

188 ms

menu01_bg.gif

menu01_bg.gif

193 ms

menu02.gif

menu02.gif

341 ms

menu02_bg.gif

menu02_bg.gif

364 ms

menu03.gif

menu03.gif

371 ms

menu04.gif

menu04.gif

377 ms

copy01.jpg

copy01.jpg

1164 ms

title_bg.gif

title_bg.gif

510 ms

ranking01.jpg

ranking01.jpg

902 ms

ranking02.jpg

ranking02.jpg

943 ms

ranking03.jpg

ranking03.jpg

1014 ms

ranking04.jpg

ranking04.jpg

1100 ms

ranking05.jpg

ranking05.jpg

1299 ms

ranking06.jpg

ranking06.jpg

2818 ms

analyze.png

analyze.png

532 ms

SEO Factors

freeprice.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

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

Social Sharing Optimization

freeprice.jp

Open Graph description is not detected on the main page of Freeprice. 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: