3.9 sec in total
1.1 sec
2.4 sec
356 ms
Visit buckheadblooms.com now to see the best up-to-date Buckhead Blooms content and also check out these interesting facts you probably never knew about buckheadblooms.com
Atlanta's premiere upscale flower shop. Same day floral delivery in the Atlanta metro area as well as surrounding Georgia neighborhoods. Beautiful flower arrangements for all occasions, birthday, symp...
Visit buckheadblooms.comWe analyzed Buckheadblooms.com page load time and found that the first response time was 1.1 sec and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
buckheadblooms.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value15.5 s
0/100
25%
Value8.1 s
21/100
10%
Value1,880 ms
9/100
30%
Value0.207
60/100
15%
Value16.4 s
5/100
10%
1116 ms
52 ms
93 ms
78 ms
75 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Buckheadblooms.com, 91% (137 requests) were made to Assets.floranext.com and 5% (8 requests) were made to Image.floranext.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Buckheadblooms.com.
Page size can be reduced by 123.8 kB (19%)
642.2 kB
518.4 kB
In fact, the total size of Buckheadblooms.com main page is 642.2 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. 60% of websites need less resources to load. Javascripts take 307.7 kB which makes up the majority of the site volume.
Potential reduce by 109.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 109.2 kB or 87% of the original size.
Potential reduce by 3.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. Buckhead Blooms images are well optimized though.
Potential reduce by 9.7 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 998 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. Buckheadblooms.com has all CSS files already compressed.
Number of requests can be reduced by 123 (88%)
140
17
The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Buckhead Blooms. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 121 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
buckheadblooms.com
1116 ms
calendar.css
52 ms
styles-m.css
93 ms
styles-l.css
78 ms
require.min.js
75 ms
requirejs-min-resolver.min.js
73 ms
mixins.min.js
77 ms
requirejs-config.min.js
71 ms
polyfill.min.js
143 ms
lazysizes.min.js
144 ms
buckhead_blooms_logo_1_2__64ff6549e47aa.png
509 ms
jquery.mobile.custom.min.js
24 ms
common.min.js
17 ms
dataPost.min.js
44 ms
bootstrap.min.js
17 ms
jquery.min.js
21 ms
translate-inline.min.js
41 ms
mage-translation-dictionary.min.js
42 ms
responsive.min.js
53 ms
theme.min.js
41 ms
opensans-400.woff
39 ms
opensans-300.woff
384 ms
opensans-600.woff
393 ms
opensans-700.woff
384 ms
domReady.min.js
121 ms
main.min.js
130 ms
bootstrap.min.js
131 ms
jquery-migrate.min.js
111 ms
jquery.min.js
107 ms
template.min.js
102 ms
confirm.min.js
118 ms
widget.min.js
117 ms
translate.min.js
124 ms
text.min.js
122 ms
smart-keyboard-handler.min.js
119 ms
mage.min.js
133 ms
ie-class-fixer.min.js
136 ms
js
126 ms
logo-basic-floranext-black.webp
90 ms
google_reviews_1.png
358 ms
banner_reyna_728x90.jpg
430 ms
2black_ccbanner.png
44 ms
dialog.min.js
89 ms
jquery-ui.min.js
89 ms
ElectraLTStd-Regular.woff
87 ms
advanced-icons.woff
88 ms
Blank-Theme-Icons.woff
382 ms
flora-base-icons.woff
402 ms
tabs.min.js
124 ms
matchMedia.min.js
113 ms
underscore.min.js
139 ms
knockout.min.js
149 ms
knockout-es5.min.js
221 ms
scripts.min.js
211 ms
engine.min.js
212 ms
bootstrap.min.js
211 ms
bootstrap.min.js
228 ms
bootstrap.min.js
247 ms
observable_array.min.js
249 ms
bound-nodes.min.js
246 ms
owl.carousel.min.js
245 ms
modal.min.js
279 ms
modal-mixin.min.js
280 ms
js
69 ms
analytics.js
21 ms
button.min.js
194 ms
draggable.min.js
194 ms
position.min.js
195 ms
resizable.min.js
196 ms
yellow_rose_special_100_65afed790cb46.jpg.webp
399 ms
img_4280_65a0567ce896c.jpg.webp
395 ms
img_4284_65a05698a099b.jpg.webp
405 ms
core.min.js
215 ms
collapsible.min.js
212 ms
collect
27 ms
knockout-repeat.min.js
94 ms
knockout-fast-foreach.min.js
101 ms
observable_source.min.js
93 ms
renderer.min.js
109 ms
console-logger.min.js
101 ms
resizable.min.js
98 ms
i18n.min.js
111 ms
scope.min.js
114 ms
range.min.js
114 ms
mage-init.min.js
136 ms
keyboard.min.js
131 ms
optgroup.min.js
125 ms
after-render.min.js
148 ms
autoselect.min.js
153 ms
datepicker.min.js
147 ms
outer_click.min.js
161 ms
fadeVisible.min.js
148 ms
collapsible.min.js
159 ms
staticChecked.min.js
159 ms
simple-checked.min.js
171 ms
bind-html.min.js
165 ms
tooltip.min.js
169 ms
color-picker.min.js
171 ms
autocomplete.min.js
183 ms
format.min.js
179 ms
44242fbb-f896-44ee-8bea-bffb68cf1a36.png.webp
81 ms
jqueryTooltip.min.js
143 ms
bootstrap-datepicker.min.js
147 ms
wrapper.min.js
146 ms
events.min.js
163 ms
es6-collections.min.js
159 ms
key-codes.min.js
135 ms
mouse.min.js
155 ms
jquery.storageapi.extended.min.js
170 ms
class.min.js
180 ms
local.min.js
196 ms
logger.min.js
188 ms
entry-factory.min.js
197 ms
console-output-handler.min.js
198 ms
formatter.min.js
209 ms
message-pool.min.js
204 ms
levels-pool.min.js
216 ms
logger-utils.min.js
221 ms
async.min.js
222 ms
registry.min.js
223 ms
loader.min.js
229 ms
slider.min.js
240 ms
main.min.js
242 ms
misc-mixin.min.js
250 ms
calendar.min.js
251 ms
moment.min.js
266 ms
spectrum.min.js
270 ms
tinycolor.min.js
297 ms
datepicker.min.js
273 ms
jquery.cookie.min.js
237 ms
jquery.storageapi.min.js
239 ms
js-translation.json
219 ms
entry.min.js
196 ms
template.min.js
189 ms
dom-observer.min.js
155 ms
bindings.min.js
162 ms
arrays.min.js
116 ms
compare.min.js
133 ms
misc.min.js
132 ms
objects.min.js
134 ms
strings.min.js
135 ms
modal-popup.html
101 ms
bootstrap-datepicker.min.js
74 ms
modal-slide.html
78 ms
modal-custom.html
74 ms
modal-popup.html
69 ms
MutationObserver.min.js
45 ms
FormData.min.js
39 ms
tooltip.html
20 ms
print.css
25 ms
buckheadblooms.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
Links do not have a discernible name
buckheadblooms.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
buckheadblooms.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 Buckheadblooms.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 Buckheadblooms.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.
buckheadblooms.com
Open Graph description is not detected on the main page of Buckhead Blooms. 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: