Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

8.7 sec in total

First Response

685 ms

Resources Loaded

7.8 sec

Page Rendered

220 ms

springs.jp screenshot

About Website

Click here to check amazing Springs content for Japan. Otherwise, check out these important facts you probably never knew about springs.jp

久光製薬スプリングスのオフィシャルサイトです。

Visit springs.jp

Key Findings

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

Performance Metrics

springs.jp performance score

0

Network Requests Diagram

springs.jp

685 ms

base.css

316 ms

style.css

637 ms

jquery.min.js

71 ms

smoothRollOver.js

322 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 84% of them (105 requests) were addressed to the original Springs.jp, 4% (5 requests) were made to Content.googleapis.com and 3% (4 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Springs.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 306.5 kB (17%)

Content Size

1.9 MB

After Optimization

1.5 MB

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

HTML Optimization

-81%

Potential reduce by 39.3 kB

  • Original 48.6 kB
  • After minification 39.3 kB
  • After compression 9.2 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 9.3 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 39.3 kB or 81% of the original size.

Image Optimization

-12%

Potential reduce by 196.2 kB

  • Original 1.7 MB
  • After minification 1.5 MB

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, Springs needs image optimization as it can save up to 196.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-51%

Potential reduce by 27.7 kB

  • Original 54.1 kB
  • After minification 42.9 kB
  • After compression 26.5 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 27.7 kB or 51% of the original size.

CSS Optimization

-86%

Potential reduce by 43.3 kB

  • Original 50.5 kB
  • After minification 43.2 kB
  • After compression 7.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. Springs.jp needs all CSS files to be minified and compressed as it can save up to 43.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (11%)

Requests Now

124

After Optimization

110

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

SEO Factors

springs.jp SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Springs.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Springs.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.

Social Sharing Optimization

Open Graph data is detected on the main page of Springs. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: