Tools & Wizards About Us
floralinnea.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

floralinnea.com

Flora Linnea svenskodlade rosor och klematis - Flora Linnea

Page Load Speed

3.7 sec in total

First Response

352 ms

Resources Loaded

3.1 sec

Page Rendered

277 ms

floralinnea.com screenshot

About Website

Click here to check amazing Flora Linnea content. Otherwise, check out these important facts you probably never knew about floralinnea.com

Flora Linneas specialitet är Austinrosor, rosor, klematis, lökar, fröer och trädgårdsartiklar. Vi erbjuder trädgårdsprodukter och trädgårdsredskap, heminredning som möbler, porslin och dekorationer. T...

Visit floralinnea.com

Key Findings

We analyzed Floralinnea.com page load time and found that the first response time was 352 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

floralinnea.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value1,660 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.127

82/100

15%

TTI (Time to Interactive)

Value15.8 s

6/100

10%

Network Requests Diagram

floralinnea.com

352 ms

floralinnea.se

785 ms

vertnav.css

226 ms

ultracart.js

725 ms

css

25 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Floralinnea.com, 70% (30 requests) were made to Floralinnea.se and 12% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Floralinnea.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 83.3 kB (7%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Floralinnea.com 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. 45% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 54.5 kB

  • Original 66.7 kB
  • After minification 56.0 kB
  • After compression 12.2 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. This page needs HTML code to be minified as it can gain 10.7 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 54.5 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 23.3 kB

  • Original 1.0 MB
  • After minification 997.4 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. Flora Linnea images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 5.6 kB

  • Original 25.1 kB
  • After minification 25.1 kB
  • After compression 19.5 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 5.6 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (11%)

Requests Now

35

After Optimization

31

  • Images
  • JavaScript
  • CSS

The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flora Linnea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

floralinnea.com

floralinnea.com

352 ms

floralinnea.se

floralinnea.se

785 ms

vertnav.css

vertnav.css

226 ms

ultracart.js

ultracart.js

725 ms

css

css

25 ms

flora.css

flora.css

319 ms

ga.js

ga.js

23 ms

plusone.js

plusone.js

154 ms

prum.min.js

prum.min.js

44 ms

tracking_image.gif

tracking_image.gif

207 ms

logo.png

logo.png

236 ms

logo.gif

logo.gif

153 ms

nada.png

nada.png

152 ms

flora-linnea_austinrosor.jpg

flora-linnea_austinrosor.jpg

625 ms

flora-linnea_stamrosor.jpg

flora-linnea_stamrosor.jpg

1256 ms

a-shropshire-lad-ausled-austinrosor_700.jpg

a-shropshire-lad-ausled-austinrosor_700.jpg

331 ms

austinrosstart_1.jpg

austinrosstart_1.jpg

339 ms

rosa-helenae-hybrida_1.jpg

rosa-helenae-hybrida_1.jpg

346 ms

jordn_tsmatarewg.jpg

jordn_tsmatarewg.jpg

348 ms

file_13_23.jpg

file_13_23.jpg

540 ms

file_58.jpg

file_58.jpg

555 ms

fl_presentkort_1.jpg

fl_presentkort_1.jpg

458 ms

winchester-cathedral-auscat-austinrosor_700_3.jpg

winchester-cathedral-auscat-austinrosor_700_3.jpg

569 ms

FL_Link_Ros.jpg

FL_Link_Ros.jpg

680 ms

FL_Link_Tulpan.jpg

FL_Link_Tulpan.jpg

750 ms

FL_Link_Klematis.jpg

FL_Link_Klematis.jpg

813 ms

FL_Link_Pase.jpg

FL_Link_Pase.jpg

790 ms

FL_Knapp_Stor_Tradgardstjanst.jpg

FL_Knapp_Stor_Tradgardstjanst.jpg

826 ms

FB-f-Logo__blue_50.png

FB-f-Logo__blue_50.png

791 ms

Pinterest_Favicon_sm.png

Pinterest_Favicon_sm.png

857 ms

YouTube-icon-sm.png

YouTube-icon-sm.png

901 ms

klarna.png

klarna.png

1013 ms

posten.png

posten.png

922 ms

dhl_square.png

dhl_square.png

928 ms

icon_sprite.png

icon_sprite.png

1055 ms

__utm.gif

__utm.gif

35 ms

IczWvq5y_Cwwv_rBjOtT0w.woff

IczWvq5y_Cwwv_rBjOtT0w.woff

8 ms

CcKI4k9un7TZVWzRVT-T8xsxEYwM7FgeyaSgU71cLG0.woff

CcKI4k9un7TZVWzRVT-T8xsxEYwM7FgeyaSgU71cLG0.woff

8 ms

-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff

-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff

31 ms

xkvoNo9fC8O2RDydKj12bxsxEYwM7FgeyaSgU71cLG0.woff

xkvoNo9fC8O2RDydKj12bxsxEYwM7FgeyaSgU71cLG0.woff

30 ms

JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff

JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff

30 ms

opc-ajax-loader.gif

opc-ajax-loader.gif

968 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

6 ms

Accessibility Review

floralinnea.com accessibility score

83

Accessibility Issues

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

High

[role]s do not have all required [aria-*] attributes

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

floralinnea.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

floralinnea.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    SV

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floralinnea.com can be misinterpreted by Google and other search engines. Our service has detected that Swedish is used on the page, and it does not match the claimed English language. Our system also found out that Floralinnea.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.

Social Sharing Optimization

floralinnea.com

Open Graph description is not detected on the main page of Flora Linnea. 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: