2 sec in total
89 ms
1.8 sec
55 ms
Visit ottodot.com now to see the best up-to-date Ottodot content and also check out these interesting facts you probably never knew about ottodot.com
Mastery every Science concept through Ottodot's Roblox Science learning modules. Design based on the MOE science syllabus. For kids 5-12 year olds.
Visit ottodot.comWe analyzed Ottodot.com page load time and found that the first response time was 89 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
ottodot.com performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value7.3 s
5/100
25%
Value8.3 s
19/100
10%
Value1,250 ms
19/100
30%
Value0.001
100/100
15%
Value20.7 s
2/100
10%
89 ms
39 ms
74 ms
305 ms
57 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ottodot.com, 47% (34 requests) were made to Static.wixstatic.com and 31% (22 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 787.2 kB (51%)
1.6 MB
767.0 kB
In fact, the total size of Ottodot.com main page is 1.6 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. 35% of websites need less resources to load. HTML takes 805.2 kB which makes up the majority of the site volume.
Potential reduce by 653.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. 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 653.2 kB or 81% of the original size.
Potential reduce by 133.9 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, Ottodot needs image optimization as it can save up to 133.9 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 80 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.
Number of requests can be reduced by 11 (22%)
50
39
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ottodot. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
www.ottodot.com
89 ms
minified.js
39 ms
focus-within-polyfill.js
74 ms
polyfill.min.js
305 ms
thunderbolt-commons.4a2008b2.bundle.min.js
57 ms
main.5d83208c.bundle.min.js
56 ms
lodash.min.js
57 ms
react.production.min.js
56 ms
react-dom.production.min.js
57 ms
siteTags.bundle.min.js
56 ms
wix-perf-measure.umd.min.js
58 ms
97328e_8c8ae03b6a014390baac0d190e941917~mv2.png
217 ms
Ottodot%C2%AE.png
413 ms
97328e_edfaf19d18bc48de80111559aa8ab617~mv2.png
366 ms
Ottodot%C2%AE.png
414 ms
97328e_74eb9e853f15449083381a7f8d2681de~mv2.png
367 ms
97328e_2cb96545555945a3a2ebe46a635a6646~mv2.png
418 ms
97328e_5bb314c458e04a0f9dfad85fadd32731~mv2.png
413 ms
97328e_e4370b1ca43e4c34a04204d85f6f89d9~mv2.png
493 ms
CNA_logo.png
553 ms
cna938_logo.png
522 ms
938%20live_logo.jpg
534 ms
Mediacorp_Channel_U_logo.png
600 ms
97328e_051f068bdada42698943ad1cb3282c1d~mv2.png
566 ms
Mediacorp_Channel_8_logo.png
647 ms
97328e_0dcf88706e7748c691a77fcd1eb81a4b~mv2.png
695 ms
IMG_7810_JPG.jpg
974 ms
oea%20meaning.png
839 ms
97328e_2f9e24c34c2f4246b71226c24f034066~mv2.gif
676 ms
97328e_15d5f210b94349339e7d1bfc28c8730c~mv2.png
807 ms
Online%20Class.png
1034 ms
97328e_14deb8e7399942d7b82013f224c2e401~mv2.png
919 ms
97328e_a0234b6d66224339ac12bc30f154dc3c~mv2.png
782 ms
97328e_c8328306b1de4d87ade0736a518d7515~mv2.png
939 ms
97328e_21459d87df404452aa59d348de806d89~mv2.png
1006 ms
97328e_9b1f7e03a5da4836889614cbcffcbbd7~mv2.png
1032 ms
temasek-foundation.png
1086 ms
9.png
1131 ms
7.png
1123 ms
partner%20-%20imda%20pixel.jpeg
1194 ms
10.png
1186 ms
8.png
1184 ms
11.png
1178 ms
97328e_b41f1b67406e4ced860de0fe13f510aa~mv2.png
1227 ms
97328e_b03e95bab6374bb58ad92dd96776e59b~mv2.png
1301 ms
xfbml.customerchat.js
241 ms
bundle.min.js
178 ms
c5749443-93da-4592-b794-42f28d62ef72.woff
16 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
33 ms
b56b944e-bbe0-4450-a241-de2125d3e682.woff
33 ms
6f8d1983-4d34-4fa4-9110-988f6c495757.woff
33 ms
192dac76-a6d9-413d-bb74-22308f2e0cc5.woff
32 ms
0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff
31 ms
908c4810-64db-4b46-bb8e-823eb41f68c0.woff
96 ms
AvenirLTW05-35Light.woff
96 ms
61bd362e-7162-46bd-b67e-28f366c4afbe.woff
96 ms
AvenirLTW05-85Heavy.woff
94 ms
123 ms
128 ms
121 ms
129 ms
121 ms
121 ms
164 ms
161 ms
164 ms
175 ms
156 ms
deprecation-en.v5.html
5 ms
bolt-performance
47 ms
deprecation-style.v5.css
7 ms
right-arrow.svg
5 ms
ottodot.com accessibility score
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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
ottodot.com 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
Page has valid source maps
ottodot.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ottodot.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ottodot.com 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.
ottodot.com
Open Graph data is detected on the main page of Ottodot. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: