2.5 sec in total
46 ms
2 sec
399 ms
Click here to check amazing Funnysize content. Otherwise, check out these important facts you probably never knew about funnysize.com
My Store
Visit funnysize.comWe analyzed Funnysize.com page load time and found that the first response time was 46 ms and then it took 2.4 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.
funnysize.com performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value5.7 s
17/100
25%
Value7.3 s
28/100
10%
Value760 ms
39/100
30%
Value0
100/100
15%
Value7.3 s
50/100
10%
46 ms
900 ms
39 ms
34 ms
30 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Funnysize.com, 82% (31 requests) were made to Thepetcore.com and 8% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (956 ms) relates to the external source Thepetcore.com.
Page size can be reduced by 395.8 kB (13%)
3.0 MB
2.6 MB
In fact, the total size of Funnysize.com main page is 3.0 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.6 MB which makes up the majority of the site volume.
Potential reduce by 30.8 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 7.8 kB, which is 22% 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 30.8 kB or 85% of the original size.
Potential reduce by 86.7 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. Funnysize images are well optimized though.
Potential reduce by 141.0 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 141.0 kB or 67% of the original size.
Potential reduce by 137.3 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. Funnysize.com needs all CSS files to be minified and compressed as it can save up to 137.3 kB or 82% of the original size.
Number of requests can be reduced by 8 (26%)
31
23
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funnysize. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
funnysize.com
46 ms
www.thepetcore.com
900 ms
jquery-2.1.1.min.js
39 ms
bootstrap.min.css
34 ms
bootstrap.min.js
30 ms
font-awesome.min.css
20 ms
css
31 ms
stylesheet.css
21 ms
owl.carousel.css
70 ms
956 ms
common.js
32 ms
owl.carousel.min.js
68 ms
analytics.js
29 ms
logo.png
67 ms
us.png
15 ms
mx.png
65 ms
ca.png
65 ms
aquarium-1140x380.png
91 ms
img_1-1140x380.png
100 ms
img_6-1140x380.png
94 ms
img_5-1140x380.png
120 ms
img_2_0-1140x380.png
113 ms
nfl-130x100.png
65 ms
redbull-130x100.png
66 ms
sony-130x100.png
77 ms
cocacola-130x100.png
80 ms
burgerking-130x100.png
91 ms
canon-130x100.png
101 ms
harley-130x100.png
101 ms
dell-130x100.png
103 ms
disney-130x100.png
107 ms
starbucks-130x100.png
110 ms
nintendo-130x100.png
111 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
50 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
50 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
51 ms
fontawesome-webfont.woff
100 ms
collect
22 ms
funnysize.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
funnysize.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
funnysize.com 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
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 Funnysize.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 Funnysize.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.
funnysize.com
Open Graph description is not detected on the main page of Funnysize. 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: