2.3 sec in total
493 ms
1.6 sec
217 ms
Welcome to littlesomething.com homepage info - get ready to check Littlesomething best content right away, or after learning these important things about littlesomething.com
Visit littlesomething.comWe analyzed Littlesomething.com page load time and found that the first response time was 493 ms and then it took 1.8 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.
littlesomething.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value3.7 s
59/100
25%
Value3.5 s
88/100
10%
Value130 ms
96/100
30%
Value0.45
20/100
15%
Value4.0 s
87/100
10%
493 ms
181 ms
116 ms
97 ms
254 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 61% of them (49 requests) were addressed to the original Littlesomething.com, 13% (10 requests) were made to Static.xx.fbcdn.net and 6% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (493 ms) belongs to the original domain Littlesomething.com.
Page size can be reduced by 243.1 kB (32%)
762.0 kB
518.9 kB
In fact, the total size of Littlesomething.com main page is 762.0 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. 55% of websites need less resources to load. Images take 490.0 kB which makes up the majority of the site volume.
Potential reduce by 42.7 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 12.5 kB, which is 24% 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 42.7 kB or 82% of the original size.
Potential reduce by 63.4 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, Littlesomething needs image optimization as it can save up to 63.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 125.9 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 125.9 kB or 61% of the original size.
Potential reduce by 11.1 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. Littlesomething.com needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 79% of the original size.
Number of requests can be reduced by 31 (42%)
73
42
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Littlesomething. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.littlesomething.com
493 ms
utilities.js
181 ms
default_modified.css
116 ms
tabs.css
97 ms
jquery.min.js
254 ms
jquery.quicksearch.js
105 ms
quicksearch.css
113 ms
css
54 ms
css
66 ms
detect.js
140 ms
jquery-1.3.2.min.js
263 ms
webwidget_slideshow_dot.css
125 ms
webwidget_slideshow_dot.js
128 ms
webfont.js
43 ms
ga.js
42 ms
bodybg.png
65 ms
divider.png
65 ms
headerBotBg.png
170 ms
logo.png
133 ms
tele.png
65 ms
cart.gif
66 ms
textfeild.gif
96 ms
search.gif
96 ms
navbg.png
96 ms
navdivider.gif
97 ms
in_business.png
210 ms
lefttitlebg.png
223 ms
spacer.gif
224 ms
slide2.jpg
216 ms
slide5.jpg
216 ms
slide3.jpg
210 ms
slide4.jpg
280 ms
slide6.jpg
258 ms
slide7.jpg
260 ms
productpicture_thumbnail.jpg
258 ms
addtocart.gif
265 ms
chc-pnts-6oz-snowman_thumbnail.jpg
267 ms
10_thumbnail.jpg
352 ms
basilbag1_thumbnail.jpg
351 ms
37_thumbnail.jpg
354 ms
43_thumbnail.jpg
351 ms
line1.gif
421 ms
thumbnail.asp
330 ms
subscrib.png
434 ms
thumbnail.asp
440 ms
footerlogo.png
435 ms
feature_bg.png
409 ms
footerBg.png
415 ms
arrow.png
411 ms
all.js
24 ms
css
46 ms
__utm.gif
36 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
73 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
101 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
116 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
144 ms
c2o0ps8nkBmaOYctqBq1rXhCUOGz7vYGh680lGh-uXM.woff
142 ms
widgets.js
94 ms
76 ms
count.asp
376 ms
xd_arbiter.php
29 ms
xd_arbiter.php
60 ms
carousel_circle_normal.png
313 ms
carousel_circle_solid.png
311 ms
like_box.php
53 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
126 ms
410ucuAGgaJ.css
36 ms
pERLJfhzcxv.css
122 ms
q68gy-v_YMF.js
32 ms
FJmpeSpHpjS.js
35 ms
0wM5s1Khldu.js
32 ms
1bNoFZUdlYZ.js
34 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
95 ms
10372793_10152140704392653_7078404790686188049_n.jpg
57 ms
wL6VQj7Ab77.png
24 ms
s7jcwEQH7Sx.png
23 ms
I6-MnjEovm5.js
3 ms
pQrUxxo5oQp.js
5 ms
spacer.gif
41 ms
jot
87 ms
littlesomething.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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
littlesomething.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
Page has valid source maps
littlesomething.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Littlesomething.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Littlesomething.com main page’s claimed encoding is iso-8859-1. 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.
littlesomething.com
Open Graph description is not detected on the main page of Littlesomething. 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: