Tools & Wizards About Us

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

flora.qa

Flora Flowers Online Shop in Qatar | Flowers | Chocolates | Occasions | Sweets | Doha | Qatar | Online | Delivery

Page Load Speed

10.6 sec in total

First Response

1.8 sec

Resources Loaded

8.4 sec

Page Rendered

426 ms

About Website

Welcome to flora.qa homepage info - get ready to check Flora best content right away, or after learning these important things about flora.qa

Order fresh flowers in Qatar with same day delivery or visit local Shop florists. Shop for flowers, sweets, gifts and gift baskets by occasion & season.

Visit flora.qa

Key Findings

We analyzed Flora.qa page load time and found that the first response time was 1.8 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

flora.qa performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value15.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value18.5 s

0/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.432

22/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

www.flora.qa

1834 ms

global.css

1561 ms

highdpi.css

670 ms

responsive-tables.css

670 ms

uniform.default.css

676 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 96% of them (108 requests) were addressed to the original Flora.qa, 2% (2 requests) were made to Connect.facebook.net and 2% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Flora.qa.

Page Optimization Overview & Recommendations

Page size can be reduced by 770.4 kB (32%)

Content Size

2.4 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flora.qa main page is 2.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. 45% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 158.9 kB

  • Original 185.1 kB
  • After minification 152.5 kB
  • After compression 26.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 32.6 kB, which is 18% 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 158.9 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 111 B

  • Original 1.5 MB
  • After minification 1.5 MB

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 images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 249.9 kB

  • Original 332.1 kB
  • After minification 264.0 kB
  • After compression 82.3 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 249.9 kB or 75% of the original size.

CSS Optimization

-85%

Potential reduce by 361.5 kB

  • Original 427.4 kB
  • After minification 327.7 kB
  • After compression 65.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. Flora.qa needs all CSS files to be minified and compressed as it can save up to 361.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (57%)

Requests Now

109

After Optimization

47

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

flora.qa accessibility score

50

Accessibility Issues

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

Form elements do not have associated labels

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

flora.qa 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

flora.qa SEO score

83

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flora.qa 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 Flora.qa 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

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