Access sapporo.travel. 【公式】札幌観光情報サイトようこそさっぽろ

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value31.9 s

0/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value39.5 s

0/100

10%

sapporo.travel

10 ms

www.sapporo.travel

54 ms

gtm.js

101 ms

adsbygoogle.js

171 ms

all.css

52 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 53% of them (52 requests) were addressed to the original Sapporo.travel, 9% (9 requests) were made to Pagead2.googlesyndication.com and 6% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Sapporo.travel.

Content Size

8.0 MB

After Optimization

7.3 MB

In fact, the total size of Sapporo.travel main page is 8.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.9 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 63.3 kB

Original 80.1 kB
After minification 74.7 kB
After compression 16.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. 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 63.3 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 306.3 kB

Original 6.9 MB
After minification 6.6 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. Sapporo images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 406.4 kB

Original 1.0 MB
After minification 1.0 MB
After compression 603.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 406.4 kB or 40% of the original size.

CSS Optimization

-0%

Potential reduce by 136 B

Original 43.7 kB
After minification 43.7 kB
After compression 43.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. Sapporo.travel has all CSS files already compressed.

Requests Now

After Optimization

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