Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 78

    SEO

    Google-friendlier than
    40% of websites

fleurop.at

Fleurop Austria online

Page Load Speed

7.5 sec in total

First Response

315 ms

Resources Loaded

6.6 sec

Page Rendered

570 ms

fleurop.at screenshot

About Website

Visit fleurop.at now to see the best up-to-date Fleurop content for Austria and also check out these interesting facts you probably never knew about fleurop.at

Fleurop-Interflora: birthday bouquets, roses, Maennerpflanzen and many other gift ideas ordered online and delivered worldwide by local florists.

Visit fleurop.at

Key Findings

We analyzed Fleurop.at page load time and found that the first response time was 315 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

fleurop.at performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value1,690 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.432

22/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

fleurop.at

315 ms

www.fleurop.at

1094 ms

at_style.css

507 ms

jquery-ui-1.8.24.custom.css

407 ms

jquery-1.8.2.min.js

732 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 89% of them (50 requests) were addressed to the original Fleurop.at, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Fleurop.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 469.6 kB (36%)

Content Size

1.3 MB

After Optimization

825.9 kB

In fact, the total size of Fleurop.at main page is 1.3 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. 15% of websites need less resources to load. Images take 766.1 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 33.5 kB

  • Original 39.7 kB
  • After minification 26.4 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 13.4 kB, which is 34% 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 33.5 kB or 84% of the original size.

Image Optimization

-10%

Potential reduce by 75.1 kB

  • Original 766.1 kB
  • After minification 691.0 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. Fleurop images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 272.7 kB

  • Original 384.9 kB
  • After minification 371.9 kB
  • After compression 112.2 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 272.7 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 88.3 kB

  • Original 104.7 kB
  • After minification 81.2 kB
  • After compression 16.4 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. Fleurop.at needs all CSS files to be minified and compressed as it can save up to 88.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (25%)

Requests Now

53

After Optimization

40

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

Accessibility Review

fleurop.at accessibility score

73

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

[aria-*] attributes do not match their roles

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

fleurop.at best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

fleurop.at SEO score

78

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-9

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fleurop.at 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 Fleurop.at main page’s claimed encoding is utf-9. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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