2.1 sec in total
387 ms
1.5 sec
255 ms
Visit candybouquet.com now to see the best up-to-date Candybouquet content for United States and also check out these interesting facts you probably never knew about candybouquet.com
This domain may be for sale!
Visit candybouquet.comWe analyzed Candybouquet.com page load time and found that the first response time was 387 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
candybouquet.com performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value3.2 s
71/100
25%
Value2.9 s
95/100
10%
Value210 ms
89/100
30%
Value0.272
45/100
15%
Value3.2 s
94/100
10%
387 ms
340 ms
685 ms
258 ms
347 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 95% of them (38 requests) were addressed to the original Candybouquet.com, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (685 ms) belongs to the original domain Candybouquet.com.
Page size can be reduced by 165.7 kB (31%)
540.8 kB
375.1 kB
In fact, the total size of Candybouquet.com main page is 540.8 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. 15% of websites need less resources to load. Images take 345.6 kB which makes up the majority of the site volume.
Potential reduce by 7.4 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 7.4 kB or 69% of the original size.
Potential reduce by 19.9 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. Candybouquet images are well optimized though.
Potential reduce by 117.4 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 117.4 kB or 74% of the original size.
Potential reduce by 21.0 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. Candybouquet.com needs all CSS files to be minified and compressed as it can save up to 21.0 kB or 82% of the original size.
Number of requests can be reduced by 6 (15%)
39
33
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Candybouquet. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
candybouquet.com
387 ms
stylefd.css
340 ms
jquery.js
685 ms
ui.core.js
258 ms
ui.tabs.js
347 ms
jquery.idTabs.min.js
182 ms
scriptsfd.js
246 ms
AC_RunActiveContent.js
361 ms
pagesfd.css
92 ms
bg_top.jpg
94 ms
logo.jpg
191 ms
badge_since1989.png
91 ms
top_contactus.gif
101 ms
top_franchise.gif
98 ms
bg_nav.gif
88 ms
nav_home.gif
181 ms
nav_wheretoroder.gif
183 ms
nav_ourbouquets.gif
182 ms
nav_franchising.gif
188 ms
nav_aboutus.gif
186 ms
nav_tastynews.gif
272 ms
bg_content.gif
263 ms
getwellsoon.png
472 ms
happybirthday.png
539 ms
bg_welcome_top.gif
261 ms
bg_welcome_bottom.gif
265 ms
heading_sendacandybouquet.gif
347 ms
btn_ordernow_green.png
352 ms
bg_bouquet_features.jpg
358 ms
bg_newsletter.jpg
464 ms
btn_newslettersubscribe.png
458 ms
bg_tabbox.gif
432 ms
bg_tabbox_top.gif
444 ms
tab_box_franchising.gif
526 ms
tab_box_tastynews.gif
542 ms
bg_tabbox_bottom.gif
549 ms
franchising_girl.gif
550 ms
bg_bottom.gif
553 ms
ga.js
27 ms
__utm.gif
25 ms
candybouquet.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
<frame> or <iframe> elements do not have a title
candybouquet.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
candybouquet.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Candybouquet.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Candybouquet.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.
candybouquet.com
Open Graph description is not detected on the main page of Candybouquet. 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: