3.8 sec in total
734 ms
2.8 sec
345 ms
Click here to check amazing Burke Florist content. Otherwise, check out these important facts you probably never knew about burkeflorist.com
Burke Florist is a family owned shop in Fairfax, VA that creates beautiful unique floral arrangements for delivery. We are located in University Mall across from GMU.
Visit burkeflorist.comWe analyzed Burkeflorist.com page load time and found that the first response time was 734 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
burkeflorist.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value8.2 s
2/100
25%
Value7.6 s
26/100
10%
Value1,750 ms
10/100
30%
Value0.236
53/100
15%
Value17.5 s
4/100
10%
734 ms
39 ms
73 ms
61 ms
101 ms
Our browser made a total of 158 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Burkeflorist.com, 83% (131 requests) were made to Assets.floranext.com and 12% (19 requests) were made to Image.floranext.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Image.floranext.com.
Page size can be reduced by 133.1 kB (22%)
600.4 kB
467.3 kB
In fact, the total size of Burkeflorist.com main page is 600.4 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. 65% of websites need less resources to load. Javascripts take 303.5 kB which makes up the majority of the site volume.
Potential reduce by 116.9 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 15.3 kB, which is 12% 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 116.9 kB or 88% of the original size.
Potential reduce by 5.6 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. Obviously, Burke Florist needs image optimization as it can save up to 5.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 9.8 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 862 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. Burkeflorist.com has all CSS files already compressed.
Number of requests can be reduced by 123 (82%)
150
27
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Burke Florist. 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.
burkeflorist.com
734 ms
calendar.css
39 ms
styles-m.css
73 ms
styles-l.css
61 ms
require.min.js
101 ms
requirejs-min-resolver.min.js
101 ms
mixins.min.js
99 ms
requirejs-config.min.js
104 ms
polyfill.min.js
109 ms
x800_1532458085_0.12761400_1532458084.jpeg
539 ms
jquery.mobile.custom.min.js
26 ms
common.min.js
25 ms
dataPost.min.js
29 ms
bootstrap.min.js
26 ms
jquery.min.js
41 ms
translate-inline.min.js
27 ms
mage-translation-dictionary.min.js
97 ms
PRHQdW5lSIy2n2WSJSN09A.js
169 ms
js
93 ms
logo-basic-floranext-black.webp
21 ms
8402ddf3-d899-4695-92aa-6716ed804e39.png.webp
787 ms
d2328312-5507-4584-bf7d-88f11bff2551.png.webp
537 ms
44242fbb-f896-44ee-8bea-bffb68cf1a36.png.webp
538 ms
0.42942200_1530820038_1.jpeg.webp
999 ms
0.08150700_1530814924_1.jpeg.webp
939 ms
0.19552100_1530819590_1.jpeg.webp
1020 ms
images_2_1.jpg.webp
966 ms
0.41097100_1530815179_1.jpeg.webp
915 ms
0.35238100_1530815588_1.jpeg.webp
1210 ms
0.21340300_1530827437_1.jpeg.webp
1291 ms
0.75396400_1530828799_1.jpeg.webp
1332 ms
0.69092200_1530815347_1.jpeg.webp
1338 ms
0.68368800_1530815454_1.jpeg.webp
1374 ms
0.47835000_1530828245_1.jpeg.webp
1404 ms
0.71494200_1530818850_1.jpeg.webp
1406 ms
yelp_fullcolor_1.png
1646 ms
2000px-f_icon.svg_1.png
1800 ms
credit1.png
1633 ms
responsive.min.js
76 ms
theme.min.js
77 ms
Lato-Regular.woff
113 ms
domReady.min.js
76 ms
main.min.js
72 ms
bootstrap.min.js
81 ms
jquery.min.js
79 ms
template.min.js
79 ms
translate.min.js
78 ms
confirm.min.js
76 ms
widget.min.js
107 ms
dialog.min.js
104 ms
jquery-ui.min.js
104 ms
jquery-migrate.min.js
79 ms
flora-base-icons.woff
38 ms
Blank-Theme-Icons.woff
39 ms
tabs.min.js
39 ms
text.min.js
37 ms
underscore.min.js
37 ms
smart-keyboard-handler.min.js
74 ms
mage.min.js
75 ms
ie-class-fixer.min.js
75 ms
matchMedia.min.js
69 ms
scripts.min.js
70 ms
knockout.min.js
67 ms
knockout-es5.min.js
68 ms
owl.carousel.min.js
33 ms
engine.min.js
36 ms
bootstrap.min.js
33 ms
bootstrap.min.js
33 ms
bootstrap.min.js
35 ms
observable_array.min.js
34 ms
bound-nodes.min.js
93 ms
modal.min.js
93 ms
modal-mixin.min.js
109 ms
js
99 ms
analytics.js
96 ms
button.min.js
90 ms
draggable.min.js
90 ms
position.min.js
88 ms
resizable.min.js
88 ms
core.min.js
88 ms
collapsible.min.js
152 ms
PRHQdW5lSIy2n2WSJSN09A.js
275 ms
autocomplete.min.js
89 ms
knockout-repeat.min.js
86 ms
knockout-fast-foreach.min.js
86 ms
format.min.js
98 ms
jqueryTooltip.min.js
97 ms
bootstrap-datepicker.min.js
97 ms
renderer.min.js
94 ms
resizable.min.js
93 ms
i18n.min.js
100 ms
scope.min.js
104 ms
range.min.js
99 ms
mage-init.min.js
103 ms
keyboard.min.js
97 ms
optgroup.min.js
114 ms
after-render.min.js
138 ms
autoselect.min.js
118 ms
datepicker.min.js
114 ms
outer_click.min.js
114 ms
fadeVisible.min.js
128 ms
collapsible.min.js
129 ms
staticChecked.min.js
129 ms
simple-checked.min.js
132 ms
bind-html.min.js
140 ms
tooltip.min.js
143 ms
color-picker.min.js
145 ms
wrapper.min.js
145 ms
events.min.js
159 ms
es6-collections.min.js
161 ms
key-codes.min.js
153 ms
observable_source.min.js
154 ms
console-logger.min.js
165 ms
collect
32 ms
mouse.min.js
110 ms
jquery.storageapi.extended.min.js
111 ms
async.min.js
123 ms
registry.min.js
139 ms
moment.min.js
158 ms
loader.min.js
175 ms
main.min.js
194 ms
misc-mixin.min.js
198 ms
datepicker.min.js
214 ms
slider.min.js
210 ms
calendar.min.js
212 ms
spectrum.min.js
198 ms
tinycolor.min.js
216 ms
class.min.js
215 ms
local.min.js
220 ms
logger.min.js
233 ms
entry-factory.min.js
254 ms
console-output-handler.min.js
258 ms
formatter.min.js
269 ms
message-pool.min.js
270 ms
levels-pool.min.js
286 ms
logger-utils.min.js
272 ms
jquery.cookie.min.js
274 ms
jquery.storageapi.min.js
272 ms
PRHQdW5lSIy2n2WSJSN09A.js
92 ms
dom-observer.min.js
252 ms
bindings.min.js
272 ms
js-translation.json
220 ms
arrays.min.js
193 ms
compare.min.js
190 ms
misc.min.js
203 ms
objects.min.js
208 ms
strings.min.js
207 ms
template.min.js
209 ms
bootstrap-datepicker.min.js
209 ms
modal-slide.html
98 ms
modal-popup.html
87 ms
modal-custom.html
82 ms
entry.min.js
83 ms
modal-popup.html
76 ms
MutationObserver.min.js
68 ms
FormData.min.js
41 ms
tooltip.html
18 ms
print.css
17 ms
burkeflorist.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
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>).
burkeflorist.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
burkeflorist.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 Burkeflorist.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 Burkeflorist.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.
burkeflorist.com
Open Graph description is not detected on the main page of Burke Florist. 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: