7 sec in total
1.5 sec
5.2 sec
343 ms
Welcome to windowflowers.com homepage info - get ready to check Windowflowers best content right away, or after learning these important things about windowflowers.com
Windowboxes, Corporate Cut Flowers, Office Plants & Hanging Baskets. Largest independent comprehensive supplier of Corporate Horticultural Services to the commercial sector.
Visit windowflowers.comWe analyzed Windowflowers.com page load time and found that the first response time was 1.5 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
windowflowers.com performance score
name
value
score
weighting
Value12.5 s
0/100
10%
Value16.1 s
0/100
25%
Value14.3 s
1/100
10%
Value110 ms
97/100
30%
Value0.051
99/100
15%
Value16.1 s
6/100
10%
1471 ms
155 ms
472 ms
339 ms
334 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 83% of them (83 requests) were addressed to the original Windowflowers.com, 9% (9 requests) were made to Fonts.googleapis.com and 5% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Windowflowers.com.
Page size can be reduced by 1.7 MB (35%)
4.9 MB
3.2 MB
In fact, the total size of Windowflowers.com main page is 4.9 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. 55% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 67.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 67.5 kB or 81% of the original size.
Potential reduce by 120.1 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. Windowflowers images are well optimized though.
Potential reduce by 567.9 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 567.9 kB or 75% of the original size.
Potential reduce by 957.5 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. Windowflowers.com needs all CSS files to be minified and compressed as it can save up to 957.5 kB or 85% of the original size.
Number of requests can be reduced by 59 (64%)
92
33
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Windowflowers. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
windowflowers.com
1471 ms
wp-emoji-release.min.js
155 ms
style.min.css
472 ms
cleantalk-public.min.css
339 ms
styles.css
334 ms
style.css
339 ms
single-team-member.css
340 ms
fontawesome.css
508 ms
fa-brands.css
456 ms
fa-solid.css
457 ms
fa-regular.css
456 ms
font-awesome.min.css
592 ms
elegant-icons.css
678 ms
genericons.css
694 ms
front-end.css
1185 ms
jquery-ui.css
609 ms
animate.css
669 ms
owl.carousel.css
715 ms
owl.theme.default.min.css
726 ms
jquery.flipster.min.css
792 ms
jquery.mCustomScrollbar.css
899 ms
colorbox.css
813 ms
dashicons.min.css
974 ms
css
44 ms
prettyPhoto.css
857 ms
style.css
1204 ms
jquery.min.js
1104 ms
jquery-migrate.min.js
979 ms
apbct-public-bundle.min.js
1147 ms
scripts.js
1089 ms
masonry.pkgd.min.js
1108 ms
core.min.js
1222 ms
mouse.min.js
1221 ms
slider.min.js
1288 ms
frontend.js
1270 ms
simple-skillbar.js
1318 ms
owl.carousel.js
1317 ms
js
77 ms
iframe_api
60 ms
owl.animate.js
1335 ms
owl.autoplay.js
1194 ms
owl.navigation.js
1064 ms
isotope.pkgd.js
1142 ms
jquery.flipster.js
1081 ms
jquery.mCustomScrollbar.concat.min.js
1109 ms
jquery.colorbox.js
1022 ms
index.js
1017 ms
index.js
1100 ms
imagesloaded.min.js
1085 ms
underscore.min.js
1081 ms
main.js
1233 ms
content-slider.js
1000 ms
comment-reply.min.js
929 ms
css
31 ms
css
48 ms
css
49 ms
css
48 ms
css
64 ms
css
65 ms
css
110 ms
css
77 ms
windowflowers_logo.png
146 ms
instagram.png
187 ms
twitter.png
200 ms
facebook.png
222 ms
linkedin.png
230 ms
flower-130x130.png
262 ms
out-planting-130x130.png
300 ms
in-planting-130x130.png
320 ms
events-130x130.png
400 ms
about-130x130.png
403 ms
gallery-130x130.png
404 ms
team-130x130.png
414 ms
contact-130x130.png
432 ms
020-586x349.jpg
492 ms
House-Of-Commons363.jpgdocid1772021-586x349.jpg
468 ms
CH-Frontage-4-586x349.jpg
587 ms
290720091075-586x349.jpg
525 ms
IMG_3346-586x349.jpg
532 ms
For-RBKC-586x349.jpg
577 ms
108-586x349.jpg
664 ms
px_sprites_w.png
619 ms
2016-Safecontractor.png
665 ms
Plants@work-v1.png
663 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
20 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
34 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
41 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf
51 ms
PexetoIcons.woff
682 ms
PexetoArrows.woff
665 ms
www-widgetapi.js
67 ms
overlay.png
343 ms
Roses-wallpaper.jpg
381 ms
cs-loader-w.gif
381 ms
Exterior-Plants.jpg
560 ms
interior-plants-pexel.jpg
800 ms
wedding-pexels-1.jpg
605 ms
Sending-flowers-pexels.jpg
734 ms
events-and-seasonal-1.jpg
554 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
5 ms
windowflowers.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
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.
windowflowers.com 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
windowflowers.com 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
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 Windowflowers.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 Windowflowers.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.
windowflowers.com
Open Graph data is detected on the main page of Windowflowers. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: