Tools & Wizards About Us
flower.am screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

flower.am

Avenue

Page Load Speed

1.9 sec in total

First Response

262 ms

Resources Loaded

1.6 sec

Page Rendered

61 ms

flower.am screenshot

About Website

Welcome to flower.am homepage info - get ready to check Flower best content right away, or after learning these important things about flower.am

Avenue des Fleurs Flowers And Gifts Shop

Visit flower.am

Key Findings

We analyzed Flower.am page load time and found that the first response time was 262 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

flower.am performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value29.6 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

flower.am

262 ms

flower.am

483 ms

all.min.css

32 ms

bootstrap.min.css

38 ms

slick.min.css

46 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 31% of them (5 requests) were addressed to the original Flower.am, 25% (4 requests) were made to Fonts.googleapis.com and 19% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (823 ms) belongs to the original domain Flower.am.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 kB (5%)

Content Size

23.1 kB

After Optimization

21.9 kB

  • HTML
  • JavaScript

In fact, the total size of Flower.am main page is 23.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 5% of websites need less resources to load. Javascripts take 21.0 kB which makes up the majority of the site volume.

HTML Optimization

-54%

Potential reduce by 1.1 kB

  • Original 2.1 kB
  • After minification 2.1 kB
  • After compression 958 B

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 1.1 kB or 54% of the original size.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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. This website has mostly compressed JavaScripts.

Requests Breakdown

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

Requests Now

14

After Optimization

6

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

flower.am

flower.am

262 ms

flower.am

flower.am

483 ms

all.min.css

all.min.css

32 ms

bootstrap.min.css

bootstrap.min.css

38 ms

slick.min.css

slick.min.css

46 ms

sweetalert2.min.css

sweetalert2.min.css

118 ms

slick-theme.min.css

slick-theme.min.css

46 ms

css

css

45 ms

icon

icon

51 ms

main.8df2e4f8.js

main.8df2e4f8.js

823 ms

main.bc7e3033.css

main.bc7e3033.css

459 ms

js

js

67 ms

css2

css2

14 ms

css2

css2

25 ms

analytics.js

analytics.js

15 ms

collect

collect

12 ms

Accessibility Review

flower.am accessibility score

81

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

<frame> or <iframe> elements do not have a title

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

flower.am best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

flower.am SEO score

92

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

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flower.am can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Flower.am 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

flower.am

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: