Tools & Wizards About Us
przystanektorun.pl screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

przystanektorun.pl

Przystanek Toruń - Hotel w centrum Torunia, wesela, konferencje

Page Load Speed

4.5 sec in total

First Response

271 ms

Resources Loaded

4.2 sec

Page Rendered

58 ms

przystanektorun.pl screenshot

About Website

Welcome to przystanektorun.pl homepage info - get ready to check Przystanek Torun best content right away, or after learning these important things about przystanektorun.pl

Hotel Przystanek Toruń*** & Restauracja Lokomotywa oferuje 50 komfortowych pokoi z bezpłatnym parkingiem w centrum Torunia, w bezpośrednim sąsiedztwie Starego Miasta. Restauracja oferuje dania kuchni ...

Visit przystanektorun.pl

Key Findings

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

Performance Metrics

przystanektorun.pl performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value1.005

2/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

przystanektorun.pl

271 ms

przystanektorun.pl

1136 ms

vqp8vat.css

93 ms

logo.png

227 ms

menu.png

343 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 69% of them (24 requests) were addressed to the original Przystanektorun.pl, 23% (8 requests) were made to Use.typekit.net and 3% (1 request) were made to P.typekit.net. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Przystanektorun.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 63.1 kB (2%)

Content Size

3.3 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 45.5 kB

  • Original 59.3 kB
  • After minification 56.1 kB
  • After compression 13.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. 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 45.5 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 17.5 kB

  • Original 3.2 MB
  • After minification 3.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. Przystanek Torun images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 73 B

  • Original 49.2 kB
  • After minification 49.2 kB
  • After compression 49.1 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.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

We found no issues to fix!

Requests Now

24

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Przystanek Torun. According to our analytics all requests are already optimized.

Network Requests Diagram

przystanektorun.pl

przystanektorun.pl

271 ms

przystanektorun.pl

przystanektorun.pl

1136 ms

vqp8vat.css

vqp8vat.css

93 ms

logo.png

logo.png

227 ms

menu.png

menu.png

343 ms

p.css

p.css

33 ms

general.js

general.js

611 ms

style.php

style.php

1096 ms

embed

embed

177 ms

image_50727937%20(002).JPG

image_50727937%20(002).JPG

1213 ms

IMG_20231211_211327.jpg

IMG_20231211_211327.jpg

1000 ms

IMG_8172.jpg

IMG_8172.jpg

793 ms

IMG_1328.jpg

IMG_1328.jpg

911 ms

keyboard_arrow_left-24px.svg

keyboard_arrow_left-24px.svg

693 ms

keyboard_arrow_right-24px.svg

keyboard_arrow_right-24px.svg

807 ms

train.svg

train.svg

906 ms

bicycle.svg

bicycle.svg

920 ms

running.svg

running.svg

1020 ms

adoption.svg

adoption.svg

1025 ms

Lokomotywa_142.jpg

Lokomotywa_142.jpg

1449 ms

Lokomotywa_003.jpg

Lokomotywa_003.jpg

1466 ms

pop_up.jpg

pop_up.jpg

1704 ms

pfr.jpg

pfr.jpg

2720 ms

torun-unsplash.jpg

torun-unsplash.jpg

1857 ms

js

js

62 ms

roomsslick

roomsslick

286 ms

cien-smaller.png

cien-smaller.png

121 ms

d

d

12 ms

d

d

27 ms

d

d

26 ms

d

d

26 ms

fontello.woff

fontello.woff

148 ms

d

d

148 ms

d

d

24 ms

d

d

111 ms

Accessibility Review

przystanektorun.pl accessibility score

85

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

przystanektorun.pl best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

przystanektorun.pl SEO score

93

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

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

przystanektorun.pl

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