7.2 sec in total
281 ms
6.1 sec
839 ms
Welcome to honeywellbakes.com homepage info - get ready to check Honeywell Bakes best content right away, or after learning these important things about honeywellbakes.com
The planet friendly bakery for hand iced unique biscuit gifts and artisan baking kits. Order for nationwide delivery in plastic-free packaging for all occasions
Visit honeywellbakes.comWe analyzed Honeywellbakes.com page load time and found that the first response time was 281 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
honeywellbakes.com performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value23.8 s
0/100
25%
Value19.0 s
0/100
10%
Value4,770 ms
0/100
30%
Value0.038
100/100
15%
Value27.1 s
0/100
10%
281 ms
2761 ms
69 ms
34 ms
35 ms
Our browser made a total of 196 requests to load all elements on the main page. We found that 80% of them (156 requests) were addressed to the original Honeywellbakes.com, 14% (27 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Assets.pinterest.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Honeywellbakes.com.
Page size can be reduced by 309.6 kB (17%)
1.8 MB
1.5 MB
In fact, the total size of Honeywellbakes.com main page is 1.8 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. Only a small number of websites need less resources to load. Javascripts take 983.7 kB which makes up the majority of the site volume.
Potential reduce by 303.7 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 303.7 kB or 84% of the original size.
Potential reduce by 916 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. Honeywell Bakes images are well optimized though.
Potential reduce by 2.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 2.8 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. Honeywellbakes.com has all CSS files already compressed.
Number of requests can be reduced by 148 (95%)
156
8
The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Honeywell Bakes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 96 to 1 for JavaScripts and from 54 to 1 for CSS and as a result speed up the page load time.
honeywellbakes.com
281 ms
honeywellbakes.com
2761 ms
gtm.js
69 ms
index.css
34 ms
sbi-styles.min.css
35 ms
blocks.css
29 ms
cookie-law-info-public.css
31 ms
cookie-law-info-gdpr.css
39 ms
style.css
41 ms
jquery-ui.css
28 ms
woocommerce-layout.css
46 ms
woocommerce.css
41 ms
form-basic.css
47 ms
woocommerce.css
52 ms
pinterest-for-woocommerce-pins.min.css
49 ms
frontend.css
52 ms
style.css
53 ms
animate.min.css
59 ms
style.css
86 ms
all.min.css
95 ms
v4-shims.min.css
63 ms
public.css
99 ms
style.css
109 ms
elementor-icons.min.css
107 ms
frontend.min.css
116 ms
swiper.min.css
113 ms
font-awesome.min.css
128 ms
frontend.min.css
154 ms
post-50187.css
114 ms
frontend.min.css
136 ms
jet-blog.css
129 ms
flatpickr.min.css
133 ms
global.css
147 ms
post-2818.css
133 ms
post-50224.css
151 ms
post-68025.css
179 ms
post-115405.css
181 ms
post-75850.css
182 ms
tp.widget.bootstrap.min.js
20 ms
lib.js
907 ms
custom.css
161 ms
checkout-blocks.css
156 ms
wacp-frontend.min.css
158 ms
perfect-scrollbar.min.css
168 ms
woocommerce.css
158 ms
fontawesome.min.css
164 ms
solid.min.css
152 ms
style.css
157 ms
regular.min.css
158 ms
brands.min.css
155 ms
jquery.min.js
152 ms
jquery-migrate.min.js
181 ms
utm-tracker.min.js
184 ms
cookie-law-info-public.js
185 ms
headerScript.min.js
176 ms
jquery.blockUI.min.js
147 ms
js.cookie.min.js
138 ms
woocommerce.min.js
139 ms
gtm4wp-woocommerce-enhanced.js
142 ms
pinit.js
121 ms
fo.js
143 ms
wc-blocks.css
136 ms
post-53223.css
133 ms
all-products.css
129 ms
frontend.css
126 ms
animations.min.css
121 ms
cookie-law-info-table.css
120 ms
public.css
121 ms
webfont.min.js
117 ms
utils.min.js
115 ms
cart-fragments.min.js
164 ms
email-decode.min.js
99 ms
core.min.js
159 ms
js.js
132 ms
datepicker.min.js
132 ms
lazysizes.min.js
130 ms
lazysizes.min.js
138 ms
add-to-cart.min.js
138 ms
sourcebuster.min.js
136 ms
order-attribution.min.js
134 ms
mailchimp-woocommerce-public.min.js
136 ms
tracker.js
135 ms
wc-quick-view.js
128 ms
underscore.min.js
131 ms
frontend.min.js
189 ms
vue.min.js
130 ms
jet-menu-public-scripts.js
105 ms
pinterest-for-woocommerce-tracking.min.js
104 ms
pinterest-for-woocommerce-save-button.min.js
117 ms
wacp-frontend.min.js
674 ms
perfect-scrollbar.min.js
673 ms
jquery.sticky.min.js
153 ms
tp.min.js
74 ms
lodash.min.js
669 ms
wp-polyfill.min.js
668 ms
moment.min.js
666 ms
hooks.min.js
667 ms
deprecated.min.js
672 ms
date.min.js
675 ms
index.js
671 ms
react.min.js
669 ms
index.js
667 ms
react-dom.min.js
667 ms
index.js
860 ms
i18n.min.js
862 ms
url.min.js
860 ms
css
80 ms
api-fetch.min.js
856 ms
react-jsx-runtime.min.js
799 ms
dom-ready.min.js
799 ms
a11y.min.js
808 ms
dom.min.js
806 ms
escape-html.min.js
804 ms
S6u8w4BMUTPHh30AXC-v.ttf
74 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
594 ms
S6uyw4BMUTPHjx4wWw.ttf
594 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
600 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
601 ms
S6u-w4BMUTPHjxsIPx-oPCc.ttf
600 ms
S6u_w4BMUTPHjxsI9w2_Gwfo.ttf
600 ms
S6u8w4BMUTPHjxsAXC-v.ttf
601 ms
S6u_w4BMUTPHjxsI5wq_Gwfo.ttf
604 ms
S6u_w4BMUTPHjxsI3wi_Gwfo.ttf
798 ms
element.min.js
802 ms
is-shallow-equal.min.js
794 ms
keycodes.min.js
797 ms
priority-queue.min.js
798 ms
compose.min.js
802 ms
html-entities.min.js
799 ms
primitives.min.js
801 ms
private-apis.min.js
798 ms
redux-routine.min.js
796 ms
data.min.js
798 ms
rich-text.min.js
903 ms
warning.min.js
904 ms
23db68133c9ed08a6e5bae9d9.js
903 ms
fbevents.js
773 ms
core.js
771 ms
components.min.js
860 ms
ywcas-settings.js
852 ms
ywcas-blocks-data.js
849 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WCzsWzLdnfw.ttf
437 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WCwkWzLdnfw.ttf
434 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WC2UWzLdnfw.ttf
437 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WC7sWzLdnfw.ttf
438 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WCzsXzLdnfw.ttf
437 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WC-URzLdnfw.ttf
441 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WC9wRzLdnfw.ttf
558 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WC7sRzLdnfw.ttf
439 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WC5IRzLdnfw.ttf
451 ms
ywcas-blocks-registry.js
332 ms
accounting.min.js
337 ms
search-block-frontend.js
335 ms
jquery.smartmenus.min.js
335 ms
url-polyfill.min.js
334 ms
imagesloaded.min.js
335 ms
webpack-pro.runtime.min.js
338 ms
webpack.runtime.min.js
342 ms
frontend-modules.min.js
339 ms
frontend.min.js
338 ms
waypoints.min.js
338 ms
frontend.min.js
267 ms
q5uUsoa5M_tv7IihmnkabC5XiXCAlXGks1WZkG1MP5s7.ttf
405 ms
q5uUsoa5M_tv7IihmnkabC5XiXCAlXGks1WZTm1MP5s7.ttf
252 ms
q5uUsoa5M_tv7IihmnkabC5XiXCAlXGks1WZzm1MP5s7.ttf
405 ms
q5uUsoa5M_tv7IihmnkabC5XiXCAlXGks1WZ_G1MP5s7.ttf
404 ms
q5uUsoa5M_tv7IihmnkabC5XiXCAlXGks1WZEGpMP5s7.ttf
270 ms
q5uUsoa5M_tv7IihmnkabC5XiXCAlXGks1WZKWpMP5s7.ttf
402 ms
q5uUsoa5M_tv7IihmnkabC5XiXCAlXGks1WZTmpMP5s7.ttf
349 ms
q5uUsoa5M_tv7IihmnkabC5XiXCAlXGks1WZZ2pMP5s7.ttf
401 ms
elements-handlers.min.js
151 ms
widgets-scripts.js
151 ms
wp-util.min.js
154 ms
frontend.min.js
156 ms
jet-blog.min.js
152 ms
flatpickr.min.js
154 ms
public.js
149 ms
icomoon.ttf
433 ms
fa-regular-400.woff
499 ms
fa-regular-400.woff
560 ms
fa-solid-900.woff
651 ms
fa-solid-900.woff
609 ms
eicons.woff
650 ms
holiday-regular-webfont.woff
959 ms
open-sans-v27-latin-ext_latin-regular.woff
926 ms
open-sans-v27-latin-ext_latin-700.woff
924 ms
jupiterx.woff
1003 ms
sbi-sprite.png
961 ms
close.svg
853 ms
honeywell-logo.svg
849 ms
4Q1A8595.jpg
848 ms
20342ff8dd1f3b29ae293c71d.js
104 ms
honeywellbakes.com
1534 ms
pinit_main.js
13 ms
Jar-Of-Pumpkin-Biscuits-1.jpg
424 ms
woocommerce-smallscreen.css
14 ms
honeywellbakes.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
honeywellbakes.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
honeywellbakes.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Honeywellbakes.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 Honeywellbakes.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.
honeywellbakes.com
Open Graph description is not detected on the main page of Honeywell Bakes. 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: