Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

nekropol.com

Некрополь - информационные памятники. Виртуальные могилы, жертвы Холокоста, эпитафии, генеалогия

Page Load Speed

4.1 sec in total

First Response

402 ms

Resources Loaded

3.6 sec

Page Rendered

81 ms

nekropol.com screenshot

About Website

Welcome to nekropol.com homepage info - get ready to check Nekropol best content for Russia right away, or after learning these important things about nekropol.com

Некрополь – информационные памятники. Виртуальные памятники - хранилище информации об умерших родственниках и друзьях, о жертвах и героях Холокоста, о советских гражданах, похороненных в Германии. Кал...

Visit nekropol.com

Key Findings

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

Performance Metrics

nekropol.com performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

nekropol.com

402 ms

nekropol.com

495 ms

www.nekropol.com

379 ms

www.nekropol.com

518 ms

tag.js

773 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 63% of them (17 requests) were addressed to the original Nekropol.com, 7% (2 requests) were made to Google-analytics.com and 7% (2 requests) were made to Counter.rambler.ru. The less responsive or slowest element that took the longest time to load (889 ms) relates to the external source Counter.rambler.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.1 kB (17%)

Content Size

151.0 kB

After Optimization

124.9 kB

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

HTML Optimization

-73%

Potential reduce by 25.7 kB

  • Original 35.2 kB
  • After minification 30.1 kB
  • After compression 9.5 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 5.1 kB, which is 14% 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 25.7 kB or 73% of the original size.

Image Optimization

-39%

Potential reduce by 347 B

  • Original 898 B
  • After minification 551 B

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, Nekropol needs image optimization as it can save up to 347 B or 39% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 115.0 kB
  • After minification 115.0 kB
  • After compression 114.9 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 14 (67%)

Requests Now

21

After Optimization

7

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

Accessibility Review

nekropol.com accessibility score

93

Accessibility Issues

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

nekropol.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

nekropol.com SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nekropol.com 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 Nekropol.com 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 Nekropol. 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: