13.7 sec in total
2.5 sec
10.6 sec
632 ms
Visit sweetpotatopaper.com now to see the best up-to-date Sweetpotatopaper content and also check out these interesting facts you probably never knew about sweetpotatopaper.com
Visit sweetpotatopaper.comWe analyzed Sweetpotatopaper.com page load time and found that the first response time was 2.5 sec and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
sweetpotatopaper.com performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value12.8 s
0/100
25%
Value8.7 s
17/100
10%
Value720 ms
41/100
30%
Value0.836
4/100
15%
Value12.2 s
15/100
10%
2499 ms
52 ms
75 ms
114 ms
123 ms
Our browser made a total of 177 requests to load all elements on the main page. We found that 87% of them (154 requests) were addressed to the original Sweetpotatopaper.com, 3% (5 requests) were made to Fonts.googleapis.com and 2% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Sweetpotatopaper.com.
Page size can be reduced by 3.7 MB (66%)
5.7 MB
2.0 MB
In fact, the total size of Sweetpotatopaper.com main page is 5.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. 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. CSS take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 239.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. This page needs HTML code to be minified as it can gain 29.8 kB, which is 11% 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 239.2 kB or 86% of the original size.
Potential reduce by 15.8 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. Sweetpotatopaper images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 70% of the original size.
Potential reduce by 2.4 MB
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. Sweetpotatopaper.com needs all CSS files to be minified and compressed as it can save up to 2.4 MB or 88% of the original size.
Number of requests can be reduced by 130 (80%)
162
32
The browser has sent 162 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sweetpotatopaper. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 73 to 1 for JavaScripts and from 59 to 1 for CSS and as a result speed up the page load time.
sweetpotatopaper.com
2499 ms
webfont.js
52 ms
wp-emoji-release.min.js
75 ms
font-awesome.css
114 ms
style.css
123 ms
public.css
125 ms
custom-css.css
124 ms
font-awesome.min.css
69 ms
dashicons.min.css
161 ms
jquery-ui-dialog.min.css
133 ms
woocomposer.min.css
146 ms
styles.css
153 ms
jquery-ui.css
154 ms
jquery.fancyProductDesigner.min.css
203 ms
fancy-product.css
182 ms
settings.css
187 ms
awesome.css
191 ms
woocommerce-layout.css
193 ms
woocommerce.css
194 ms
defaults.css
212 ms
fonts.css
219 ms
base.css
223 ms
style.css
224 ms
css
92 ms
css
112 ms
prettyPhoto.css
224 ms
jquery.selectBox.css
235 ms
style.css
244 ms
font-awesome.min.css
254 ms
js_composer.min.css
379 ms
custom-css.css
257 ms
Defaults.css
264 ms
css
117 ms
ultimate.min.css
344 ms
app.css
275 ms
easyzoom.css
284 ms
woocommerce-overwrite.css
293 ms
animate.min.css
300 ms
animations-products-grid.css
309 ms
fresco.css
320 ms
js
85 ms
conversion.js
73 ms
webfont.js
38 ms
jquery.easing.min.js
58 ms
idangerous.swiper.css
319 ms
owl.carousel.css
272 ms
owl.theme.css
269 ms
offcanvas.css
264 ms
nanoscroller.css
299 ms
select2.css
299 ms
defaults.css
296 ms
styles.css
290 ms
responsive.css
279 ms
style.css
282 ms
font-awesome.min.css
281 ms
style.css
277 ms
core-init.css
268 ms
core-min.css
277 ms
style.css
267 ms
jquery.bxslider.css
269 ms
animate.css
267 ms
shadows.css
258 ms
animate.css
290 ms
jquery.js
296 ms
jquery-migrate.min.js
279 ms
jquery.themepunch.tools.min.js
314 ms
jquery.themepunch.revolution.min.js
277 ms
wpbo_thumbnail_input_validation.js
268 ms
picturefill.min.js
259 ms
jquery.cookie.js
279 ms
public.js
300 ms
gtm4wp-contact-form-7-tracker.js
290 ms
gtm4wp-form-move-tracker.js
282 ms
ultimate.min.js
303 ms
modernizr.custom.js
268 ms
jscripts.php
268 ms
core.min.js
257 ms
widget.min.js
244 ms
mouse.min.js
244 ms
resizable.min.js
405 ms
draggable.min.js
365 ms
button.min.js
366 ms
position.min.js
331 ms
dialog.min.js
330 ms
wpdialog.min.js
330 ms
woocomposer.min.js
331 ms
site_tracking.js
324 ms
jquery.form.min.js
322 ms
scripts.js
322 ms
jquery.blockUI.min.js
322 ms
woocommerce.min.js
309 ms
jquery.cookie.min.js
310 ms
cart-fragments.min.js
299 ms
cuzd-dispatch.min.js
299 ms
jquery.prettyPhoto.min.js
297 ms
jquery.prettyPhoto.init.min.js
297 ms
jquery.selectBox.min.js
298 ms
jquery.yith-wcwl.js
263 ms
add-to-cart-variation.js
262 ms
foundation.min.js
351 ms
foundation.interchange.js
262 ms
isotope.pkgd.min.js
347 ms
imagesloaded.js
345 ms
jquery.touchSwipe.min.js
315 ms
jquery.fitvids.js
294 ms
idangerous.swiper.min.js
295 ms
owl.carousel.min.js
413 ms
fresco.js
406 ms
jquery.nanoscroller.min.js
402 ms
select2.min.js
403 ms
jquery.scroll_to.js
401 ms
jquery.stellar.min.js
400 ms
jquery.snapscroll.min.js
401 ms
easyzoom.js
395 ms
scripts.js
235 ms
jscripts-ftr-min.js
234 ms
core-init.js
236 ms
core-min.js
232 ms
wp-embed.min.js
231 ms
responsive-progressbar.js
231 ms
js_composer_front.min.js
231 ms
comment-reply.min.js
230 ms
jquery.bxslider.js
251 ms
jquery.fitvids.js
249 ms
frontend.js
248 ms
frontend.js
249 ms
jquery.lettering.js
249 ms
jquery.textillate.js
247 ms
logobeta.png
532 ms
2Bride-banner-975x574.jpg
626 ms
2books-banner-975x574.jpg
626 ms
2bday-banner-975x574.jpg
530 ms
2Bride-banner-243x191.jpg
527 ms
2books-banner-243x191.jpg
526 ms
2bday-banner-243x191.jpg
619 ms
call-center.png
532 ms
free-delivery.png
531 ms
delivery-date.png
531 ms
fundraising.png
533 ms
blerd_1024x1024-570x570.png
1838 ms
Delta-elephant-180x256.png
535 ms
analytics.js
66 ms
wpspin_light.gif
413 ms
graphic-rain-180x256.png
452 ms
Criss-Cross-180x256.png
503 ms
Floral-Bridal-180x256.png
452 ms
Barnard2-500x355.jpg
452 ms
199425089719024878_14V0QHug_f-467x355.jpg
1716 ms
72dc72411c52f12018f50ad16104c7cb-500x355.jpg
1716 ms
budget-wed-500x334.jpg
1716 ms
small-pie-logo.png
1715 ms
ajax-loader.gif
1713 ms
fontawesome-webfont.woff
1698 ms
fontawesome-webfont.woff
1698 ms
fontawesome-webfont.woff
1699 ms
fontawesome-webfont.woff
208 ms
fontawesome-webfont.woff
1699 ms
getbowtied-icons.woff
1697 ms
lXoKq2PC8Z_S1wl-BwvrB-vvDin1pK8aKteLpeZ5c0A.ttf
384 ms
WooComposer.woff
1695 ms
collect
217 ms
css
47 ms
collect
1312 ms
sweetpotatopaper.com
1510 ms
admin-ajax.php
2556 ms
css
206 ms
bx_loader.gif
142 ms
controls.png
142 ms
ga-audiences
342 ms
widget_v2.135.js
140 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
49 ms
WoAoVT7K3k7hHfxKbvB6BxKju6jhv-maymYuC0OGw7k.ttf
251 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
251 ms
empty_cart_offcanvas.png
37 ms
avatar_simple_visitor.png
105 ms
aL63HcygAAVYuCCsAAA==
1 ms
woocommerce-smallscreen.css
37 ms
sweetpotatopaper.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
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.
sweetpotatopaper.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
sweetpotatopaper.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 Sweetpotatopaper.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 Sweetpotatopaper.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.
sweetpotatopaper.com
Open Graph description is not detected on the main page of Sweetpotatopaper. 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: