1.9 sec in total
245 ms
1.5 sec
162 ms
Visit godot-ja.readthedocs.io now to see the best up-to-date Godot Ja Readthedocs content for China and also check out these interesting facts you probably never knew about godot-ja.readthedocs.io
このドキュメントは Weblate のコミュニティー・メンバーによって、英語の原文から翻訳されました。 翻訳の進行度合いによっては、段落やページ全体がまだ英語のままになっている場合があるかもしれません。Weblateにて新しく翻訳をしたり、既存の文を査読することで、あなたもコミュニティーの助けになれます。 現時点では、翻訳版は "latest" (開発中)ブランチのみで提供されますが、しかし安定版...
Visit godot-ja.readthedocs.ioWe analyzed Godot-ja.readthedocs.io page load time and found that the first response time was 245 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
godot-ja.readthedocs.io performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value4.0 s
51/100
25%
Value4.1 s
79/100
10%
Value0 ms
100/100
30%
Value0.001
100/100
15%
Value3.7 s
90/100
10%
245 ms
150 ms
219 ms
181 ms
162 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Godot-ja.readthedocs.io, 6% (2 requests) were made to Cdn.jsdelivr.net and 3% (1 request) were made to Hosted.weblate.org. The less responsive or slowest element that took the longest time to load (660 ms) relates to the external source Docs.godotengine.org.
Page size can be reduced by 981.2 kB (91%)
1.1 MB
102.2 kB
In fact, the total size of Godot-ja.readthedocs.io main page is 1.1 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. 40% of websites need less resources to load. HTML takes 1.1 MB which makes up the majority of the site volume.
Potential reduce by 978.0 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 978.0 kB or 92% of the original size.
Potential reduce by 2.1 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. Obviously, Godot Ja Readthedocs needs image optimization as it can save up to 2.1 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 307 B
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.
Potential reduce by 782 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. Godot-ja.readthedocs.io needs all CSS files to be minified and compressed as it can save up to 782 B or 40% of the original size.
Number of requests can be reduced by 19 (83%)
23
4
The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Godot Ja Readthedocs. 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 8 to 1 for CSS and as a result speed up the page load time.
245 ms
pygments.css
150 ms
theme.css
219 ms
copybutton.css
181 ms
tabs.css
162 ms
algolia.css
179 ms
docsearch.min.css
21 ms
custom.css
184 ms
documentation_options.js
291 ms
jquery.js
296 ms
underscore.js
325 ms
doctools.js
337 ms
clipboard.min.js
347 ms
copybutton.js
362 ms
translations.js
445 ms
readthedocs-doc-embed.js
306 ms
custom.js
459 ms
docsearch.min.js
24 ms
algolia.js
660 ms
theme.js
475 ms
readthedocs-doc-embed.css
353 ms
readthedocs-analytics.js
447 ms
docs_logo.svg
148 ms
lato-normal.woff
167 ms
lato-bold.woff
301 ms
fontawesome-webfont.woff
384 ms
lato-normal-italic.woff
294 ms
lato-bold-italic.woff
273 ms
Roboto-Slab-Regular.woff
331 ms
Roboto-Slab-Bold.woff
439 ms
287x66-white.png
122 ms
godot-ja.readthedocs.io accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s do not have all required [aria-*] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
godot-ja.readthedocs.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
godot-ja.readthedocs.io SEO score
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
Document uses legible font sizes
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Godot-ja.readthedocs.io 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 Godot-ja.readthedocs.io 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.
godot-ja.readthedocs.io
Open Graph data is detected on the main page of Godot Ja Readthedocs. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: