Tools & Wizards About Us
zaem.ru screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

zaem.ru

Заём под 0% | Заём.ру

Page Load Speed

14.9 sec in total

First Response

1.5 sec

Resources Loaded

12 sec

Page Rendered

1.5 sec

zaem.ru screenshot

About Website

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

Заём.ру - онлайн-займы на банковскую карту

Visit zaem.ru

Key Findings

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

Performance Metrics

zaem.ru performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value1,310 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value9.7 s

28/100

10%

Network Requests Diagram

zaem.ru

1490 ms

www.zaem.ru

913 ms

core.css

324 ms

colorbox.css

477 ms

stylesheet.css

474 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 76% of them (74 requests) were addressed to the original Zaem.ru, 4% (4 requests) were made to Share.pluso.ru and 3% (3 requests) were made to Kitbit.net. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Zaem.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 550.1 kB (53%)

Content Size

1.0 MB

After Optimization

494.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zaem.ru main page is 1.0 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. Images take 486.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 48.3 kB

  • Original 62.2 kB
  • After minification 57.4 kB
  • After compression 13.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 48.3 kB or 78% of the original size.

Image Optimization

-31%

Potential reduce by 149.2 kB

  • Original 486.2 kB
  • After minification 337.1 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, Zaem needs image optimization as it can save up to 149.2 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 292.2 kB

  • Original 421.4 kB
  • After minification 347.5 kB
  • After compression 129.2 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 292.2 kB or 69% of the original size.

CSS Optimization

-81%

Potential reduce by 60.4 kB

  • Original 74.4 kB
  • After minification 56.2 kB
  • After compression 13.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. Zaem.ru needs all CSS files to be minified and compressed as it can save up to 60.4 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

90

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zaem.ru

zaem.ru

1490 ms

www.zaem.ru

www.zaem.ru

913 ms

core.css

core.css

324 ms

colorbox.css

colorbox.css

477 ms

stylesheet.css

stylesheet.css

474 ms

style.css

style.css

439 ms

style.css

style.css

444 ms

style.css

style.css

443 ms

jquery.stylizedForm.css

jquery.stylizedForm.css

446 ms

style.css

style.css

589 ms

style.css

style.css

598 ms

styles.css

styles.css

588 ms

template_styles.css

template_styles.css

589 ms

core.js

core.js

734 ms

core_ajax.js

core_ajax.js

598 ms

session.js

session.js

629 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

733 ms

jquery.ui-slider.js

jquery.ui-slider.js

608 ms

jquery.numeric.js

jquery.numeric.js

627 ms

test.js

test.js

627 ms

lib.js

lib.js

788 ms

jquery.colorbox.js

jquery.colorbox.js

791 ms

jquery.stylizedForm.js

jquery.stylizedForm.js

798 ms

jquery.form.js

jquery.form.js

790 ms

jquery.mask.min.js

jquery.mask.min.js

807 ms

form.css

form.css

862 ms

analytics.js

analytics.js

91 ms

spread.php

spread.php

253 ms

Block3_3.png

Block3_3.png

179 ms

cards.jpg

cards.jpg

678 ms

borshises.jpg

borshises.jpg

708 ms

map.jpg

map.jpg

678 ms

bg-header-top-wrapper-left.png

bg-header-top-wrapper-left.png

206 ms

smail-logo.gif

smail-logo.gif

205 ms

bg-header-top-wrapper.png

bg-header-top-wrapper.png

300 ms

company.png

company.png

301 ms

FederalNetwork.png

FederalNetwork.png

675 ms

get_loan.png

get_loan.png

661 ms

club.png

club.png

683 ms

pay.png

pay.png

691 ms

get_money.png

get_money.png

699 ms

home.png

home.png

730 ms

bg-header-top-wrapper-right.png

bg-header-top-wrapper-right.png

731 ms

logo.png

logo.png

891 ms

bg-logo-wrapp.png

bg-logo-wrapp.png

886 ms

magistrc-webfont.woff

magistrc-webfont.woff

831 ms

magistcb-webfont.woff

magistcb-webfont.woff

830 ms

bg-logo-wrapp-end.png

bg-logo-wrapp-end.png

821 ms

main-baner.png

main-baner.png

971 ms

collect

collect

49 ms

calculator_background.png

calculator_background.png

1036 ms

calculator-top.png

calculator-top.png

893 ms

input_26_mid.png

input_26_mid.png

901 ms

input_26_right.png

input_26_right.png

899 ms

input_26_left.png

input_26_left.png

899 ms

slider_background_left.png

slider_background_left.png

1035 ms

slider_background_right.png

slider_background_right.png

1034 ms

bullet.gif

bullet.gif

1042 ms

star.png

star.png

1043 ms

button.png

button.png

1041 ms

take_money_button.png

take_money_button.png

2803 ms

calculator-bottom.png

calculator-bottom.png

2152 ms

button_background.png

button_background.png

3036 ms

3_green_borders.png

3_green_borders.png

2806 ms

green_3_border_small.png

green_3_border_small.png

2713 ms

federal_button.png

federal_button.png

2784 ms

rtrg

rtrg

438 ms

footer.png

footer.png

5064 ms

pluso-like.js

pluso-like.js

396 ms

bottom-left.png

bottom-left.png

2688 ms

bottom-right.png

bottom-right.png

2727 ms

watch.js

watch.js

295 ms

165896

165896

325 ms

reformal.js

reformal.js

319 ms

overlay.png

overlay.png

2480 ms

slider_bg.png

slider_bg.png

2481 ms

slider_bg_fill.png

slider_bg_fill.png

2526 ms

slider_circle.png

slider_circle.png

2530 ms

radio.gif

radio.gif

2642 ms

checkbox.gif

checkbox.gif

2715 ms

3_green_borders2.png

3_green_borders2.png

2840 ms

widget_ru_RU.js

widget_ru_RU.js

297 ms

tab.png

tab.png

325 ms

st.php

st.php

331 ms

73362%7CaHR0cDovL3d3dy56YWVtLnJ1Lw==%7C%7C64178

73362%7CaHR0cDovL3d3dy56YWVtLnJ1Lw==%7C%7C64178

311 ms

gl.png

gl.png

128 ms

06.png

06.png

2053 ms

process

process

988 ms

hit;PLUSO

hit;PLUSO

988 ms

chat_ru_RU.js

chat_ru_RU.js

2209 ms

plus.png

plus.png

414 ms

kb.js

kb.js

1864 ms

collect_pluso.js

collect_pluso.js

2923 ms

dct.js

dct.js

223 ms

h.gif

h.gif

203 ms

s.js

s.js

997 ms

3696d9c5412d7dbcbaf1f52aba44c40f

3696d9c5412d7dbcbaf1f52aba44c40f

111 ms

Accessibility Review

zaem.ru accessibility score

83

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

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

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zaem.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 Zaem.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

zaem.ru

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