3.2 sec in total
248 ms
2.6 sec
299 ms
Click here to check amazing Sweetlyall content. Otherwise, check out these important facts you probably never knew about sweetlyall.com
BUZZWORD
Visit sweetlyall.comWe analyzed Sweetlyall.com page load time and found that the first response time was 248 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
sweetlyall.com performance score
name
value
score
weighting
Value1.5 s
95/100
10%
Value3.3 s
70/100
25%
Value1.7 s
100/100
10%
Value480 ms
60/100
30%
Value0.015
100/100
15%
Value3.2 s
94/100
10%
248 ms
419 ms
132 ms
133 ms
102 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 85% of them (50 requests) were addressed to the original Sweetlyall.com, 8% (5 requests) were made to Buzzworduk.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Sweetlyall.com.
Page size can be reduced by 287.1 kB (17%)
1.7 MB
1.4 MB
In fact, the total size of Sweetlyall.com main page is 1.7 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. 20% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 21.9 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 21.9 kB or 79% of the original size.
Potential reduce by 136.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. Sweetlyall images are well optimized though.
Potential reduce by 63.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 63.9 kB or 67% of the original size.
Potential reduce by 65.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. Sweetlyall.com needs all CSS files to be minified and compressed as it can save up to 65.2 kB or 85% of the original size.
Number of requests can be reduced by 19 (37%)
52
33
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sweetlyall. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
sweetlyall.com
248 ms
www.sweetlyall.com
419 ms
style.css
132 ms
jquery-ui-1.10.3.custom.css
133 ms
reset.css
102 ms
ajax.js
90 ms
blocker.js
80 ms
jquery.min.js
66 ms
css
33 ms
cookiecuttr.css
103 ms
jquery.cookie.js
123 ms
jquery.cookiecuttr.js
129 ms
jquery.bxslider.js
209 ms
jquery.bxslider.css
147 ms
functions.js
169 ms
jquery-ui.js
7 ms
analytics.js
93 ms
index.php
66 ms
index.php
1100 ms
index.php
1109 ms
index.php
1053 ms
banner04RnR.jpg
624 ms
index.php
676 ms
Alphabet-slider.jpg
465 ms
banner03HFWP1.jpg
632 ms
banner05HFWP_2.jpg
584 ms
banner04RnR.jpg
604 ms
bg.jpg
122 ms
logo.png
88 ms
top_menu_bg.png
56 ms
s1.png
95 ms
s2.png
126 ms
search_bg.png
134 ms
search_icon.png
159 ms
top_basket_bg.png
164 ms
arrow_top2.png
211 ms
line.png
196 ms
small_arrow.png
201 ms
1940894777.jpg
239 ms
565159831.jpg
250 ms
1760801277.jpg
252 ms
783111403.jpg
279 ms
bg_product.png
289 ms
783111403.jpg
336 ms
2107636635.jpg
361 ms
565159831.jpg
364 ms
1940894777.jpg
435 ms
1760801277.jpg
418 ms
1019492645.jpg
455 ms
1666170132.jpg
463 ms
1028500289.jpg
487 ms
992164769.jpg
506 ms
964227619.jpg
507 ms
2042297988.jpg
535 ms
footer_logos.png
554 ms
ui-bg_flat_75_ffffff_40x100.png
583 ms
bx_loader.gif
1606 ms
RobotoCondensed-Regular-webfont.woff
609 ms
controls.png
1657 ms
sweetlyall.com accessibility score
sweetlyall.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
sweetlyall.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sweetlyall.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Sweetlyall.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.
sweetlyall.com
Open Graph description is not detected on the main page of Sweetlyall. 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: