9.7 sec in total
1.1 sec
7.6 sec
954 ms
Visit thriveflowers.com.au now to see the best up-to-date Thrive Flowers content and also check out these interesting facts you probably never knew about thriveflowers.com.au
Find the perfect wedding flowers in Melbourne at Thrive Flowers. Our talented florists specialise in creating stunning floral arrangements.
Visit thriveflowers.com.auWe analyzed Thriveflowers.com.au page load time and found that the first response time was 1.1 sec and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
thriveflowers.com.au performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value21.6 s
0/100
25%
Value16.8 s
0/100
10%
Value1,040 ms
25/100
30%
Value0.004
100/100
15%
Value21.2 s
1/100
10%
1077 ms
3438 ms
39 ms
49 ms
42 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 94% of them (98 requests) were addressed to the original Thriveflowers.com.au, 2% (2 requests) were made to Googletagmanager.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Thriveflowers.com.au.
Page size can be reduced by 653.7 kB (12%)
5.7 MB
5.0 MB
In fact, the total size of Thriveflowers.com.au main page is 5.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.2 MB which makes up the majority of the site volume.
Potential reduce by 440.0 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 440.0 kB or 91% of the original size.
Potential reduce by 213.7 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. Thrive Flowers images are well optimized though.
Number of requests can be reduced by 71 (74%)
96
25
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thrive 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 41 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
thriveflowers.com.au
1077 ms
thriveflowers.com.au
3438 ms
style-index.css
39 ms
jquery-ui.css
49 ms
datepicker.css
42 ms
address-form.css
39 ms
style.css
41 ms
woocommerce-layout.css
49 ms
woocommerce.css
55 ms
style.css
70 ms
gateway.css
79 ms
style.min.css
76 ms
theme.min.css
68 ms
header-footer.min.css
80 ms
elementor-icons.min.css
97 ms
custom-frontend-lite.min.css
104 ms
swiper.min.css
76 ms
custom-pro-frontend-lite.min.css
86 ms
all.min.css
81 ms
v4-shims.min.css
92 ms
style.min.css
112 ms
font-awesome.min.css
119 ms
general.min.css
101 ms
css
36 ms
fontawesome.min.css
113 ms
solid.min.css
118 ms
brands.min.css
125 ms
thriveflowers.com.au
821 ms
jquery.min.js
142 ms
jquery-migrate.min.js
135 ms
core.min.js
154 ms
select2.min.js
146 ms
datepicker.min.js
161 ms
jquery.ui.datepicker-en-GB.js
175 ms
jquery.blockUI.min.js
175 ms
add-to-cart.min.js
186 ms
js.cookie.min.js
182 ms
woocommerce.min.js
183 ms
js
66 ms
js
129 ms
custom-pro-widget-nav-menu.min.css
204 ms
widget-woocommerce.min.css
200 ms
v4-shims.min.js
201 ms
Oe1yEoBr5XYf
127 ms
custom-widget-icon-list.min.css
55 ms
wc-blocks.css
66 ms
photoswipe.min.css
72 ms
default-skin.min.css
110 ms
accessibility.js
84 ms
sourcebuster.min.js
77 ms
order-attribution.min.js
92 ms
button.js
110 ms
hello-frontend.min.js
101 ms
happy-addons.min.js
115 ms
general.min.js
124 ms
jquery.sticky.min.js
121 ms
jquery.smartmenus.min.js
133 ms
cart-fragments.min.js
158 ms
webpack-pro.runtime.min.js
142 ms
webpack.runtime.min.js
142 ms
frontend-modules.min.js
154 ms
hooks.min.js
159 ms
i18n.min.js
177 ms
frontend.min.js
161 ms
waypoints.min.js
184 ms
frontend.min.js
194 ms
elements-handlers.min.js
190 ms
jquery.zoom.min.js
181 ms
jquery.flexslider.min.js
199 ms
photoswipe.min.js
202 ms
photoswipe-ui-default.min.js
234 ms
underscore.min.js
198 ms
wp-util.min.js
216 ms
add-to-cart-variation.min.js
228 ms
single-product.min.js
199 ms
cropped-thrive-1024x292.png
784 ms
thrive-1024x512.png
749 ms
cropped-thrive.png
72 ms
home-banner-1200x600px-1.png
71 ms
thrive-alyssa-and-rosie.png
74 ms
flowers-for-weddings-400x400px.png
73 ms
flowers-for-corporate-400x400px.png
86 ms
flowers-for-events-400x400px.png
75 ms
Untitled-design-51.png
113 ms
Header-Flower-School-1.jpg
114 ms
workshop-3-1-1536x1437-1.jpg
1568 ms
Women-fixing-flowers.jpg
189 ms
workshop-1.jpg
1917 ms
workshops-2-400x400px.png
1725 ms
workshop-5-scaled-1.jpg
2377 ms
3f427c2d-8347-479b-8b3e-f779dfdcfb51.png
783 ms
car.jpg
816 ms
2-1.png
808 ms
1.png
832 ms
font
42 ms
Optima-Pro-Bold.ttf
776 ms
Optima-Pro-Medium.ttf
792 ms
fa-solid-900.woff
803 ms
fa-regular-400.woff
823 ms
eicons.woff
2014 ms
preview-review
735 ms
fa-brands-400.woff
806 ms
thriveflowers.com.au
2157 ms
woocommerce-smallscreen.css
29 ms
thriveflowers.com.au 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
ARIA IDs are not unique
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
thriveflowers.com.au best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
thriveflowers.com.au SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thriveflowers.com.au 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 Thriveflowers.com.au 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.
thriveflowers.com.au
Open Graph data is detected on the main page of Thrive Flowers. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: