Tools & Wizards About Us
aleph.to screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

aleph.to

【 Aleph（アレフ） 公式サイト 】 苦しみからの解放と解脱・悟りを説く

Page Load Speed

6.2 sec in total

First Response

838 ms

Resources Loaded

5.1 sec

Page Rendered

301 ms

aleph.to screenshot

About Website

Visit aleph.to now to see the best up-to-date Aleph content for Russia and also check out these interesting facts you probably never knew about aleph.to

Aleph(アレフ)公式サイト。Alephの理念を紹介しています。全国の道場のご案内、およびメールフォームもあります。

Visit aleph.to

Key Findings

We analyzed Aleph.to page load time and found that the first response time was 838 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

aleph.to performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

76/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

aleph.to

838 ms

script.js

370 ms

style2.css

562 ms

hover.css

1584 ms

jquery.min.js

1407 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 211.5 kB (35%)

Content Size

600.7 kB

After Optimization

389.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aleph.to main page is 600.7 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 371.6 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 2.8 kB

  • Original 4.6 kB
  • After minification 4.2 kB
  • After compression 1.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. 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 2.8 kB or 62% of the original size.

Image Optimization

-6%

Potential reduce by 23.9 kB

  • Original 371.6 kB
  • After minification 347.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. Aleph images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 63.9 kB

  • Original 95.4 kB
  • After minification 90.8 kB
  • After compression 31.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 63.9 kB or 67% of the original size.

CSS Optimization

-94%

Potential reduce by 120.9 kB

  • Original 129.1 kB
  • After minification 107.1 kB
  • After compression 8.2 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. Aleph.to needs all CSS files to be minified and compressed as it can save up to 120.9 kB or 94% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (16%)

Requests Now

19

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aleph.to

aleph.to

838 ms

script.js

script.js

370 ms

style2.css

style2.css

562 ms

hover.css

hover.css

1584 ms

jquery.min.js

jquery.min.js

1407 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

812 ms

acclog.js

acclog.js

225 ms

top-sora.png

top-sora.png

2839 ms

top-close.png

top-close.png

209 ms

top-information.png

top-information.png

188 ms

top-logo.png

top-logo.png

734 ms

menu_07.png

menu_07.png

197 ms

menu_02.png

menu_02.png

204 ms

menu_03.png

menu_03.png

374 ms

menu_04.png

menu_04.png

392 ms

menu_05.png

menu_05.png

407 ms

menu_06.png

menu_06.png

416 ms

top-mandala.png

top-mandala.png

2058 ms

copyright.png

copyright.png

586 ms

acclog.cgi

acclog.cgi

657 ms

Accessibility Review

aleph.to accessibility score

74

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

Image elements do not have [alt] attributes

Best Practices

aleph.to best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

aleph.to 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

Image elements do not have [alt] attributes

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 Aleph.to 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 Aleph.to 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

aleph.to

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