Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

egazety.pl

eGazety.pl - prasa online, e-wydania, prenumeraty

Page Load Speed

10.8 sec in total

First Response

419 ms

Resources Loaded

10.1 sec

Page Rendered

249 ms

egazety.pl screenshot

About Website

Visit egazety.pl now to see the best up-to-date EGazety content for Poland and also check out these interesting facts you probably never knew about egazety.pl

Elektroniczne wydania czasopism polskich i zagranicznych. Dzienniki, tygodniki, miesięczniki - prenumerata, pojedyncze wydania, archiwum - gazeta online.

Visit egazety.pl

Key Findings

We analyzed Egazety.pl page load time and found that the first response time was 419 ms and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

egazety.pl performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.111

87/100

15%

TTI (Time to Interactive)

Value9.7 s

28/100

10%

Network Requests Diagram

egazety.pl

419 ms

www.egazety.pl

648 ms

site.css

235 ms

style.css

240 ms

lightbox.css

236 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 75% of them (92 requests) were addressed to the original Egazety.pl, 8% (10 requests) were made to Static.xx.fbcdn.net and 4% (5 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (8.6 sec) relates to the external source App2.salesmanago.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 63.0 kB (15%)

Content Size

420.1 kB

After Optimization

357.1 kB

In fact, the total size of Egazety.pl main page is 420.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. 55% of websites need less resources to load. Images take 324.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 50.9 kB

  • Original 63.5 kB
  • After minification 49.5 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 14.0 kB, which is 22% 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 50.9 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 1.0 kB

  • Original 324.8 kB
  • After minification 323.7 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. EGazety images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 11.0 kB

  • Original 31.8 kB
  • After minification 30.1 kB
  • After compression 20.8 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 11.0 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 68 (57%)

Requests Now

120

After Optimization

52

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

Accessibility Review

egazety.pl accessibility score

68

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

egazety.pl best practices score

58

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

egazety.pl SEO score

85

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Egazety.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish 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 Egazety.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 EGazety. 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: