Tools & Wizards About Us
amplitude.ru screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

amplitude.ru

Продажа и ремонт компьютеров, нотбуков, цифровых фотоаппаратов, принтеров. Программное обеспечение. / ООО

Page Load Speed

4.8 sec in total

First Response

469 ms

Resources Loaded

4.1 sec

Page Rendered

248 ms

amplitude.ru screenshot

About Website

Welcome to amplitude.ru homepage info - get ready to check Amplitude best content for Russia right away, or after learning these important things about amplitude.ru

Магазин по продаже и ремонту компьютеров, ноутбуков, принтеров, цифровых фотоаппаратов и др. цифровой техники.

Visit amplitude.ru

Key Findings

We analyzed Amplitude.ru page load time and found that the first response time was 469 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

amplitude.ru performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.486

17/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

amplitude.ru

469 ms

amplitude.ru

1080 ms

typography.php

411 ms

style.css

368 ms

ja.tabs.css

379 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 98% of them (89 requests) were addressed to the original Amplitude.ru, 1% (1 request) were made to Acint.net and 1% (1 request) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Acint.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 273.5 kB (40%)

Content Size

679.4 kB

After Optimization

405.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Amplitude.ru main page is 679.4 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. 35% of websites need less resources to load. Images take 344.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 40.0 kB

  • Original 51.5 kB
  • After minification 47.0 kB
  • After compression 11.6 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. 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 40.0 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 14.4 kB

  • Original 344.7 kB
  • After minification 330.2 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. Amplitude images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 127.8 kB

  • Original 173.8 kB
  • After minification 147.2 kB
  • After compression 46.0 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 127.8 kB or 74% of the original size.

CSS Optimization

-83%

Potential reduce by 91.3 kB

  • Original 109.4 kB
  • After minification 78.5 kB
  • After compression 18.1 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. Amplitude.ru needs all CSS files to be minified and compressed as it can save up to 91.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 72 (82%)

Requests Now

88

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

amplitude.ru

amplitude.ru

469 ms

amplitude.ru

amplitude.ru

1080 ms

typography.php

typography.php

411 ms

style.css

style.css

368 ms

ja.tabs.css

ja.tabs.css

379 ms

style.css

style.css

378 ms

mod_jabulletin.css

mod_jabulletin.css

380 ms

style.css

style.css

391 ms

mod_jasidenews.css

mod_jasidenews.css

489 ms

ja_contentslide.css

ja_contentslide.css

502 ms

ja_contentslide.css

ja_contentslide.css

503 ms

style.css

style.css

505 ms

style.css

style.css

522 ms

mod_jaslideshow2.css

mod_jaslideshow2.css

534 ms

mod_jaslideshow2.css

mod_jaslideshow2.css

611 ms

mootools.js

mootools.js

884 ms

caption.js

caption.js

648 ms

ja.tabs.js

ja.tabs.js

778 ms

ja_contentslide.js

ja_contentslide.js

666 ms

script.js

script.js

663 ms

script.js

script.js

854 ms

system.css

system.css

772 ms

general.css

general.css

789 ms

addons.css

addons.css

796 ms

layout.css

layout.css

898 ms

template.css

template.css

1030 ms

typo.css

typo.css

916 ms

ja.script.js

ja.script.js

926 ms

ja.ddmod.js

ja.ddmod.js

974 ms

mega.css

mega.css

1023 ms

mega.js

mega.js

1043 ms

icon-min.gif

icon-min.gif

126 ms

icon-max.gif

icon-max.gif

131 ms

bgtop.png

bgtop.png

255 ms

logo.png

logo.png

127 ms

search-bg.png

search-bg.png

124 ms

mainlevel-active.gif

mainlevel-active.gif

128 ms

sl-01_950_300.jpg

sl-01_950_300.jpg

484 ms

sl-02_950_300.jpg

sl-02_950_300.jpg

503 ms

sl-03_950_300.jpg

sl-03_950_300.jpg

366 ms

re-left.gif

re-left.gif

254 ms

re-right.gif

re-right.gif

253 ms

servis.jpg

servis.jpg

378 ms

1c.jpg

1c.jpg

379 ms

1az.jpg

1az.jpg

380 ms

1a.jpg

1a.jpg

488 ms

pr.png

pr.png

626 ms

corner-rs1.png

corner-rs1.png

497 ms

slide-mask.png

slide-mask.png

506 ms

but-pre.png

but-pre.png

596 ms

but-next.png

but-next.png

599 ms

container-bg.gif

container-bg.gif

603 ms

rs2-top.png

rs2-top.png

603 ms

corner-rs2.png

corner-rs2.png

613 ms

rs2-mid-top.png

rs2-mid-top.png

704 ms

rs2-mid-bot.png

rs2-mid-bot.png

704 ms

rs3-top.png

rs3-top.png

720 ms

corner-rs3.png

corner-rs3.png

731 ms

rs3-mid-l.png

rs3-mid-l.png

729 ms

rs3-mid-r.png

rs3-mid-r.png

739 ms

rs3-mid-top.png

rs3-mid-top.png

827 ms

h3-bg.gif

h3-bg.gif

824 ms

title-orange.gif

title-orange.gif

844 ms

bw-bg.png

bw-bg.png

838 ms

rs3-bot.png

rs3-bot.png

843 ms

rs5-top.png

rs5-top.png

847 ms

corner-rs5.png

corner-rs5.png

929 ms

aci.js

aci.js

1409 ms

hit

hit

535 ms

rs5-mid-l.png

rs5-mid-l.png

878 ms

rs5-mid-r.png

rs5-mid-r.png

896 ms

rs5-mid-top.png

rs5-mid-top.png

891 ms

rs5-bot.png

rs5-bot.png

897 ms

title-brown.gif

title-brown.gif

897 ms

title-green.gif

title-green.gif

848 ms

title-blue.gif

title-blue.gif

858 ms

icon-badge2.png

icon-badge2.png

880 ms

grad1.gif

grad1.gif

774 ms

rs2-bot.png

rs2-bot.png

776 ms

b-br.gif

b-br.gif

772 ms

b-bl.gif

b-bl.gif

842 ms

b-tr.gif

b-tr.gif

753 ms

b-tl.gif

b-tl.gif

771 ms

h3-bg2.gif

h3-bg2.gif

763 ms

bullet4.gif

bullet4.gif

770 ms

title-black.gif

title-black.gif

766 ms

rs4-top.png

rs4-top.png

736 ms

corner-rs4.png

corner-rs4.png

750 ms

rs4-ml.png

rs4-ml.png

757 ms

rs4-mr.png

rs4-mr.png

759 ms

rs4-bot.png

rs4-bot.png

771 ms

Accessibility Review

amplitude.ru accessibility score

68

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

Form elements do not have associated labels

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

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

Serves images with low resolution

SEO Factors

amplitude.ru SEO score

100

Search Engine Optimization Advices

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

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

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

amplitude.ru

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