Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

tootoo.to

CGI RESCUE レンタル掲示板サービス

Page Load Speed

4.2 sec in total

First Response

589 ms

Resources Loaded

2.4 sec

Page Rendered

1.2 sec

tootoo.to screenshot

About Website

Click here to check amazing Tootoo content for Japan. Otherwise, check out these important facts you probably never knew about tootoo.to

レンタル画像掲示板サービスです。

Visit tootoo.to

Key Findings

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

Performance Metrics

tootoo.to performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value6.4 s

59/100

10%

Network Requests Diagram

tootoo.to

589 ms

index2.css

357 ms

show_ads.js

6 ms

Logo_25wht.gif

28 ms

q7324.gif

913 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 31% of them (8 requests) were addressed to the original Tootoo.to, 12% (3 requests) were made to Pagead2.googlesyndication.com and 8% (2 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (913 ms) relates to the external source Rescue.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 240.4 kB (64%)

Content Size

375.8 kB

After Optimization

135.4 kB

In fact, the total size of Tootoo.to main page is 375.8 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. 35% of websites need less resources to load. Javascripts take 360.5 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 8.2 kB

  • Original 12.5 kB
  • After minification 12.1 kB
  • After compression 4.4 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 8.2 kB or 65% of the original size.

JavaScript Optimization

-64%

Potential reduce by 230.2 kB

  • Original 360.5 kB
  • After minification 353.9 kB
  • After compression 130.4 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 230.2 kB or 64% of the original size.

CSS Optimization

-77%

Potential reduce by 2.1 kB

  • Original 2.7 kB
  • After minification 2.2 kB
  • After compression 620 B

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. Tootoo.to needs all CSS files to be minified and compressed as it can save up to 2.1 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (40%)

Requests Now

25

After Optimization

15

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

Accessibility Review

tootoo.to accessibility score

69

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

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

tootoo.to best practices score

67

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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

tootoo.to SEO score

75

Search Engine Optimization Advices

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 Tootoo.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 Tootoo.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

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