Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

26to50.com

26to50

Page Load Speed

6.9 sec in total

First Response

1.1 sec

Resources Loaded

5.7 sec

Page Rendered

109 ms

26to50.com screenshot

About Website

Click here to check amazing 26 To 50 content. Otherwise, check out these important facts you probably never knew about 26to50.com

翻訳家のグループによる、新しい海外小説の紹介サイト。メンバーの選んだ作品を翻訳して掲載します。その他海外の作家や編集者へのインタビューなども掲載しています。On this site we to promote new writings and new writers, both to our readers and to our publishers in Japan

Visit 26to50.com

Key Findings

We analyzed 26to50.com page load time and found that the first response time was 1.1 sec and then it took 5.8 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

26to50.com performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value210 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.6 s

57/100

10%

Network Requests Diagram

www.26to50.com

1087 ms

main.css

194 ms

no.css

1030 ms

no.js

1030 ms

geov2.js

1061 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 47% of them (7 requests) were addressed to the original 26to50.com, 27% (4 requests) were made to Bc.geocities.yahoo.co.jp and 7% (1 request) were made to I.yimg.jp. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Logql.yahoo.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 50.8 kB (68%)

Content Size

74.7 kB

After Optimization

24.0 kB

In fact, the total size of 26to50.com main page is 74.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. Javascripts take 60.3 kB which makes up the majority of the site volume.

HTML Optimization

-51%

Potential reduce by 1.2 kB

  • Original 2.3 kB
  • After minification 2.2 kB
  • After compression 1.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. 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 1.2 kB or 51% of the original size.

JavaScript Optimization

-65%

Potential reduce by 39.4 kB

  • Original 60.3 kB
  • After minification 58.6 kB
  • After compression 21.0 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 39.4 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 10.2 kB

  • Original 12.1 kB
  • After minification 8.8 kB
  • After compression 1.9 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. 26to50.com needs all CSS files to be minified and compressed as it can save up to 10.2 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

14

After Optimization

11

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 26 To 50. 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.

Accessibility Review

26to50.com accessibility score

100

Accessibility Issues

Best Practices

26to50.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

26to50.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 26to50.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 26to50.com 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 26 To 50. 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: