Tools & Wizards About Us
sapie.or.jp screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

sapie.or.jp

サピエ

Page Load Speed

2.6 sec in total

First Response

521 ms

Resources Loaded

2 sec

Page Rendered

109 ms

sapie.or.jp screenshot

About Website

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

「サピエ」は、視覚障害者を始め、目で文字を読むことが困難な方々に対して、さまざまな情報を点字、音声データで提供するネットワークです。

Visit sapie.or.jp

Key Findings

We analyzed Sapie.or.jp page load time and found that the first response time was 521 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

sapie.or.jp performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value2.5 s

97/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.121

84/100

15%

TTI (Time to Interactive)

Value1.2 s

100/100

10%

Network Requests Diagram

sapie.or.jp

521 ms

CN1WWW

203 ms

base.css

345 ms

home.css

343 ms

accesstool.js

344 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that all of those requests were addressed to Sapie.or.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (521 ms) belongs to the original domain Sapie.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.9 kB (11%)

Content Size

35.0 kB

After Optimization

31.1 kB

  • HTML
  • Images

In fact, the total size of Sapie.or.jp main page is 35.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. Only 10% of websites need less resources to load. Images take 29.4 kB which makes up the majority of the site volume.

HTML Optimization

-56%

Potential reduce by 3.2 kB

  • Original 5.6 kB
  • After minification 5.6 kB
  • After compression 2.5 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 3.2 kB or 56% of the original size.

Image Optimization

-3%

Potential reduce by 740 B

  • Original 29.4 kB
  • After minification 28.7 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. Sapie images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

21

After Optimization

21

  • Images
  • JavaScript
  • CSS

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sapie. According to our analytics all requests are already optimized.

Network Requests Diagram

sapie.or.jp

sapie.or.jp

521 ms

CN1WWW

CN1WWW

203 ms

base.css

base.css

345 ms

home.css

home.css

343 ms

accesstool.js

accesstool.js

344 ms

acc.js

acc.js

348 ms

logo.png

logo.png

173 ms

logo_home.gif

logo_home.gif

174 ms

trc.gif

trc.gif

175 ms

ac_font.gif

ac_font.gif

173 ms

ac_color.gif

ac_color.gif

173 ms

ac_text.gif

ac_text.gif

327 ms

nav_bg2.png

nav_bg2.png

327 ms

icon_id.gif

icon_id.gif

328 ms

home_earth.jpg

home_earth.jpg

511 ms

body_bg.jpg

body_bg.jpg

344 ms

title_bg3.png

title_bg3.png

343 ms

home_menu_library.gif

home_menu_library.gif

498 ms

home_menu_local.gif

home_menu_local.gif

499 ms

home_menu_support.gif

home_menu_support.gif

500 ms

home_entry.gif

home_entry.gif

513 ms

title_bg1.png

title_bg1.png

514 ms

print.css

print.css

172 ms

Accessibility Review

sapie.or.jp accessibility score

100

Accessibility Issues

Best Practices

sapie.or.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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

sapie.or.jp SEO score

97

Search Engine Optimization Advices

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sapie.or.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 Sapie.or.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

sapie.or.jp

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