1.3 sec in total
121 ms
976 ms
178 ms
Click here to check amazing The Sweetpea content. Otherwise, check out these important facts you probably never knew about thesweetpea.com
Sweetpea, Burlesque Icon
Visit thesweetpea.comWe analyzed Thesweetpea.com page load time and found that the first response time was 121 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
thesweetpea.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value8.8 s
1/100
25%
Value7.9 s
22/100
10%
Value1,320 ms
17/100
30%
Value0.3
39/100
15%
Value12.5 s
14/100
10%
121 ms
148 ms
175 ms
45 ms
44 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 23% of them (10 requests) were addressed to the original Thesweetpea.com, 65% (28 requests) were made to Cdn2.editmysite.com and 2% (1 request) were made to Widget.privy.com. The less responsive or slowest element that took the longest time to load (255 ms) relates to the external source Static.zotabox.com.
Page size can be reduced by 87.0 kB (5%)
1.7 MB
1.6 MB
In fact, the total size of Thesweetpea.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. 70% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 74.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. 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 74.8 kB or 82% of the original size.
Potential reduce by 424 B
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. The Sweetpea images are well optimized though.
Potential reduce by 11.2 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. This website has mostly compressed JavaScripts.
Potential reduce by 614 B
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. Thesweetpea.com has all CSS files already compressed.
Number of requests can be reduced by 25 (86%)
29
4
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of The Sweetpea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
thesweetpea.com
121 ms
www.thesweetpea.com
148 ms
www.thesweetpea.com
175 ms
sites.css
45 ms
fancybox.css
44 ms
social-icons.css
41 ms
main_style.css
110 ms
font.css
42 ms
font.css
43 ms
font.css
58 ms
font.css
58 ms
font.css
57 ms
font.css
57 ms
font.css
57 ms
jquery-1.8.3.min.js
57 ms
stl.js
62 ms
main.js
60 ms
commerce-core.js
56 ms
main-commerce-browse.js
57 ms
widget.js
61 ms
email-decode.min.js
28 ms
plugins.js
211 ms
custom.js
185 ms
mobile.js
186 ms
main-customer-accounts-site.js
58 ms
widgets.js
255 ms
pea-logo.png
28 ms
queen-pea-catwoman-1-1_orig.jpg
203 ms
regular.woff
9 ms
medium.woff
9 ms
light.woff
8 ms
ultralight.woff
15 ms
semibold.woff
8 ms
bold.woff
16 ms
ga.js
67 ms
snowday262.js
46 ms
api.js
77 ms
regular.woff
17 ms
light.woff
17 ms
bold.woff
18 ms
regular.woff
18 ms
wsocial.woff
24 ms
recaptcha__en.js
32 ms
thesweetpea.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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
thesweetpea.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
thesweetpea.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
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 Thesweetpea.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 Thesweetpea.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.
thesweetpea.com
Open Graph data is detected on the main page of The Sweetpea. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: