Tools & Wizards About Us
amocrm.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

amocrm.com

Boost sales with messaging apps — Kommo

Page Load Speed

3 sec in total

First Response

140 ms

Resources Loaded

2.5 sec

Page Rendered

414 ms

amocrm.com screenshot

About Website

Visit amocrm.com now to see the best up-to-date Amocrm content for Mexico and also check out these interesting facts you probably never knew about amocrm.com

Convert leads to sales, automate conversations across various messaging apps with easy-to-use, web-based online CRM - Kommo.

Visit amocrm.com

Key Findings

We analyzed Amocrm.com page load time and found that the first response time was 140 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

amocrm.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value2,870 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

amocrm.com

140 ms

www.amocrm.com

512 ms

style.css

144 ms

stylesheet.css

205 ms

login.css

209 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 73% of them (69 requests) were addressed to the original Amocrm.com, 5% (5 requests) were made to Static.olark.com and 3% (3 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (793 ms) belongs to the original domain Amocrm.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 856.7 kB (56%)

Content Size

1.5 MB

After Optimization

675.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Amocrm.com main page is 1.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. 50% of websites need less resources to load. Javascripts take 673.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 130.7 kB

  • Original 157.6 kB
  • After minification 149.2 kB
  • After compression 26.9 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 130.7 kB or 83% of the original size.

Image Optimization

-37%

Potential reduce by 219.6 kB

  • Original 588.6 kB
  • After minification 369.0 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. Obviously, Amocrm needs image optimization as it can save up to 219.6 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-61%

Potential reduce by 412.9 kB

  • Original 673.8 kB
  • After minification 610.2 kB
  • After compression 261.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 412.9 kB or 61% of the original size.

CSS Optimization

-84%

Potential reduce by 93.6 kB

  • Original 111.9 kB
  • After minification 84.9 kB
  • After compression 18.3 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. Amocrm.com needs all CSS files to be minified and compressed as it can save up to 93.6 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

79

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

amocrm.com

amocrm.com

140 ms

www.amocrm.com

www.amocrm.com

512 ms

style.css

style.css

144 ms

stylesheet.css

stylesheet.css

205 ms

login.css

login.css

209 ms

register.css

register.css

212 ms

forgot_pwd.css

forgot_pwd.css

214 ms

intlTelInput.css

intlTelInput.css

216 ms

recall.css

recall.css

221 ms

new_promo_top_menu.css

new_promo_top_menu.css

270 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

483 ms

nonauth.js

nonauth.js

280 ms

geolocate.js

geolocate.js

279 ms

register_form_lang_en.js

register_form_lang_en.js

281 ms

register_form_validation.js

register_form_validation.js

283 ms

intlTelInput.js

intlTelInput.js

471 ms

forgot_password_form.js

forgot_password_form.js

347 ms

jquery-cookie.js

jquery-cookie.js

347 ms

script.js

script.js

350 ms

roitracker.js

roitracker.js

353 ms

sourcebuster.min.js

sourcebuster.min.js

415 ms

main.js

main.js

415 ms

raphael-min.js

raphael-min.js

636 ms

jquery.carousel-1.1.min.js

jquery.carousel-1.1.min.js

423 ms

watch_visor.js

watch_visor.js

466 ms

conversion.js

conversion.js

37 ms

291 ms

ga.js

ga.js

140 ms

374 ms

register_mail.png

register_mail.png

136 ms

register_pass.png

register_pass.png

135 ms

register_person.png

register_person.png

134 ms

register_coupone.png

register_coupone.png

135 ms

our_friends.png

our_friends.png

202 ms

login.png

login.png

134 ms

password.png

password.png

197 ms

logo_main.png

logo_main.png

198 ms

home_ico.png

home_ico.png

199 ms

1.png

1.png

198 ms

2.png

2.png

196 ms

3.png

3.png

274 ms

4.png

4.png

275 ms

5.png

5.png

274 ms

6.png

6.png

273 ms

Adam%20Kessel_main.png

Adam%20Kessel_main.png

462 ms

Amanda%20Tufeld_main.png

Amanda%20Tufeld_main.png

407 ms

Cheryl%20Lasher_main.png

Cheryl%20Lasher_main.png

525 ms

Sylvain%20Roy_main.png

Sylvain%20Roy_main.png

413 ms

Matthew_main.png

Matthew_main.png

423 ms

chat.png

chat.png

351 ms

call.png

call.png

421 ms

dropdown_white.png

dropdown_white.png

467 ms

poster1.jpg

poster1.jpg

536 ms

transparent_bg.png

transparent_bg.png

481 ms

1.png

1.png

483 ms

2.png

2.png

515 ms

3.png

3.png

534 ms

4.png

4.png

547 ms

spritesheet.png

spritesheet.png

553 ms

email.png

email.png

582 ms

you.png

you.png

652 ms

facebook.png

facebook.png

602 ms

twitter.png

twitter.png

603 ms

code.js

code.js

647 ms

81 ms

loader0.js

loader0.js

174 ms

OpenSans-Light.woff

OpenSans-Light.woff

793 ms

OpenSans-Regular.woff

OpenSans-Regular.woff

630 ms

87 ms

fbevents.js

fbevents.js

293 ms

advert.gif

advert.gif

123 ms

OpenSans-Semibold.woff

OpenSans-Semibold.woff

679 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

625 ms

OpenSans-ExtraBold.woff

OpenSans-ExtraBold.woff

629 ms

OpenSans-LightItalic.woff

OpenSans-LightItalic.woff

674 ms

OpenSans-Italic.woff

OpenSans-Italic.woff

719 ms

__utm.gif

__utm.gif

47 ms

57 ms

64 ms

OpenSans-SemiboldItalic.woff

OpenSans-SemiboldItalic.woff

701 ms

OpenSans-BoldItalic.woff

OpenSans-BoldItalic.woff

707 ms

OpenSans-ExtraBoldItalic.woff

OpenSans-ExtraBoldItalic.woff

744 ms

ga-audiences

ga-audiences

24 ms

9830-769-10-2759.js

9830-769-10-2759.js

32 ms

c

c

216 ms

1

1

91 ms

33 ms

36 ms

counter

counter

160 ms

application2.js

application2.js

84 ms

utils.js

utils.js

149 ms

tracker

tracker

161 ms

storage.html

storage.html

28 ms

storage.js

storage.js

30 ms

Accessibility Review

amocrm.com accessibility score

53

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.

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

amocrm.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

amocrm.com SEO score

85

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

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 Amocrm.com 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 Amocrm.com 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

amocrm.com

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