Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

sitestock.jp

サイト売買やサイトM&AのコンサルティングならSiteStock

Page Load Speed

12 sec in total

First Response

1.4 sec

Resources Loaded

10.1 sec

Page Rendered

480 ms

sitestock.jp screenshot

About Website

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

サイト売買、売却、M&A、買収、買取、ドメイン、ホームページ、営業権譲渡などのコンサルティング業務ならサイトストックにお任せください。月間平均取引額1,000万円以上、売買専業企業No.1の取引実績。ワールドビジネスサテライト等メディア登場多数。.

Visit sitestock.jp

Key Findings

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

Performance Metrics

sitestock.jp performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value4,000 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.333

34/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

sitestock.jp

1391 ms

heightLine.js

363 ms

index.js

385 ms

jquery.js

769 ms

mypage.css

387 ms

Our browser made a total of 135 requests to load all elements on the main page. We found that 87% of them (118 requests) were addressed to the original Sitestock.jp, 3% (4 requests) were made to Pagead2.googlesyndication.com and 2% (3 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Sitestock.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 129.4 kB (7%)

Content Size

1.7 MB

After Optimization

1.6 MB

In fact, the total size of Sitestock.jp main page is 1.7 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. 45% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 36.9 kB

  • Original 47.8 kB
  • After minification 42.4 kB
  • After compression 10.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. This page needs HTML code to be minified as it can gain 5.3 kB, which is 11% 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 36.9 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 5.0 kB

  • Original 1.5 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. Site Stock images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 52.5 kB

  • Original 178.1 kB
  • After minification 176.6 kB
  • After compression 125.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 52.5 kB or 29% of the original size.

CSS Optimization

-86%

Potential reduce by 35.0 kB

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

Requests Breakdown

Number of requests can be reduced by 26 (20%)

Requests Now

131

After Optimization

105

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

Accessibility Review

sitestock.jp accessibility score

84

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Names and labels

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.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

sitestock.jp best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

sitestock.jp SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

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

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sitestock.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 Sitestock.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 description is not detected on the main page of Site Stock. 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: