Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

flamingo.ru

Доставка цветов по Москве, России и миру. Заказ букетов и подарочных корзин | Фламинго.ру

Page Load Speed

24.4 sec in total

First Response

1 sec

Resources Loaded

22.9 sec

Page Rendered

426 ms

flamingo.ru screenshot

About Website

Click here to check amazing Flamingo content for Russia. Otherwise, check out these important facts you probably never knew about flamingo.ru

Доставка цветов по Москве, России и миру. Фламинго.Ру Заказ букетов, цветочных композиций. Подарочные корзины с фруктами и продуктами. Круглосуточная поддержка и удобные методы оплаты.

Visit flamingo.ru

Key Findings

We analyzed Flamingo.ru page load time and found that the first response time was 1 sec and then it took 23.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

flamingo.ru performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value800 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.108

87/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

www.flamingo.ru

1049 ms

template.css

360 ms

add.css

363 ms

registration_form.css

187 ms

style.css

188 ms

Our browser made a total of 259 requests to load all elements on the main page. We found that 46% of them (119 requests) were addressed to the original Flamingo.ru, 17% (45 requests) were made to Pbs.twimg.com and 5% (12 requests) were made to Widgets.livetex.ru. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (41%)

Content Size

2.5 MB

After Optimization

1.5 MB

In fact, the total size of Flamingo.ru main page is 2.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 73.8 kB

  • Original 94.7 kB
  • After minification 83.5 kB
  • After compression 21.0 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 11.3 kB, which is 12% 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 73.8 kB or 78% of the original size.

Image Optimization

-11%

Potential reduce by 158.1 kB

  • Original 1.4 MB
  • After minification 1.2 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. Obviously, Flamingo needs image optimization as it can save up to 158.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 627.9 kB

  • Original 832.6 kB
  • After minification 668.5 kB
  • After compression 204.7 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 627.9 kB or 75% of the original size.

CSS Optimization

-82%

Potential reduce by 195.1 kB

  • Original 236.5 kB
  • After minification 193.8 kB
  • After compression 41.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. Flamingo.ru needs all CSS files to be minified and compressed as it can save up to 195.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 94 (38%)

Requests Now

248

After Optimization

154

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

Accessibility Review

flamingo.ru accessibility score

54

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

flamingo.ru 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

High

Missing source maps for large first-party JavaScript

SEO Factors

flamingo.ru SEO score

77

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

Image elements do not have [alt] attributes

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flamingo.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Flamingo.ru 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 Flamingo. 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: