2.8 sec in total
478 ms
2.2 sec
142 ms
Click here to check amazing Little 4 content. Otherwise, check out these important facts you probably never knew about little4.com
World leading educational robots and STEM solutions for educational institutions and schools.
Visit little4.comWe analyzed Little4.com page load time and found that the first response time was 478 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
little4.com performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value10.1 s
0/100
25%
Value6.7 s
36/100
10%
Value1,020 ms
26/100
30%
Value0.276
44/100
15%
Value11.8 s
17/100
10%
478 ms
25 ms
288 ms
42 ms
241 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 51% of them (31 requests) were addressed to the original Little4.com, 28% (17 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (964 ms) belongs to the original domain Little4.com.
Page size can be reduced by 68.1 kB (3%)
2.3 MB
2.3 MB
In fact, the total size of Little4.com main page is 2.3 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. 65% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 31.5 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 31.5 kB or 75% of the original size.
Potential reduce by 18.0 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. Little 4 images are well optimized though.
Potential reduce by 9.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. This website has mostly compressed JavaScripts.
Potential reduce by 9.2 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. Little4.com needs all CSS files to be minified and compressed as it can save up to 9.2 kB or 13% of the original size.
Number of requests can be reduced by 33 (77%)
43
10
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Little 4. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
Default.asp
478 ms
jquery-ui.css
25 ms
default.css
288 ms
jquery-3.7.1.min.js
42 ms
jquery-migrate-merged.js
241 ms
jquery-ui.min.js
36 ms
volusion.js
408 ms
content.css
225 ms
paypal-rest-default-buttons.js
315 ms
soft_add.js
199 ms
soft_add_mult.js
310 ms
soft_add.css
310 ms
javascripts.js
342 ms
f2c8c7e93216e073_complete.js
40 ms
js
49 ms
template.css
599 ms
style-editor.css
419 ms
design-toolkit.min.js
430 ms
picturefill.min.js
435 ms
vnav.css
466 ms
vnav.js
508 ms
bjqs.css
645 ms
jquery-1.7.1.min.js
30 ms
bjqs-1.3.min.js
667 ms
v84a3a4012de94ce1a686ba8c167c359c1696973893317
92 ms
clear1x1.gif
575 ms
banner01.jpg
672 ms
banner02.jpg
768 ms
banner03.jpg
732 ms
banner04.jpg
964 ms
jquery-1.11.1.min.js
727 ms
slider.min.js
740 ms
template.min.js
763 ms
class-name-watcher.js
825 ms
fontello.css
483 ms
ionicons.min.css
463 ms
js
45 ms
css
64 ms
js
182 ms
analytics.js
30 ms
S6uyw4BMUTPHjx4wWw.ttf
169 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
170 ms
S6u8w4BMUTPHh30AXC-v.ttf
174 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
174 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
173 ms
header_bg.jpg
242 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ0LQl2xMB.ttf
152 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ql2xMB.ttf
150 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl2xMB.ttf
149 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl2xMB.ttf
222 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7Ml2xMB.ttf
221 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl2xMB.ttf
222 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ml2xMB.ttf
224 ms
collect
196 ms
collect
116 ms
S6u8w4BMUTPHjxsAXC-v.ttf
152 ms
S6u_w4BMUTPHjxsI9w2_Gwfo.ttf
154 ms
S6u-w4BMUTPHjxsIPx-oPCc.ttf
176 ms
S6u_w4BMUTPHjxsI5wq_Gwfo.ttf
177 ms
S6u_w4BMUTPHjxsI3wi_Gwfo.ttf
155 ms
main.js
27 ms
little4.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
ARIA IDs are not unique
little4.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
little4.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Little4.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 Little4.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.
little4.com
Open Graph description is not detected on the main page of Little 4. 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: