4.4 sec in total
737 ms
3.3 sec
359 ms
Click here to check amazing Floramedia content for Netherlands. Otherwise, check out these important facts you probably never knew about floramedia.com
Floramedia partners with horticultural customers Europe-wide to develop creative media solutions across all channels.
Visit floramedia.comWe analyzed Floramedia.com page load time and found that the first response time was 737 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
floramedia.com performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value7.5 s
4/100
25%
Value9.5 s
12/100
10%
Value260 ms
83/100
30%
Value0.001
100/100
15%
Value7.8 s
44/100
10%
737 ms
160 ms
180 ms
180 ms
182 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 92% of them (68 requests) were addressed to the original Floramedia.com, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Floramedia.com.
Page size can be reduced by 1.9 MB (43%)
4.4 MB
2.5 MB
In fact, the total size of Floramedia.com main page is 4.4 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. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 75.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 75.5 kB or 83% of the original size.
Potential reduce by 6.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. Floramedia images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 79% of the original size.
Potential reduce by 761.1 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. Floramedia.com needs all CSS files to be minified and compressed as it can save up to 761.1 kB or 87% of the original size.
Number of requests can be reduced by 46 (73%)
63
17
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floramedia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.floramedia.com
737 ms
language-selector.css
160 ms
styles.css
180 ms
everslider.css
180 ms
templates.css
182 ms
style.css
361 ms
mediaelementplayer.min.css
182 ms
wp-mediaelement.css
240 ms
rgs.css
242 ms
font-awesome.min.css
244 ms
style.css
248 ms
prettyPhoto.css
260 ms
responsive.css
328 ms
fm-shop-picker.css
322 ms
js_composer.min.css
336 ms
css
28 ms
jquery.js
419 ms
jquery-migrate.min.js
347 ms
modernizr.js
401 ms
ProgressCircle.min.js
403 ms
Chart.min.js
469 ms
core.min.js
478 ms
widget.min.js
477 ms
position.min.js
496 ms
menu.min.js
499 ms
autocomplete.min.js
499 ms
wpss-search-suggest.js
497 ms
jquery.form.min.js
498 ms
scripts.js
498 ms
jquery.easing.1.3.js
562 ms
jquery.mousewheel.js
559 ms
jquery.everslider.min.js
562 ms
templates.js
562 ms
nicescroll.js
567 ms
prettyPhoto.js
566 ms
superfish.js
639 ms
init.js
810 ms
infinitescroll.js
640 ms
mediaelement-and-player.min.js
549 ms
wp-mediaelement.js
552 ms
nectar-slider.js
561 ms
comment-reply.min.js
616 ms
fm-shop-picker.js
619 ms
slider-fix.js
567 ms
wp-embed.min.js
578 ms
sitepress.js
581 ms
js_composer_front.min.js
633 ms
wp-emoji-release.min.js
624 ms
analytics.js
6 ms
collect
160 ms
en.png
376 ms
logo.png
401 ms
logo_retina.png
711 ms
www.floramedia.com
993 ms
loading-white-bg.gif
714 ms
arrow487.png
679 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
20 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
19 ms
fontawesome-webfont.svg
675 ms
icomoon.woff
672 ms
collect
55 ms
diagonal_line.png
83 ms
slider-1.jpg
1136 ms
grid.png
85 ms
slider-3.2.jpg
512 ms
slidehome-multimedia3.jpg
620 ms
slidehome-sustainability2.jpg
324 ms
slider-2.21.jpg
763 ms
Sovba_Regular-webfont.woff
387 ms
OpenSans-Regular-webfont.woff
350 ms
OpenSans-Light-webfont.woff
432 ms
OpenSans-Semibold-webfont.woff
468 ms
OpenSansBold-webfont.woff
515 ms
fontawesome-webfont.woff
544 ms
floramedia.com 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
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.
floramedia.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
floramedia.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Floramedia.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 Floramedia.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.
floramedia.com
Open Graph description is not detected on the main page of Floramedia. 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: