Tools & Wizards About Us
2012.tagline.ru screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

2012.tagline.ru

Рейтинг Top-100 ведущих веб-студий России Тэглайн-2012, заказать сайт, создание сайта в России, разработка сайта, сколько стоит создать сайт в Рунете

Page Load Speed

6.9 sec in total

First Response

1.8 sec

Resources Loaded

4.8 sec

Page Rendered

298 ms

2012.tagline.ru screenshot

About Website

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

Рейтинг Top-100 ведущих веб-студий России Тэглайн-2012, заказать сайт, создание сайта в России, разработка сайта, сколько стоит создать сайт в Рунете

Visit 2012.tagline.ru

Key Findings

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

Performance Metrics

2012.tagline.ru performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

2012.tagline.ru

1815 ms

ga.js

387 ms

openapi.js

519 ms

s1.css

405 ms

style.css

389 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 76% of them (93 requests) were addressed to the original 2012.tagline.ru, 7% (9 requests) were made to Fasthire.ru and 5% (6 requests) were made to About.tagline.ru. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain 2012.tagline.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.1 kB (26%)

Content Size

487.2 kB

After Optimization

362.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 55.6 kB

  • Original 68.8 kB
  • After minification 66.3 kB
  • After compression 13.2 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 55.6 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 12.9 kB

  • Original 239.7 kB
  • After minification 226.8 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. 2012 Tagline images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 54.1 kB

  • Original 165.3 kB
  • After minification 165.2 kB
  • After compression 111.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 54.1 kB or 33% of the original size.

CSS Optimization

-19%

Potential reduce by 2.6 kB

  • Original 13.4 kB
  • After minification 13.4 kB
  • After compression 10.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. 2012.tagline.ru needs all CSS files to be minified and compressed as it can save up to 2.6 kB or 19% of the original size.

Requests Breakdown

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

Requests Now

119

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

2012.tagline.ru

2012.tagline.ru

1815 ms

ga.js

ga.js

387 ms

openapi.js

openapi.js

519 ms

s1.css

s1.css

405 ms

style.css

style.css

389 ms

jquery.js

jquery.js

647 ms

animation.js

animation.js

647 ms

widgets.js

widgets.js

42 ms

publicautoheight.js

publicautoheight.js

671 ms

1.jpg

1.jpg

404 ms

pirogov.png

pirogov.png

134 ms

trilan.png

trilan.png

132 ms

morizo.png

morizo.png

558 ms

agima.png

agima.png

283 ms

qb.png

qb.png

265 ms

onetouch.png

onetouch.png

284 ms

inclouds.png

inclouds.png

284 ms

mst.png

mst.png

397 ms

4tagline.png

4tagline.png

406 ms

binario.jpg

binario.jpg

403 ms

binn.png

binn.png

411 ms

cpeople.png

cpeople.png

527 ms

nineseven_logo.png

nineseven_logo.png

1513 ms

umi-cms.jpg

umi-cms.jpg

540 ms

pich.png

pich.png

541 ms

ruformat.jpg

ruformat.jpg

555 ms

regru.png

regru.png

661 ms

studio38.jpg

studio38.jpg

676 ms

megaplan.png

megaplan.png

679 ms

logo1.jpg

logo1.jpg

699 ms

anima.png

anima.png

701 ms

agente.png

agente.png

795 ms

diafan.cms.gif

diafan.cms.gif

813 ms

imagespark.png

imagespark.png

817 ms

e-time.png

e-time.png

838 ms

scada.png

scada.png

836 ms

sibirix.png

sibirix.png

928 ms

artlebedev.png

artlebedev.png

948 ms

actis.png

actis.png

953 ms

adv.png

adv.png

972 ms

redkeds.png

redkeds.png

976 ms

ailove.png

ailove.png

1059 ms

defainteractive.png

defainteractive.png

1084 ms

grape.png

grape.png

1089 ms

logotype.png

logotype.png

259 ms

anim.gif

anim.gif

548 ms

banner.gif

banner.gif

1071 ms

str_top.gif

str_top.gif

1112 ms

articulmedia.png

articulmedia.png

989 ms

promointeractive.png

promointeractive.png

1063 ms

creativepeople.png

creativepeople.png

944 ms

pirogov(1).png

pirogov(1).png

949 ms

notamedia.png

notamedia.png

968 ms

small

small

171 ms

str_down.gif

str_down.gif

964 ms

all.js

all.js

15 ms

__utm.gif

__utm.gif

7 ms

ga.js

ga.js

13 ms

hit

hit

260 ms

__utm.gif

__utm.gif

8 ms

watch.js

watch.js

1 ms

all.js

all.js

9 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

145 ms

itech.group.png

itech.group.png

932 ms

qsoft.png

qsoft.png

960 ms

nile.png

nile.png

969 ms

cetis.png

cetis.png

985 ms

nimax.png

nimax.png

990 ms

settings

settings

69 ms

screen.css

screen.css

139 ms

main.css

main.css

261 ms

form.css

form.css

260 ms

frame.css

frame.css

267 ms

jquery.min.js

jquery.min.js

391 ms

iframe.js

iframe.js

268 ms

aero.png

aero.png

936 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

23 ms

agima(1).png

agima(1).png

962 ms

webprofy.png

webprofy.png

971 ms

ingate.png

ingate.png

971 ms

dominion.png

dominion.png

985 ms

embeds

embeds

32 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

31 ms

hit

hit

490 ms

godde.png

godde.png

938 ms

wow.png

wow.png

960 ms

delaform.png

delaform.png

974 ms

mstdigital.png

mstdigital.png

1019 ms

umistudio.png

umistudio.png

962 ms

freeger.png

freeger.png

886 ms

trilan(1).png

trilan(1).png

923 ms

firma.png

firma.png

953 ms

bbdo.png

bbdo.png

960 ms

ony.png

ony.png

968 ms

print.css

print.css

132 ms

trinet.png

trinet.png

899 ms

aic.png

aic.png

974 ms

binn(1).png

binn(1).png

915 ms

justbenice.png

justbenice.png

933 ms

techart.png

techart.png

964 ms

sibirix(1).png

sibirix(1).png

883 ms

orangelabel.png

orangelabel.png

882 ms

itconstruct.png

itconstruct.png

910 ms

fish-art.png

fish-art.png

928 ms

adlabs.png

adlabs.png

1012 ms

atilect.png

atilect.png

887 ms

greensight.png

greensight.png

860 ms

kinetica.png

kinetica.png

880 ms

fert.png

fert.png

887 ms

knockknock.png

knockknock.png

916 ms

accorddigital.png

accorddigital.png

892 ms

dalee.png

dalee.png

859 ms

colary.png

colary.png

882 ms

inspiration.png

inspiration.png

947 ms

aic.jpg

aic.jpg

871 ms

1.gif

1.gif

851 ms

8.gif

8.gif

858 ms

2.jpg

2.jpg

845 ms

2.gif

2.gif

881 ms

3.gif

3.gif

880 ms

6.gif

6.gif

906 ms

4.gif

4.gif

946 ms

Accessibility Review

2012.tagline.ru accessibility score

56

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

2012.tagline.ru best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

2012.tagline.ru SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

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 2012.tagline.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 2012.tagline.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

2012.tagline.ru

Open Graph data is detected on the main page of 2012 Tagline. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: