Tools & Wizards About Us
p218.ru screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

p218.ru

Постановление № 218 | Кооперация науки и бизнеса

Page Load Speed

4.8 sec in total

First Response

1.1 sec

Resources Loaded

3.5 sec

Page Rendered

226 ms

p218.ru screenshot

About Website

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

Принятое 9 апреля 2010 года Правительством России постановление № 218 направлено на развитие научно-промышленной кооперации науки и бизнеса.

Visit p218.ru

Key Findings

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

Performance Metrics

p218.ru performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value10,620 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.0 s

1/100

10%

Network Requests Diagram

p218.ru

1111 ms

k2.css

251 ms

normalize.css

254 ms

layout.css

254 ms

joomla.css

393 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 82% of them (41 requests) were addressed to the original P218.ru, 8% (4 requests) were made to Mc.yandex.ru and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain P218.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 229.8 kB (45%)

Content Size

509.1 kB

After Optimization

279.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of P218.ru main page is 509.1 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 230.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 25.6 kB

  • Original 33.2 kB
  • After minification 31.5 kB
  • After compression 7.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 25.6 kB or 77% of the original size.

Image Optimization

-12%

Potential reduce by 27.1 kB

  • Original 230.9 kB
  • After minification 203.9 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, P 218 needs image optimization as it can save up to 27.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-51%

Potential reduce by 43.1 kB

  • Original 84.1 kB
  • After minification 84.1 kB
  • After compression 41.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 43.1 kB or 51% of the original size.

CSS Optimization

-83%

Potential reduce by 134.0 kB

  • Original 160.9 kB
  • After minification 116.6 kB
  • After compression 27.0 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. P218.ru needs all CSS files to be minified and compressed as it can save up to 134.0 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

46

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

p218.ru

p218.ru

1111 ms

k2.css

k2.css

251 ms

normalize.css

normalize.css

254 ms

layout.css

layout.css

254 ms

joomla.css

joomla.css

393 ms

system.css

system.css

261 ms

template.css

template.css

398 ms

menu.css

menu.css

376 ms

gk.stuff.css

gk.stuff.css

378 ms

style1.css

style1.css

380 ms

typography.style1.css

typography.style1.css

519 ms

typography.iconset.style1.css

typography.iconset.style1.css

501 ms

css

css

27 ms

719 ms

mootools-core.js

mootools-core.js

883 ms

core.js

core.js

520 ms

jquery.min.js

jquery.min.js

921 ms

jquery-noconflict.js

jquery-noconflict.js

625 ms

jquery-migrate.min.js

jquery-migrate.min.js

646 ms

k2.js

k2.js

649 ms

bootstrap.min.js

bootstrap.min.js

874 ms

mootools-more.js

mootools-more.js

1426 ms

gk.scripts.js

gk.scripts.js

779 ms

gk.menu.js

gk.menu.js

842 ms

swfobject.js

swfobject.js

913 ms

engine.js

engine.js

968 ms

p218_logo_2016_3.jpg

p218_logo_2016_3.jpg

505 ms

k2.items.cache.4effff5398b13b476604d4d8450bedfd_Lnsp_139.jpg

k2.items.cache.4effff5398b13b476604d4d8450bedfd_Lnsp_139.jpg

256 ms

k2.items.cache.4effff5398b13b476604d4d8450bedfd_Lnsp_140.jpg

k2.items.cache.4effff5398b13b476604d4d8450bedfd_Lnsp_140.jpg

135 ms

k2.items.cache.fb5c27012bf7bd2b528a5fe03304bd91_Lnsp_140.jpg

k2.items.cache.fb5c27012bf7bd2b528a5fe03304bd91_Lnsp_140.jpg

135 ms

k2.items.cache.d4ae67bb81032f6add66be1c1df07be9_Lnsp_140.jpg

k2.items.cache.d4ae67bb81032f6add66be1c1df07be9_Lnsp_140.jpg

134 ms

k2.items.cache.7081cca2f9cd0c06f2cce9e93d01dda9_Lnsp_140.jpg

k2.items.cache.7081cca2f9cd0c06f2cce9e93d01dda9_Lnsp_140.jpg

137 ms

k2.items.cache.ec9e5d4418cddeb916f54861fa51abb5_Lnsp_134.jpg

k2.items.cache.ec9e5d4418cddeb916f54861fa51abb5_Lnsp_134.jpg

254 ms

k2.items.cache.3d3b7d5d68132cc424920deb43e754bb_Lnsp_134.jpg

k2.items.cache.3d3b7d5d68132cc424920deb43e754bb_Lnsp_134.jpg

259 ms

k2.items.cache.3abb66d58aa91d2b7b16f08ee38a95c0_Lnsp_134.jpg

k2.items.cache.3abb66d58aa91d2b7b16f08ee38a95c0_Lnsp_134.jpg

259 ms

k2.items.cache.68497d6cb194485d2759fde9466457b7_Lnsp_134.jpg

k2.items.cache.68497d6cb194485d2759fde9466457b7_Lnsp_134.jpg

263 ms

get_flash_player.gif

get_flash_player.gif

380 ms

banner_220.jpg

banner_220.jpg

632 ms

header_bg.png

header_bg.png

363 ms

lkmPXI0UZyQWFROl-tbGWw.ttf

lkmPXI0UZyQWFROl-tbGWw.ttf

18 ms

J-_AkolK9wA0iYBM8AG4sfesZW2xOQ-xsNqO47m55DA.ttf

J-_AkolK9wA0iYBM8AG4sfesZW2xOQ-xsNqO47m55DA.ttf

18 ms

social_icons.png

social_icons.png

346 ms

ga.js

ga.js

25 ms

watch.js

watch.js

170 ms

__utm.gif

__utm.gif

25 ms

watch.js

watch.js

456 ms

tablet.css

tablet.css

127 ms

advert.gif

advert.gif

85 ms

mobile.css

mobile.css

147 ms

1

1

85 ms

Accessibility Review

p218.ru accessibility score

93

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

p218.ru best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

p218.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

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 P218.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 P218.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

p218.ru

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