Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

nekrologi-baza.pl

Nekrologi Warszawskie - Baza Nekrologów zawiera informacje o zmarłych z okolic warszawy, opracowania genealogiczne, inskrypcje z nagrobków. &laquo  » ...

Page Load Speed

4.5 sec in total

First Response

930 ms

Resources Loaded

3.4 sec

Page Rendered

167 ms

nekrologi-baza.pl screenshot

About Website

Welcome to nekrologi-baza.pl homepage info - get ready to check Nekrologi Baza best content for Poland right away, or after learning these important things about nekrologi-baza.pl

nekrologi z terenu Warszawy, stale rozbudowywane narzedzie do poszukiwan genealogicznych, opracowania nekrologow zamieszczonych w warszawskiej prasie

Visit nekrologi-baza.pl

Key Findings

We analyzed Nekrologi-baza.pl page load time and found that the first response time was 930 ms and then it took 3.6 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

nekrologi-baza.pl performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value5.4 s

71/100

10%

Network Requests Diagram

www.nekrologi-baza.pl

930 ms

font-awesome-logo.css

216 ms

menu.css

214 ms

style.css

216 ms

tool_style.css

222 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 84% of them (46 requests) were addressed to the original Nekrologi-baza.pl, 7% (4 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Nekrologi-baza.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 652.2 kB (60%)

Content Size

1.1 MB

After Optimization

439.5 kB

In fact, the total size of Nekrologi-baza.pl main page is 1.1 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 841.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 39.8 kB

  • Original 49.4 kB
  • After minification 46.7 kB
  • After compression 9.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. 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 39.8 kB or 80% of the original size.

Image Optimization

-68%

Potential reduce by 571.5 kB

  • Original 841.4 kB
  • After minification 269.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, Nekrologi Baza needs image optimization as it can save up to 571.5 kB or 68% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-16%

Potential reduce by 24.7 kB

  • Original 149.9 kB
  • After minification 149.9 kB
  • After compression 125.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 24.7 kB or 16% of the original size.

CSS Optimization

-32%

Potential reduce by 16.2 kB

  • Original 51.0 kB
  • After minification 48.8 kB
  • After compression 34.8 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. Nekrologi-baza.pl needs all CSS files to be minified and compressed as it can save up to 16.2 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (71%)

Requests Now

52

After Optimization

15

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

Accessibility Review

nekrologi-baza.pl accessibility score

60

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

nekrologi-baza.pl 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

nekrologi-baza.pl SEO score

86

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

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

Language and Encoding

  • Language Detected

    PL

  • Language Claimed

    PL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nekrologi-baza.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Nekrologi-baza.pl 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

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