14 sec in total
244 ms
13.5 sec
276 ms
Click here to check amazing Sweetgrowth content for Singapore. Otherwise, check out these important facts you probably never knew about sweetgrowth.com
Forsale Lander
Visit sweetgrowth.comWe analyzed Sweetgrowth.com page load time and found that the first response time was 244 ms and then it took 13.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
sweetgrowth.com performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value8.1 s
2/100
25%
Value29.5 s
0/100
10%
Value46,690 ms
0/100
30%
Value0
100/100
15%
Value59.5 s
0/100
10%
244 ms
2133 ms
76 ms
195 ms
195 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Sweetgrowth.com, 75% (33 requests) were made to Deo.shopeemobile.com and 7% (3 requests) were made to Shopee.sg. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Analytics.tiktok.com.
Page size can be reduced by 287.5 kB (70%)
411.2 kB
123.7 kB
In fact, the total size of Sweetgrowth.com main page is 411.2 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 411.2 kB which makes up the majority of the site volume.
Potential reduce by 287.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 287.5 kB or 70% of the original size.
Number of requests can be reduced by 30 (81%)
37
7
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sweetgrowth. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
sweetgrowth.com
244 ms
redzapple.sg
2133 ms
polyfill-legacy.001061db45c9310f.legacy.js
76 ms
index.js
195 ms
bundle.588a882573da6164.css
195 ms
796 ms
polyfill.6eeeee64c6017caa.js
12 ms
polyfill.e74248e871a636a1.js
5 ms
polyfill.0b761ff65aca5425.js
242 ms
gtm.js
67 ms
landing
90 ms
869.8e8ded9ce2f327c7.js
70 ms
bundle.8794fdc5ce70fff7.js
100 ms
webpack-runtime.ac532925337cbfd0.legacy.js
69 ms
869.f80a28901fec03ac.legacy.js
134 ms
bundle.6982f715bd0f7342.legacy.js
235 ms
bundle.27a6db7ef04f056c.legacy.css
78 ms
landing
965 ms
770a8fca674a3550e241a6de7fa82d8b.woff
813 ms
eb797abfa6a5cca2463e423c07c4f6ea.woff
812 ms
8dc942c71385e7509b87af5d07f3db78.woff
812 ms
8bd7856b64b4313341ebfbc0136c9d74.woff
837 ms
fbevents.js
855 ms
events.js
3928 ms
events.js
3929 ms
en.col179.1664877711.json
88 ms
7624.78fe96e48d071cab.legacy.js
59 ms
firebase.9fafead03e87c4c4.legacy.js
59 ms
bundle.27a6db7ef04f056c.legacy.css
311 ms
139835196351422
3028 ms
tracking-loader@1.1.5.min.js
2965 ms
pcmall-shopmicrofe.40715073f7cd57a100e3.legacy.js
2841 ms
get_payment_info
2936 ms
config.json
2834 ms
bundle.27a6db7ef04f056c.legacy.css
151 ms
5128.045ede1537ac66c7.legacy.js
2138 ms
sentry.1e109e6c975c4e01.legacy.js
2138 ms
require-trackingsdk.js
2117 ms
97.9f6925ae941f5003afb3.legacy.js
2100 ms
431.59d710d284d0015cea7a.legacy.css
2099 ms
431.4a299871c5651beb47ea.legacy.js
2098 ms
613832263d29374ef4cd566434d8f268cb15367d.js
2220 ms
431.59d710d284d0015cea7a.legacy.css
39 ms
index.min.js
202 ms
sweetgrowth.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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
sweetgrowth.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
sweetgrowth.com SEO score
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
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sweetgrowth.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 Sweetgrowth.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.
sweetgrowth.com
Open Graph description is not detected on the main page of Sweetgrowth. 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: