3.8 sec in total
1.1 sec
2.4 sec
251 ms
Click here to check amazing Merriweather S Flowers content. Otherwise, check out these important facts you probably never knew about merriweathersflowers.com
Sophisticated, custom floral design for events and every day serving Boston and points south.
Visit merriweathersflowers.comWe analyzed Merriweathersflowers.com page load time and found that the first response time was 1.1 sec and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
merriweathersflowers.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value9.0 s
1/100
25%
Value6.3 s
42/100
10%
Value3,320 ms
2/100
30%
Value0.054
98/100
15%
Value18.2 s
3/100
10%
1117 ms
59 ms
95 ms
117 ms
119 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Merriweathersflowers.com, 90% (119 requests) were made to Assets.floranext.com and 9% (12 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 Merriweathersflowers.com.
Page size can be reduced by 93.6 kB (23%)
409.5 kB
315.8 kB
In fact, the total size of Merriweathersflowers.com main page is 409.5 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. 50% of websites need less resources to load. Javascripts take 196.7 kB which makes up the majority of the site volume.
Potential reduce by 82.6 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 11.9 kB, which is 13% 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 82.6 kB or 88% of the original size.
Potential reduce by 11.1 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 12 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. Merriweathersflowers.com has all CSS files already compressed.
Number of requests can be reduced by 102 (83%)
123
21
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Merriweather S Flowers. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 103 to 1 for JavaScripts and as a result speed up the page load time.
merriweathersflowers.com
1117 ms
styles-m.css
59 ms
styles-l.css
95 ms
require.min.js
117 ms
requirejs-min-resolver.min.js
119 ms
mixins.min.js
115 ms
requirejs-config.min.js
117 ms
x800_1426014155_logo.jpg.webp
377 ms
jquery.min.js
19 ms
common.min.js
18 ms
dataPost.min.js
31 ms
bootstrap.min.js
30 ms
app.min.js
17 ms
form-key-provider.min.js
34 ms
mage-translation-dictionary.min.js
38 ms
theme.min.js
33 ms
opensans-400.woff
41 ms
opensans-300.woff
40 ms
opensans-600.woff
36 ms
opensans-700.woff
59 ms
logo-basic-floranext-black.webp
40 ms
0.27085900_1599161932.jpeg.webp
21 ms
0.75143500_1599161941.jpeg.webp
19 ms
0.12474700_1599161951.jpeg.webp
20 ms
designerschoice_1.jpg.webp
273 ms
img_9199_1.jpg.webp
360 ms
screen_shot_2021-03-10_at_4.08.29_pm_1.png.webp
417 ms
screen_shot_2021-03-25_at_3.45.35_pm_1_1.png.webp
371 ms
screen_shot_2020-09-03_at_3.02.55_pm_1.png.webp
384 ms
screen_shot_2020-09-03_at_1.54.46_pm_1.png.webp
539 ms
img_1562_1_1.jpg.webp
669 ms
img_4755_1.jpg.webp
565 ms
Lato-Regular.woff
42 ms
domReady.min.js
50 ms
jquery-mixin.min.js
45 ms
jquery-migrate.min.js
36 ms
main.min.js
36 ms
bootstrap.min.js
36 ms
template.min.js
47 ms
confirm.min.js
38 ms
widget.min.js
47 ms
types.min.js
51 ms
layout.min.js
49 ms
smart-keyboard-handler.min.js
45 ms
mage.min.js
52 ms
ie-class-fixer.min.js
67 ms
text.min.js
75 ms
wrapper.min.js
40 ms
underscore.min.js
31 ms
knockout.min.js
36 ms
knockout-es5.min.js
35 ms
translate.min.js
75 ms
modal.min.js
73 ms
scripts.min.js
74 ms
engine.min.js
74 ms
bootstrap.min.js
70 ms
bootstrap.min.js
72 ms
observable_array.min.js
98 ms
bound-nodes.min.js
73 ms
main.min.js
64 ms
registry.min.js
65 ms
version.min.js
87 ms
console-logger.min.js
85 ms
flora-base-icons.woff
37 ms
Blank-Theme-Icons.woff
39 ms
knockout-repeat.min.js
32 ms
knockout-fast-foreach.min.js
31 ms
key-codes.min.js
31 ms
core.min.js
39 ms
z-index.min.js
45 ms
autocomplete.min.js
37 ms
events.min.js
33 ms
renderer.min.js
49 ms
resizable.min.js
41 ms
i18n.min.js
65 ms
scope.min.js
62 ms
range.min.js
84 ms
mage-init.min.js
80 ms
keyboard.min.js
105 ms
optgroup.min.js
98 ms
after-render.min.js
123 ms
autoselect.min.js
123 ms
datepicker.min.js
142 ms
outer_click.min.js
137 ms
fadeVisible.min.js
162 ms
collapsible.min.js
159 ms
staticChecked.min.js
180 ms
simple-checked.min.js
174 ms
bind-html.min.js
187 ms
tooltip.min.js
197 ms
observable_source.min.js
202 ms
arrays.min.js
215 ms
compare.min.js
218 ms
misc.min.js
235 ms
objects.min.js
237 ms
strings.min.js
247 ms
local.min.js
248 ms
template.min.js
264 ms
logger.min.js
267 ms
entry-factory.min.js
262 ms
console-output-handler.min.js
283 ms
formatter.min.js
276 ms
message-pool.min.js
275 ms
levels-pool.min.js
272 ms
logger-utils.min.js
282 ms
data.min.js
270 ms
disable-selection.min.js
262 ms
focusable.min.js
256 ms
form.min.js
241 ms
ie.min.js
233 ms
keycode.min.js
244 ms
labels.min.js
240 ms
jquery-patch.min.js
214 ms
plugin.min.js
210 ms
safe-active-element.min.js
200 ms
safe-blur.min.js
202 ms
scroll-parent.min.js
203 ms
tabbable.min.js
199 ms
unique-id.min.js
184 ms
async.min.js
174 ms
loader.min.js
169 ms
class.min.js
165 ms
js-translation.json
380 ms
entry.min.js
93 ms
modal-popup.html
380 ms
modal-custom.html
368 ms
moment.min.js
90 ms
modal-slide.html
382 ms
dom-observer.min.js
43 ms
bindings.min.js
57 ms
tooltip.html
291 ms
print.css
16 ms
merriweathersflowers.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
merriweathersflowers.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
merriweathersflowers.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 Merriweathersflowers.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 Merriweathersflowers.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.
merriweathersflowers.com
Open Graph description is not detected on the main page of Merriweather S Flowers. 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: