Tools & Wizards About Us
amournsk.ru screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

amournsk.ru

Доставка цветов в Новосибирске на дом и офис. Заказать круглосуточную доставку букетов в интернет-магазине Амур

Page Load Speed

6.5 sec in total

First Response

427 ms

Resources Loaded

3.6 sec

Page Rendered

2.5 sec

amournsk.ru screenshot

About Website

Visit amournsk.ru now to see the best up-to-date Amournsk content for Russia and also check out these interesting facts you probably never knew about amournsk.ru

Доставка цветов в Новосибирске на дом и офис - заказать круглосуточную доставку букетов в интернет-магазине Амур тел.: 8 (800) 333-01-45

Visit amournsk.ru

Key Findings

We analyzed Amournsk.ru page load time and found that the first response time was 427 ms and then it took 6.1 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

amournsk.ru performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value2,630 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

Network Requests Diagram

amournsk.ru

427 ms

amournsk.ru

646 ms

amournsk.ru

655 ms

intranet-common.css

343 ms

core.js

684 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 78% of them (64 requests) were addressed to the original Amournsk.ru, 4% (3 requests) were made to Code.jivo.ru and 2% (2 requests) were made to App.comagic.ru. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Amournsk.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 585.2 kB (18%)

Content Size

3.2 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Amournsk.ru main page is 3.2 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.6 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 251.5 kB

  • Original 282.6 kB
  • After minification 223.0 kB
  • After compression 31.1 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 59.6 kB, which is 21% 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 251.5 kB or 89% of the original size.

Image Optimization

-6%

Potential reduce by 97.4 kB

  • Original 1.6 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. Amournsk images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 209.9 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.1 MB

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

CSS Optimization

-31%

Potential reduce by 26.3 kB

  • Original 86.2 kB
  • After minification 86.2 kB
  • After compression 59.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. Amournsk.ru needs all CSS files to be minified and compressed as it can save up to 26.3 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (49%)

Requests Now

75

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

amournsk.ru

amournsk.ru

427 ms

amournsk.ru

amournsk.ru

646 ms

amournsk.ru

amournsk.ru

655 ms

intranet-common.css

intranet-common.css

343 ms

core.js

core.js

684 ms

kernel_main_v1.js

kernel_main_v1.js

568 ms

dexie3.bundle.js

dexie3.bundle.js

575 ms

core_ls.js

core_ls.js

349 ms

core_frame_cache.js

core_frame_cache.js

456 ms

protobuf.js

protobuf.js

701 ms

model.js

model.js

570 ms

rest.client.js

rest.client.js

680 ms

pull.client.js

pull.client.js

700 ms

swiper-bundle.min.css

swiper-bundle.min.css

699 ms

vendor.css

vendor.css

769 ms

main.css

main.css

796 ms

additional.css

additional.css

801 ms

vendor.js

vendor.js

1150 ms

main.js

main.js

809 ms

jquery.inputmask.min.js

jquery.inputmask.min.js

817 ms

common.js

common.js

880 ms

header.js

header.js

901 ms

search.js

search.js

933 ms

jquery.validate.min.js

jquery.validate.min.js

14 ms

swiper-bundle.min.js

swiper-bundle.min.js

941 ms

sliders.js

sliders.js

939 ms

cs.min.js

cs.min.js

729 ms

J1rgCXcN4L

J1rgCXcN4L

318 ms

ba.js

ba.js

270 ms

main-mobile.css

main-mobile.css

296 ms

main-tablet.css

main-tablet.css

314 ms

main-note.css

main-note.css

346 ms

main-desktop.css

main-desktop.css

356 ms

main-fullhd.css

main-fullhd.css

355 ms

gtm.js

gtm.js

162 ms

logo.svg

logo.svg

158 ms

7q2px1xb4qn6qvo6x2k499821zh6lbqm.jpg

7q2px1xb4qn6qvo6x2k499821zh6lbqm.jpg

160 ms

4ccs31x0q0ev623ecudoumy5r0144j9m.png

4ccs31x0q0ev623ecudoumy5r0144j9m.png

232 ms

no.png

no.png

157 ms

320.png

320.png

283 ms

7noa6v6esqktq2vzs6rpmll3hvjwkzgb.jpg

7noa6v6esqktq2vzs6rpmll3hvjwkzgb.jpg

283 ms

njjfjgz1qosfgk5o7hxyuskw0oa21p13.jpg

njjfjgz1qosfgk5o7hxyuskw0oa21p13.jpg

386 ms

s06ee538ut2afqipy3sxambw1csszsd6.jpg

s06ee538ut2afqipy3sxambw1csszsd6.jpg

386 ms

nz4wd1uuj91wybu1cwmvftiys62msgxa.jpg

nz4wd1uuj91wybu1cwmvftiys62msgxa.jpg

380 ms

t4sdan3kndlxr4g0zr4bkd3mis1wyf86.jpg

t4sdan3kndlxr4g0zr4bkd3mis1wyf86.jpg

343 ms

pluses-0.svg

pluses-0.svg

377 ms

pluses-1.svg

pluses-1.svg

380 ms

pluses-2.svg

pluses-2.svg

456 ms

pluses-3.svg

pluses-3.svg

484 ms

payment-0.svg

payment-0.svg

486 ms

payment-1.svg

payment-1.svg

488 ms

payment-2.svg

payment-2.svg

500 ms

payment-3.svg

payment-3.svg

499 ms

payment-4.svg

payment-4.svg

568 ms

payment-5.svg

payment-5.svg

598 ms

analytics.js

analytics.js

159 ms

watch.js

watch.js

39 ms

icons-sprite.svg

icons-sprite.svg

562 ms

icons-symbols.svg

icons-symbols.svg

568 ms

hpdlnyj5yb588ygcv2r77zmcgi0dhufs.jpg

hpdlnyj5yb588ygcv2r77zmcgi0dhufs.jpg

709 ms

9nwwo0afn9o14y42byaxh8g65rl79op6.jpg

9nwwo0afn9o14y42byaxh8g65rl79op6.jpg

599 ms

collect

collect

18 ms

hhjk96x3b1gyf6o31r2nabd9lv4x55to.jpg

hhjk96x3b1gyf6o31r2nabd9lv4x55to.jpg

560 ms

2db1l63w9f6jjy0obe6qa5hvl1vic7ly.jpg

2db1l63w9f6jjy0obe6qa5hvl1vic7ly.jpg

624 ms

xp908mya3fgv2vyu1lm9b4bfrgax6dj9.jpg

xp908mya3fgv2vyu1lm9b4bfrgax6dj9.jpg

740 ms

js

js

74 ms

4new8yhps0gegkel902ut7ym68j7xg3k.jpg

4new8yhps0gegkel902ut7ym68j7xg3k.jpg

624 ms

ajqr72yizdxq07hujfwix10tqqvav7ev.jpg

ajqr72yizdxq07hujfwix10tqqvav7ev.jpg

627 ms

pl1c0ulek4x701hb26bt4ig9re1m2u7r.jpg

pl1c0ulek4x701hb26bt4ig9re1m2u7r.jpg

629 ms

ktcw1o09g2p3y9etno8h6damsvlhxp4l.jpg

ktcw1o09g2p3y9etno8h6damsvlhxp4l.jpg

624 ms

hit

hit

566 ms

130 ms

J1rgCXcN4L

J1rgCXcN4L

171 ms

conversion.js

conversion.js

36 ms

32 ms

29 ms

J1rgCXcN4L

J1rgCXcN4L

518 ms

circe.ttf

circe.ttf

275 ms

circe_light.ttf

circe_light.ttf

250 ms

circe_bold.ttf

circe_bold.ttf

354 ms

hit

hit

134 ms

bundle_ru_RU.js

bundle_ru_RU.js

83 ms

Accessibility Review

amournsk.ru accessibility score

86

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.

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

amournsk.ru best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

amournsk.ru SEO score

92

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

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

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

amournsk.ru

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