3 sec in total
311 ms
2 sec
652 ms
Click here to check amazing Edible Blooms content for New Zealand. Otherwise, check out these important facts you probably never knew about edibleblooms.co.nz
Edible Blooms gifts are seriously stand out. They’re unlike anything else. We have been delivering deliciously different gifts across New Zealand for more than 10 years. We don't do boring, we gif...
Visit edibleblooms.co.nzWe analyzed Edibleblooms.co.nz page load time and found that the first response time was 311 ms 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.
edibleblooms.co.nz performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value21.8 s
0/100
25%
Value15.8 s
0/100
10%
Value5,700 ms
0/100
30%
Value0.001
100/100
15%
Value31.9 s
0/100
10%
311 ms
100 ms
173 ms
73 ms
65 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 40% of them (34 requests) were addressed to the original Edibleblooms.co.nz, 11% (9 requests) were made to Cdn.shopify.com and 6% (5 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (612 ms) belongs to the original domain Edibleblooms.co.nz.
Page size can be reduced by 368.7 kB (17%)
2.2 MB
1.8 MB
In fact, the total size of Edibleblooms.co.nz main page is 2.2 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. 70% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 197.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 197.2 kB or 78% of the original size.
Potential reduce by 2.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. Edible Blooms images are well optimized though.
Potential reduce by 168.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 168.2 kB or 16% of the original size.
Potential reduce by 469 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. Edibleblooms.co.nz has all CSS files already compressed.
Number of requests can be reduced by 60 (74%)
81
21
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edible 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 48 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
edibleblooms.co.nz
311 ms
uploadery.js
100 ms
js
173 ms
connect.js
73 ms
preloads.js
65 ms
load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js
54 ms
features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js
53 ms
theme.scss.css
52 ms
lazysizes.min.js
52 ms
polyfill.min.js
375 ms
libs.min.js
74 ms
theme.min.js
95 ms
custom.js
79 ms
jquery-ui.css
60 ms
jquery.min.js
71 ms
jquery-ui.min.js
79 ms
bootstrap.bundle.min.js
74 ms
bootstrap.min.css
94 ms
storepickup.js
83 ms
pickup.js
185 ms
shipping.js
203 ms
klaviyo.js
360 ms
inbox-chat-loader.js
190 ms
pagefly.js
309 ms
lb-upsell.js
208 ms
shopify-perf-kit-1.0.0.min.js
74 ms
embed.js
87 ms
ZooomyAgeVerify.js
214 ms
lb-upsell-components.esm.js
206 ms
shopify-afterpay-javascript.js
67 ms
gtm.js
205 ms
gtm.js
206 ms
obtp.js
107 ms
gadget.js
164 ms
widget.js
369 ms
widget.js
436 ms
storepickup.css
77 ms
trekkie.storefront.4a011e6f7849be6d184f3092d081171f1a657b4e.min.js
84 ms
shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js
84 ms
shopify-boomerang-1.0.0.min.js
81 ms
af-footer.png
84 ms
EdibleBlooms_UKWebLogo-01_350x.jpg
86 ms
ChocolateBouquets_CategoryBanner_2_1x1.jpg
37 ms
BirthdayGifts_CategoryBanner_4_1_1x1.jpg
84 ms
GiftHampers_CategoryBanner_2_1x1.jpg
37 ms
Fruit_Donuts_CategoryBanner_1_1x1.jpg
305 ms
embed
275 ms
779_2_1x1.jpg
61 ms
276244770_10158531972777653_6083009328634430938_n_1x1.jpg
59 ms
59664_1_1x1.jpg
60 ms
storage.html
47 ms
montserrat_n5.18a018b6c83e89030c5d70a6d4c02c969f228500.woff
53 ms
moment.min.js
79 ms
moment-timezone-with-data-1970-2030.min.js
167 ms
ZooomyAgeVerify.php
100 ms
js
114 ms
editor.css
79 ms
ChocolateBouquets_CategoryBanner_2_1800x.jpg
209 ms
widget.css
291 ms
779_2_1500x.jpg
342 ms
js
16 ms
search.js
4 ms
geometry.js
9 ms
main.js
12 ms
open_sans.css
24 ms
widget.js
245 ms
lb-upsell-wrapper.js
49 ms
app.min.js
71 ms
gipht-button.js
93 ms
lo.js
50 ms
ISvpkjpgdT5AY6mRdkjDtDop22dFOuk3035s90ec
58 ms
doofinder-installed.js
146 ms
lmCKI7
155 ms
FlowerDonutBouquetMedium1_400x.jpg
236 ms
FlowerDonutBouquetMedium_400x.png
387 ms
BrightFlowerBouquetMediumside_400x.jpg
325 ms
BrightFlowerBouquetMedium_400x.jpg
360 ms
LOVE_Red_Bouquet_Small_8994cf4f-807e-4642-b51c-3ab6e7ca3b85_400x.png
381 ms
99201_400x.jpg
222 ms
NZ_ManlyGiftHamper_Herocraftbeer1_e7bbcc39-4a87-4a41-96b8-e67872e759ba_400x.jpg
584 ms
NZ_ManlyGiftHamper_Herocraftbeer1_400x.jpg
512 ms
birthdaybadge_crownandbouquet_626a76db-c6f2-4e44-92af-9f186102eee7_400x.jpg
612 ms
BestBirthdayCakeAndBouquetGiftHamper_Hero24_400x.jpg
397 ms
css
33 ms
edibleblooms.co.nz accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
edibleblooms.co.nz 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
edibleblooms.co.nz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Edibleblooms.co.nz 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 Edibleblooms.co.nz 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.
edibleblooms.co.nz
Open Graph data is detected on the main page of Edible Blooms. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: