7.2 sec in total
856 ms
6.2 sec
142 ms
Visit grandiflora.net now to see the best up-to-date Grandiflora content for Australia and also check out these interesting facts you probably never knew about grandiflora.net
At Grandiflora we provide flowers for all occasions across Sydney CBD, Eastern Suburbs & Northern beaches. Learn more
Visit grandiflora.netWe analyzed Grandiflora.net page load time and found that the first response time was 856 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
grandiflora.net performance score
name
value
score
weighting
Value12.9 s
0/100
10%
Value26.2 s
0/100
25%
Value36.6 s
0/100
10%
Value430 ms
64/100
30%
Value0.01
100/100
15%
Value21.0 s
1/100
10%
856 ms
252 ms
21 ms
499 ms
501 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 59% of them (26 requests) were addressed to the original Grandiflora.net, 18% (8 requests) were made to and 9% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Grandiflora.net.
Page size can be reduced by 279.7 kB (19%)
1.5 MB
1.2 MB
In fact, the total size of Grandiflora.net main page is 1.5 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. 25% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 6.5 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 6.5 kB or 70% of the original size.
Potential reduce by 116.2 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, Grandiflora needs image optimization as it can save up to 116.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 81.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 81.8 kB or 58% of the original size.
Potential reduce by 75.2 kB
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. Grandiflora.net needs all CSS files to be minified and compressed as it can save up to 75.2 kB or 33% of the original size.
Number of requests can be reduced by 9 (28%)
32
23
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grandiflora. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
grandiflora.net
856 ms
fonts.css
252 ms
slick.css
21 ms
layout.css
499 ms
morph.css
501 ms
jquery-1.11.0.min.js
1258 ms
jquery.cycle2.min.js
748 ms
slick.min.js
27 ms
runtime.js
500 ms
vzt4wya.js
143 ms
91B81C7AA35145C8E.css
1791 ms
ga.js
38 ms
565c032c2a887.jpg
1263 ms
565bffed7515f.jpg
1275 ms
565c00271f114.jpg
1521 ms
565c001a0ed28.jpg
1276 ms
565bffd352dc6.jpg
1280 ms
565bffe115dbe.jpg
1522 ms
565c033e65e1c.jpg
3273 ms
grandiflora_b.png
2021 ms
grandiflora_w.png
2038 ms
in_w.png
1777 ms
in_b.png
2018 ms
fb_w.png
2020 ms
fb_b.png
2276 ms
tw_w.png
2529 ms
tw_b.png
2518 ms
pi_w.png
2518 ms
pi_b.png
2536 ms
ml_w.png
2773 ms
ml_b.png
3015 ms
grandiflora.net
184 ms
B53zvlpaonBj4ts8dEhy2Ml1c5r+rs8NuofgGu2DVw
7 ms
IndNc3AA==
7 ms
i875zyUlUjA58U6VOiwxbGy6ucV3V6+G2UvwFfGTVc
7 ms
EHdFjDwX8vT2rwxj6RnEjxpJvERzuuA3okCe6gYrlK3i965zyUlUjA58U6UOgwyzGpwc6D+z08PsofwFU2Tb4
6 ms
hFeVEn3tlJ0qfBHMi2AuCuZYJ+U06bnp1e3hDd7cvoVFnhcxP4viTN6LBMrsEa8MTkjUwv2oPhHPQ08TFPDXelaFMQyt4jFMDd8iONzxENAhb3IDNYtX8HnfO+WlqicGPi2zx0SHLYyXVzmv6uzw26h+Aa7YNXA=
6 ms
yalIf4uvLCT6yik71vgimRfJPCGZU6UU46yntpeb4xu82byFeZblM37m+YXMj1Io0ge8IjghUQv3vfxIPBE9zlDAH+tFHc6gbxQPYmz5DsHhnseADnmjG6hYvoLPu84pL1U1MvBJkT4kOu5ifHyh88JOj7+P8id01zcA
6 ms
i875zyUlUjA58U6VOiwxbGy6ucV3V6+G2UvwFfGTVc
6 ms
AVTZNvg=
6 ms
__utm.gif
20 ms
yY2JejdAnvtNRNf25j21o8VreeL4zToVVw4WoFMLZ1wff5WyggMdeMJ6Mk6g5Mofb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
56 ms
hn7YgK8-3HMllBD1agFcVNCeQn0MUXo_TVcUe7iFC5Iff5LyggMdeMJ6Mk6g5MZfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
110 ms
p.gif
125 ms
grandiflora.net 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
Image elements do not have [alt] attributes
grandiflora.net 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
grandiflora.net 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
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grandiflora.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Grandiflora.net 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.
grandiflora.net
Open Graph description is not detected on the main page of Grandiflora. 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: