Report Summary

  • 96

    Performance

    Renders faster than
    94% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 69

    SEO

    Google-friendlier than
    37% of websites

Page Load Speed

7 sec in total

First Response

1.9 sec

Resources Loaded

4.9 sec

Page Rendered

178 ms

screenshots.jp screenshot

About Website

Click here to check amazing Screenshots content. Otherwise, check out these important facts you probably never knew about screenshots.jp

スクリーンショット.jp(ScreenShots.jp)はMac SafariやWindows IEなど複数バージョンのマルチブラウザでクロスブラウザチェックができる便利ツールです。Webサイトのページのスクリーンショットを撮って表示確認やレイアウトチェック。無料(フリー)お試し版も。

Visit screenshots.jp

Key Findings

We analyzed Screenshots.jp page load time and found that the first response time was 1.9 sec and then it took 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

screenshots.jp performance score

96

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

95/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

screenshots.jp

1949 ms

newsscroll.js

640 ms

import.css

351 ms

jquery.js

877 ms

script.js

534 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 94% of them (80 requests) were addressed to the original Screenshots.jp, 2% (2 requests) were made to Smarticon.geotrust.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Screenshots.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 129.6 kB (47%)

Content Size

278.0 kB

After Optimization

148.3 kB

In fact, the total size of Screenshots.jp main page is 278.0 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. 25% of websites need less resources to load. Javascripts take 111.0 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 16.4 kB

  • Original 22.1 kB
  • After minification 19.5 kB
  • After compression 5.7 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 2.6 kB, which is 12% 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 16.4 kB or 74% of the original size.

Image Optimization

-4%

Potential reduce by 3.8 kB

  • Original 100.0 kB
  • After minification 96.2 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. Screenshots images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 70.9 kB

  • Original 111.0 kB
  • After minification 103.3 kB
  • After compression 40.1 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 70.9 kB or 64% of the original size.

CSS Optimization

-86%

Potential reduce by 38.5 kB

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

Requests Breakdown

Number of requests can be reduced by 35 (42%)

Requests Now

84

After Optimization

49

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

Accessibility Review

screenshots.jp accessibility score

59

Accessibility Issues

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

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

screenshots.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

screenshots.jp SEO score

69

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Screenshots.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), while the claimed language is Japanese. Our system also found out that Screenshots.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 Screenshots. 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: