4.8 sec in total
451 ms
4 sec
328 ms
Welcome to interflora.no homepage info - get ready to check Interflora best content for Norway right away, or after learning these important things about interflora.no
Bestill blomster til noen du tenker på, vi leverer fra nærmeste Interflora blomsterbutikk. Vi hjelper deg med å gratulere, feire og vise omtanke.
Visit interflora.noWe analyzed Interflora.no page load time and found that the first response time was 451 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
interflora.no performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value13.8 s
0/100
25%
Value8.0 s
22/100
10%
Value450 ms
62/100
30%
Value0.206
60/100
15%
Value10.5 s
23/100
10%
451 ms
804 ms
134 ms
32 ms
51 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 26% of them (14 requests) were addressed to the original Interflora.no, 28% (15 requests) were made to D3fv9dok5w8tbc.cloudfront.net and 19% (10 requests) were made to Img5.custompublish.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Img5.custompublish.com.
Page size can be reduced by 184.7 kB (17%)
1.1 MB
889.0 kB
In fact, the total size of Interflora.no main page is 1.1 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. 65% of websites need less resources to load. Images take 542.8 kB which makes up the majority of the site volume.
Potential reduce by 52.3 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 52.3 kB or 73% of the original size.
Potential reduce by 5.5 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. Interflora images are well optimized though.
Potential reduce by 124.0 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 124.0 kB or 30% of the original size.
Potential reduce by 2.9 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. Interflora.no has all CSS files already compressed.
Number of requests can be reduced by 33 (72%)
46
13
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Interflora. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
interflora.no
451 ms
www.interflora.no
804 ms
uc.js
134 ms
icon
32 ms
css2
51 ms
animate.css
36 ms
lightgallery.min.css
65 ms
lightslider.min.css
66 ms
jquery.fullpage.min.css
562 ms
jquery-ui.css
58 ms
motion-ui.min.css
60 ms
cookieinfo-interflora.css
219 ms
28280.1285.css
454 ms
29488.1285.css
353 ms
jquery.js
602 ms
jquery-ui.js
58 ms
shop4jq.js
77 ms
lightgallery.min.js
88 ms
lightslider.min.js
63 ms
jquery.fullpage.js
84 ms
scrolloverflow.min.js
65 ms
ls.respimg.min.js
69 ms
lazysizes.min.js
70 ms
jquery.imagesloaded.min.js
70 ms
custom2017v2.js
570 ms
cpcommon.css
379 ms
cpcommon.js.php
390 ms
cookieinfo-interflora.js
466 ms
what-input.min.js
401 ms
foundation.min.js
616 ms
customization.js
459 ms
1.2.2
34 ms
afwstats.js.php
468 ms
gtm.js
57 ms
lipscore-v1.js
34 ms
lipscore-v1.css
11 ms
hotjar-3621471.js
90 ms
modules.842bcec28f9fd12bb79e.js
14 ms
sok.svg
659 ms
profil.svg
645 ms
handlekurv.svg
656 ms
levering.svg
658 ms
verden.svg
662 ms
butikk.svg
714 ms
etiskhandel_logo_580x390.jpg
960 ms
FSI+logo.png
979 ms
miljfyrtarn-norsk-farger.png
980 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
123 ms
KFOmCnqEu92Fr1Me5Q.ttf
180 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
195 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvUDQ.ttf
195 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vUDQ.ttf
195 ms
flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf
196 ms
vaar_2024_banner.jpg
1492 ms
interflora.no 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
Links do not have a discernible name
interflora.no 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
interflora.no SEO score
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
NO
NO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Interflora.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it matches the claimed language. Our system also found out that Interflora.no 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.
interflora.no
Open Graph description is not detected on the main page of Interflora. 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: