Access spctour.jp. 格安航空券と格安ツアーのSPC（エスピーシー）

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value2,090 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.111

87/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

spctour.jp

1466 ms

www.spctour.jp

1235 ms

normalize.css

350 ms

base.css

546 ms

tour_country.js

378 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 43% of them (41 requests) were addressed to the original Spctour.jp, 22% (21 requests) were made to Static.xx.fbcdn.net and 11% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Spctour.jp.

Content Size

1.2 MB

After Optimization

983.0 kB

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

HTML Optimization

-75%

Potential reduce by 21.7 kB

Original 28.8 kB
After minification 22.7 kB
After compression 7.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. This page needs HTML code to be minified as it can gain 6.1 kB, which is 21% 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 21.7 kB or 75% of the original size.

Image Optimization

-9%

Potential reduce by 84.9 kB

Original 993.2 kB
After minification 908.3 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. Spctour images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 103.8 kB

Original 163.4 kB
After minification 162.5 kB
After compression 59.6 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 103.8 kB or 64% of the original size.

CSS Optimization

-85%

Potential reduce by 45.3 kB

Original 53.4 kB
After minification 43.1 kB
After compression 8.0 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. Spctour.jp needs all CSS files to be minified and compressed as it can save up to 45.3 kB or 85% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 Spctour.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 Spctour.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

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