Tools & Wizards About Us
neobus.pl screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

neobus.pl

NEOBUS - Transportation buses rzeszów warszawa sanok krosno iwonicz zdrój rymanów polańczyk wetlina wrocław gliwice katowice kraków zakopane kielce ra...

Page Load Speed

3.7 sec in total

First Response

179 ms

Resources Loaded

2.9 sec

Page Rendered

619 ms

neobus.pl screenshot

About Website

Click here to check amazing NEOBUS content for Poland. Otherwise, check out these important facts you probably never knew about neobus.pl

Hotline: 17 277 30 95 NEOBUS - Transportation buses podkarpacie - Warsaw | podkarpacie - wrocław we also hire coaches and buses

Visit neobus.pl

Key Findings

We analyzed Neobus.pl page load time and found that the first response time was 179 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

neobus.pl performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value2,270 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

179 ms

all-styles.css

132 ms

css

182 ms

js

294 ms

jquery-1.11.0.min.js

87 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 52% of them (22 requests) were addressed to the original Neobus.pl, 10% (4 requests) were made to Connect.facebook.net and 7% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (816 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 25.1 kB (5%)

Content Size

528.6 kB

After Optimization

503.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Neobus.pl main page is 528.6 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 267.5 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 24.0 kB

  • Original 33.7 kB
  • After minification 30.2 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 24.0 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 16 B

  • Original 267.5 kB
  • After minification 267.5 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. NEOBUS images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.2 kB

  • Original 227.4 kB
  • After minification 227.4 kB
  • After compression 226.3 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.

Requests Breakdown

Number of requests can be reduced by 29 (74%)

Requests Now

39

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

179 ms

all-styles.css

all-styles.css

132 ms

css

css

182 ms

js

js

294 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

87 ms

app.js

app.js

87 ms

popup.js

popup.js

87 ms

all-js.js

all-js.js

108 ms

all-styles.css

all-styles.css

598 ms

conversion.js

conversion.js

290 ms

fbds.js

fbds.js

313 ms

gtm.js

gtm.js

219 ms

bat.js

bat.js

474 ms

1655059794786.jpg

1655059794786.jpg

321 ms

pattern2.png

pattern2.png

164 ms

xlogo.png.pagespeed.ic.DkqbhVgfyc.png

xlogo.png.pagespeed.ic.DkqbhVgfyc.png

165 ms

menu-close2.png

menu-close2.png

163 ms

user-ico2.png

user-ico2.png

152 ms

en_1.png

en_1.png

304 ms

xpl_1.png.pagespeed.ic.I4t0fl7wes.png

xpl_1.png.pagespeed.ic.I4t0fl7wes.png

302 ms

xuk_1.png.pagespeed.ic.UwL06ENYwV.png

xuk_1.png.pagespeed.ic.UwL06ENYwV.png

299 ms

xpfr-poziom.png.pagespeed.ic.g7hN1vz97k.png

xpfr-poziom.png.pagespeed.ic.g7hN1vz97k.png

302 ms

xue-h40.jpg.pagespeed.ic.y51Jk4tEsO.jpg

xue-h40.jpg.pagespeed.ic.y51Jk4tEsO.jpg

362 ms

initial-stop.png

initial-stop.png

363 ms

change-ico.png

change-ico.png

363 ms

final-stop.png

final-stop.png

363 ms

passengers.png

passengers.png

364 ms

calendar.png

calendar.png

364 ms

conversion_async.js

conversion_async.js

210 ms

ga.js

ga.js

685 ms

analytics.js

analytics.js

570 ms

fbevents.js

fbevents.js

308 ms

816 ms

806 ms

243772003809025

243772003809025

400 ms

__utm.gif

__utm.gif

459 ms

collect

collect

329 ms

323 ms

361970205705823

361970205705823

161 ms

collect

collect

98 ms

47 ms

ga-audiences

ga-audiences

157 ms

Accessibility Review

neobus.pl accessibility score

78

Accessibility Issues

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

Best Practices

neobus.pl best practices score

83

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

SEO Factors

neobus.pl SEO score

87

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

    EN

  • Language Claimed

    PL

  • Encoding

    UTF-8

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

neobus.pl

Open Graph data is detected on the main page of NEOBUS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: