Tools & Wizards About Us
lublin.eu screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

lublin.eu

lublin.eu - oficjalny portal miasta Lublin

Page Load Speed

6.5 sec in total

First Response

369 ms

Resources Loaded

5.7 sec

Page Rendered

463 ms

lublin.eu screenshot

About Website

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

lublin.eu - oficjalny portal miasta Lublin

Visit lublin.eu

Key Findings

We analyzed Lublin.eu page load time and found that the first response time was 369 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

lublin.eu performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

Network Requests Diagram

lublin.eu

369 ms

lublin.eu

909 ms

portal__1715345138_lFg.css

491 ms

portal__1646382170_lFg.js

1933 ms

5FSC3i6wEeSbXyIACtqXBA.js

29 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 80% of them (43 requests) were addressed to the original Lublin.eu, 4% (2 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Lublin.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 921.4 kB (53%)

Content Size

1.7 MB

After Optimization

827.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lublin.eu main page is 1.7 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. Javascripts take 604.9 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 163.2 kB

  • Original 186.1 kB
  • After minification 135.3 kB
  • After compression 22.8 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 50.7 kB, which is 27% 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 163.2 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 4.6 kB

  • Original 561.6 kB
  • After minification 557.0 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. Lublin images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 420.2 kB

  • Original 604.9 kB
  • After minification 604.7 kB
  • After compression 184.6 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 420.2 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 333.3 kB

  • Original 396.0 kB
  • After minification 378.2 kB
  • After compression 62.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. Lublin.eu needs all CSS files to be minified and compressed as it can save up to 333.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (35%)

Requests Now

43

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lublin.eu

lublin.eu

369 ms

lublin.eu

lublin.eu

909 ms

portal__1715345138_lFg.css

portal__1715345138_lFg.css

491 ms

portal__1646382170_lFg.js

portal__1646382170_lFg.js

1933 ms

5FSC3i6wEeSbXyIACtqXBA.js

5FSC3i6wEeSbXyIACtqXBA.js

29 ms

pl_PL.js

pl_PL.js

552 ms

js

js

52 ms

js

js

92 ms

piwik.js

piwik.js

139 ms

plac_litewski_wiosna_fot._miasto_lublin,mFOUwmGbZlOE6tCTiHtf.jpg

plac_litewski_wiosna_fot._miasto_lublin,mFOUwmGbZlOE6tCTiHtf.jpg

602 ms

logo_ue_z_obwodka_na_ciemnym_tle1.png

logo_ue_z_obwodka_na_ciemnym_tle1.png

140 ms

western_ukraine_flag_2.png

western_ukraine_flag_2.png

140 ms

lubelski_rower_miejski_1,k1qUwl-cZlOE6tCTiHtf.jpg

lubelski_rower_miejski_1,k1qUwl-cZlOE6tCTiHtf.jpg

317 ms

loteria_rozlicz_pit_w_lubinie_grafika__1,k1qUwl-cZlOE6tCTiHtf.png

loteria_rozlicz_pit_w_lubinie_grafika__1,k1qUwl-cZlOE6tCTiHtf.png

602 ms

wspolnie_po_tytul_esk_2029_1_fot._miasto_lublin,k1qUwl-cZlOE6tCTiHtf.jpg

wspolnie_po_tytul_esk_2029_1_fot._miasto_lublin,k1qUwl-cZlOE6tCTiHtf.jpg

391 ms

sl2024,k1qUwl-cZlOE2c-Zxb2InmpeU6iVT5Z7ZaFiY1exmoCIfV8.jpg

sl2024,k1qUwl-cZlOE2c-Zxb2InmpeU6iVT5Z7ZaFiY1exmoCIfV8.jpg

602 ms

uczestnicy_wycieczki_na_dachu_centrum_spotkania_kultur,k1qUwl-cZlOE6tCTiHtf.jpg

uczestnicy_wycieczki_na_dachu_centrum_spotkania_kultur,k1qUwl-cZlOE6tCTiHtf.jpg

713 ms

_dsc5433,k1qUwl-cZlOE6tCTiHtf.jpg

_dsc5433,k1qUwl-cZlOE6tCTiHtf.jpg

837 ms

l_2029_1,llPcf12Paw.png

l_2029_1,llPcf12Paw.png

716 ms

plansza_plan_dla_dzielnic,llPcf12Paw.png

plansza_plan_dla_dzielnic,llPcf12Paw.png

719 ms

elublin2,llPcf12Paw.png

elublin2,llPcf12Paw.png

716 ms

budzet_obywatelski,llPcf12Paw.png

budzet_obywatelski,llPcf12Paw.png

715 ms

strategia_50,llPcf12Paw.png

strategia_50,llPcf12Paw.png

831 ms

dialog_lublin,llPcf12Paw.png

dialog_lublin,llPcf12Paw.png

831 ms

ul._stary_gaj_fot._miasto_lublin,k1qUwl-cZlOE6tCTiHtf.jpg

ul._stary_gaj_fot._miasto_lublin,k1qUwl-cZlOE6tCTiHtf.jpg

833 ms

bliska_2_fot.miastolublin,k1qUwl-cZlOE6tCTiHtf.jpg

bliska_2_fot.miastolublin,k1qUwl-cZlOE6tCTiHtf.jpg

834 ms

ponikwoda_2024_mala,k1qUwl-cZlOE6tCTiHtf.jpg

ponikwoda_2024_mala,k1qUwl-cZlOE6tCTiHtf.jpg

841 ms

ul._budowlana,k1qUwl-cZlOE6tCTiHtf.jpg

ul._budowlana,k1qUwl-cZlOE6tCTiHtf.jpg

948 ms

ul._kruszynowa_fot._miasto_lublin,k1qUwl-cZlOE6tCTiHtf.jpg

ul._kruszynowa_fot._miasto_lublin,k1qUwl-cZlOE6tCTiHtf.jpg

1063 ms

herb.png

herb.png

948 ms

sdk.js

sdk.js

123 ms

sprite_page.png

sprite_page.png

946 ms

ul_dot.png

ul_dot.png

948 ms

logo.png

logo.png

958 ms

sprite_header.png

sprite_header.png

1061 ms

BTrgFPd.png

BTrgFPd.png

107 ms

shadow.png

shadow.png

987 ms

TitilliumWeb-Bold.woff

TitilliumWeb-Bold.woff

988 ms

TitilliumWeb-Regular.woff

TitilliumWeb-Regular.woff

989 ms

TitilliumWeb-SemiBold.woff

TitilliumWeb-SemiBold.woff

1051 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1172 ms

airst.php

airst.php

1310 ms

sdk.js

sdk.js

78 ms

146 ms

analytics.js

analytics.js

95 ms

collect

collect

13 ms

collect

collect

28 ms

tlo.png

tlo.png

619 ms

dobry.png

dobry.png

629 ms

titillium.ttf

titillium.ttf

633 ms

print.css

print.css

124 ms

tlo.png

tlo.png

123 ms

dobry.png

dobry.png

118 ms

titillium.ttf

titillium.ttf

375 ms

Accessibility Review

lublin.eu accessibility score

96

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

[lang] attributes do not have a valid value

Best Practices

lublin.eu best practices score

75

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

High

Missing source maps for large first-party JavaScript

SEO Factors

lublin.eu SEO score

88

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

High

Tap targets are not sized appropriately

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 Lublin.eu 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 Lublin.eu 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

lublin.eu

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