1.1 sec in total
66 ms
928 ms
107 ms
Click here to check amazing Sweet Tee Cakes content. Otherwise, check out these important facts you probably never knew about sweetteecakes.com
Sweet Tee Cakes Serving Maryland, DC and Virginia. Custom cakes cupcakes and other desserts in MD, DC, VA
Visit sweetteecakes.comWe analyzed Sweetteecakes.com page load time and found that the first response time was 66 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
sweetteecakes.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value12.4 s
0/100
25%
Value8.3 s
19/100
10%
Value1,420 ms
15/100
30%
Value0.431
22/100
15%
Value15.6 s
6/100
10%
66 ms
36 ms
34 ms
30 ms
102 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Sweetteecakes.com, 38% (15 requests) were made to Static.parastorage.com and 30% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (661 ms) relates to the external source Items-images-production.s3.us-west-2.amazonaws.com.
Page size can be reduced by 780.3 kB (40%)
2.0 MB
1.2 MB
In fact, the total size of Sweetteecakes.com main page is 2.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. 45% of websites need less resources to load. Images take 931.4 kB which makes up the majority of the site volume.
Potential reduce by 469.2 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 469.2 kB or 79% of the original size.
Potential reduce by 126.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. Obviously, Sweet Tee Cakes needs image optimization as it can save up to 126.0 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 185.1 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 185.1 kB or 42% of the original size.
Number of requests can be reduced by 10 (42%)
24
14
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sweet Tee Cakes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.sweetteecakes.com
66 ms
minified.js
36 ms
focus-within-polyfill.js
34 ms
polyfill.min.js
30 ms
thunderbolt-commons.b70ee867.bundle.min.js
102 ms
main.317ed945.bundle.min.js
103 ms
main.renderer.1d21f023.bundle.min.js
26 ms
lodash.min.js
101 ms
react.production.min.js
92 ms
react-dom.production.min.js
103 ms
siteTags.bundle.min.js
101 ms
original.png
661 ms
0ebffc_c11d5ae8d7904dc5ae5e05688479d424~mv2.jpg
54 ms
bundle.min.js
54 ms
1%20(1)%20(1).png
42 ms
0ebffc_02751027ecb34cfd85e9369ce9277d8b~mv2.jpg
40 ms
e1c78c_77c93b5deb6640d9be49039a5f359d4e~mv2.png
41 ms
0ebffc_b16c0240b359426f95b35a5f60a1b7f2~mv2.jpg
41 ms
0ebffc_e9204fe9152c4c64a42b258af21deaea~mv2.jpg
40 ms
0ebffc_ab545505b6384d43a999c37bd75e3afe~mv2.jpg
40 ms
41d000_c976780ea750b22ff011ed5a9e1f76d9.jpg
44 ms
106 ms
105 ms
105 ms
101 ms
102 ms
100 ms
136 ms
136 ms
129 ms
131 ms
132 ms
131 ms
deprecation-en.v5.html
6 ms
bolt-performance
26 ms
deprecation-style.v5.css
7 ms
right-arrow.svg
19 ms
WixMadeforDisplay_W_Bd.woff
6 ms
WixMadeforText_W_Bd.woff
5 ms
WixMadeforText_W_Rg.woff
6 ms
sweetteecakes.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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
sweetteecakes.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
sweetteecakes.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Sweetteecakes.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 Sweetteecakes.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.
sweetteecakes.com
Open Graph data is detected on the main page of Sweet Tee Cakes. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: