Tools & Wizards About Us
lwigrod.pl screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 42

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

lwigrod.pl

Sanatorium Krynica Zdrój - turnusy rehabilitacyjne - Lwigród

Page Load Speed

3.7 sec in total

First Response

335 ms

Resources Loaded

3.2 sec

Page Rendered

233 ms

lwigrod.pl screenshot

About Website

Click here to check amazing Lwigrod content. Otherwise, check out these important facts you probably never knew about lwigrod.pl

Lwigród to sanatorium i ośrodek wypoczynkowy w Krynicy Zdroju, oferujący między innymi turnusy rehabilitacyjne w górach. Zapraszamy do zapoznania się z naszą ofertą.

Visit lwigrod.pl

Key Findings

We analyzed Lwigrod.pl page load time and found that the first response time was 335 ms and then it took 3.4 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

lwigrod.pl performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.142

78/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

lwigrod.pl

335 ms

www.lwigrod.pl

561 ms

cms.css

114 ms

jquery-1.9.0.min.js

358 ms

jquery.flash.js

233 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 81% of them (57 requests) were addressed to the original Lwigrod.pl, 11% (8 requests) were made to Static.xx.fbcdn.net and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Lwigrod.pl.

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lwigrod.pl main page is 1.5 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. 30% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 16.5 kB

  • Original 22.6 kB
  • After minification 20.8 kB
  • After compression 6.1 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 16.5 kB or 73% of the original size.

Image Optimization

-14%

Potential reduce by 189.8 kB

  • Original 1.4 MB
  • After minification 1.2 MB

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

JavaScript Optimization

-17%

Potential reduce by 14.8 kB

  • Original 84.6 kB
  • After minification 84.6 kB
  • After compression 69.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 14.8 kB or 17% of the original size.

CSS Optimization

-22%

Potential reduce by 1.6 kB

  • Original 7.4 kB
  • After minification 7.4 kB
  • After compression 5.7 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. Lwigrod.pl needs all CSS files to be minified and compressed as it can save up to 1.6 kB or 22% of the original size.

Requests Breakdown

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

Requests Now

66

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lwigrod. 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 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lwigrod.pl

lwigrod.pl

335 ms

www.lwigrod.pl

www.lwigrod.pl

561 ms

cms.css

cms.css

114 ms

jquery-1.9.0.min.js

jquery-1.9.0.min.js

358 ms

jquery.flash.js

jquery.flash.js

233 ms

script.js

script.js

239 ms

style.css

style.css

241 ms

global.css

global.css

241 ms

slides.min.jquery.js

slides.min.jquery.js

241 ms

core_slides_start.js

core_slides_start.js

348 ms

jquery.fancybox.js

jquery.fancybox.js

377 ms

fancybox_starter.js

fancybox_starter.js

374 ms

jquery.fancybox.css

jquery.fancybox.css

374 ms

default.css

default.css

375 ms

jquery.cookie.js

jquery.cookie.js

463 ms

core_cookies.js

core_cookies.js

468 ms

core_cookies.css

core_cookies.css

482 ms

fancyCookie.js

fancyCookie.js

787 ms

fancyIntro.js

fancyIntro.js

483 ms

analytics.js

analytics.js

9 ms

collect

collect

30 ms

js

js

73 ms

page.php

page.php

180 ms

facebook-vertical_04.png

facebook-vertical_04.png

135 ms

bg.png

bg.png

130 ms

header.jpg

header.jpg

290 ms

logo.png

logo.png

228 ms

transp2.png

transp2.png

130 ms

slider.jpg

slider.jpg

350 ms

slider_1.jpeg,913,273,913:273.jpg

slider_1.jpeg,913,273,913:273.jpg

504 ms

slider_2.jpeg,913,273,913:273.jpg

slider_2.jpeg,913,273,913:273.jpg

492 ms

slider_3.jpeg,913,273,913:273.jpg

slider_3.jpeg,913,273,913:273.jpg

512 ms

osr452_zdjecie_duze_lwigrod___panorama_1_.jpg,913,273,913:273.jpg

osr452_zdjecie_duze_lwigrod___panorama_1_.jpg,913,273,913:273.jpg

564 ms

lwigrod_hotel_basen.jpg,913,273,913:273.jpg

lwigrod_hotel_basen.jpg,913,273,913:273.jpg

535 ms

content.jpg

content.jpg

487 ms

icon_plus.png

icon_plus.png

601 ms

icon_minus.png

icon_minus.png

612 ms

flag_pl.png

flag_pl.png

624 ms

flag_en.png

flag_en.png

634 ms

flag_ru.png

flag_ru.png

651 ms

flag_ua.png

flag_ua.png

684 ms

left_menu01.png

left_menu01.png

722 ms

transp.png

transp.png

732 ms

left_menu1.png

left_menu1.png

762 ms

left_menu2.png

left_menu2.png

776 ms

left_menu3.png

left_menu3.png

780 ms

left_menu4.png

left_menu4.png

823 ms

left_menu5.png

left_menu5.png

852 ms

left_menu6.png

left_menu6.png

870 ms

left_menu7.png

left_menu7.png

899 ms

photo1.jpg

photo1.jpg

932 ms

photo2.jpg

photo2.jpg

920 ms

photo3.jpg

photo3.jpg

967 ms

photo4.jpg

photo4.jpg

991 ms

slider_1.jpeg,913,273,913:273.jpg

slider_1.jpeg,913,273,913:273.jpg

1130 ms

loading.gif

loading.gif

1019 ms

fancybox_overlay.png

fancybox_overlay.png

1037 ms

popup.jpg

popup.jpg

1456 ms

fancybox_sprite.png

fancybox_sprite.png

974 ms

ZFluMDo2EQh.css

ZFluMDo2EQh.css

15 ms

VWDhCULazb5.js

VWDhCULazb5.js

32 ms

o1ndYS2og_B.js

o1ndYS2og_B.js

59 ms

5xOV5e9oy4e.js

5xOV5e9oy4e.js

60 ms

mP12tTiNgO_.js

mP12tTiNgO_.js

58 ms

owo2sPJxB2z.js

owo2sPJxB2z.js

64 ms

p55HfXW__mM.js

p55HfXW__mM.js

63 ms

fancybox_loading.gif

fancybox_loading.gif

980 ms

299520164_579293470197889_4602857984778869969_n.jpg

299520164_579293470197889_4602857984778869969_n.jpg

99 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

12 ms

trans.png

trans.png

116 ms

Accessibility Review

lwigrod.pl accessibility score

42

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

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.

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

lwigrod.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 Lwigrod.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 Lwigrod.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

lwigrod.pl

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