Report Summary

  • 50

    Performance

    Renders faster than
    68% 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

  • 100

    SEO

    Google-friendlier than
    94% of websites

rgtd.net

Ryogo Toyoda / 3D illustrator based on Tokyo, Japan

Page Load Speed

14.4 sec in total

First Response

2.2 sec

Resources Loaded

7 sec

Page Rendered

5.1 sec

About Website

Click here to check amazing Rgtd content for Russia. Otherwise, check out these important facts you probably never knew about rgtd.net

Ryogo Toyoda / 3D illustrator based on Tokyo, Japan,Ryogo Toyoda – 3D illustrator/Motion designer based on Tokyo,Japan.

Visit rgtd.net

Key Findings

We analyzed Rgtd.net page load time and found that the first response time was 2.2 sec and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

rgtd.net performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

24/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value330 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

rgtd.net

2212 ms

css

25 ms

style.css

546 ms

styles.css

332 ms

public.css

331 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 95% of them (127 requests) were addressed to the original Rgtd.net, 1% (2 requests) were made to Fonts.googleapis.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Rgtd.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 228.4 kB (2%)

Content Size

13.8 MB

After Optimization

13.6 MB

In fact, the total size of Rgtd.net main page is 13.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 13.3 MB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 184.4 kB

  • Original 198.6 kB
  • After minification 165.1 kB
  • After compression 14.2 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 33.5 kB, which is 17% 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 184.4 kB or 93% of the original size.

Image Optimization

-0%

Potential reduce by 12 B

  • Original 13.3 MB
  • After minification 13.3 MB

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. Rgtd images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 16.6 kB

  • Original 264.3 kB
  • After minification 264.3 kB
  • After compression 247.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-41%

Potential reduce by 27.3 kB

  • Original 65.9 kB
  • After minification 65.9 kB
  • After compression 38.6 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. Rgtd.net needs all CSS files to be minified and compressed as it can save up to 27.3 kB or 41% of the original size.

Requests Breakdown

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

Requests Now

130

After Optimization

114

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

Accessibility Review

rgtd.net accessibility score

100

Accessibility Issues

Best Practices

rgtd.net best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

rgtd.net SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rgtd.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Rgtd.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

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