Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

pl.ru

Parallels H-Sphere

Page Load Speed

5.3 sec in total

First Response

447 ms

Resources Loaded

4.7 sec

Page Rendered

120 ms

pl.ru screenshot

About Website

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

Петерлинк - Интернет-провайдер номер 1 в Санкт-петербурге. PeterLink Number ONE Internet provider in St.Petersburg, Russia.

Visit pl.ru

Key Findings

We analyzed Pl.ru page load time and found that the first response time was 447 ms and then it took 4.9 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

pl.ru performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.7 s

100/100

25%

SI (Speed Index)

Value0.8 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.7 s

100/100

10%

Network Requests Diagram

pl.ru

447 ms

www.peterlink.ru

3140 ms

peterlink.css

238 ms

faxer.js

249 ms

bul1.gif

215 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Pl.ru, 95% (21 requests) were made to Peterlink.ru. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Peterlink.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 14.5 kB (73%)

Content Size

20.0 kB

After Optimization

5.5 kB

In fact, the total size of Pl.ru main page is 20.0 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 17.6 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 13.9 kB

  • Original 17.6 kB
  • After minification 14.0 kB
  • After compression 3.7 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. This page needs HTML code to be minified as it can gain 3.7 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 13.9 kB or 79% of the original size.

JavaScript Optimization

-26%

Potential reduce by 289 B

  • Original 1.1 kB
  • After minification 1.1 kB
  • After compression 804 B

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 289 B or 26% of the original size.

CSS Optimization

-27%

Potential reduce by 355 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 939 B

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. Pl.ru needs all CSS files to be minified and compressed as it can save up to 355 B or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (55%)

Requests Now

20

After Optimization

9

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

Accessibility Review

pl.ru accessibility score

82

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.

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

pl.ru best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

pl.ru SEO score

58

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

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

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