Tools & Wizards About Us
flixbus.al screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

flixbus.al

FlixBus: Convenient and affordable bus travel in the US

Page Load Speed

1 sec in total

First Response

9 ms

Resources Loaded

754 ms

Page Rendered

252 ms

flixbus.al screenshot

About Website

Click here to check amazing Flix Bus content. Otherwise, check out these important facts you probably never knew about flixbus.al

Discover the new way to travel by bus. Enjoy comfortable seats with spacious legroom, power outlets and free Wi-Fi while you travel the US by bus at unbeatable prices. Book your bus ticket now → FlixB...

Visit flixbus.al

Key Findings

We analyzed Flixbus.al page load time and found that the first response time was 9 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

flixbus.al performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value1,560 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value12.4 s

14/100

10%

Network Requests Diagram

flixbus.al

9 ms

www.flixbus.com

31 ms

honeycomb-fonts.css

40 ms

cms_honeycomb.2d1dd9.css

69 ms

styles.09d339.css

83 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Flixbus.al, 32% (6 requests) were made to Honeycomb.flixbus.com and 32% (6 requests) were made to Cdn-cf.cms.flixbus.com. The less responsive or slowest element that took the longest time to load (281 ms) relates to the external source Flixbus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.0 kB (28%)

Content Size

333.5 kB

After Optimization

238.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flixbus.al main page is 333.5 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. 20% of websites need less resources to load. Javascripts take 111.5 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 92.1 kB

  • Original 103.8 kB
  • After minification 72.5 kB
  • After compression 11.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 31.3 kB, which is 30% 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 92.1 kB or 89% of the original size.

Image Optimization

-2%

Potential reduce by 2.5 kB

  • Original 102.1 kB
  • After minification 99.6 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. Flix Bus images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 114 B

  • Original 111.5 kB
  • After minification 111.5 kB
  • After compression 111.4 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

-2%

Potential reduce by 300 B

  • Original 16.2 kB
  • After minification 16.2 kB
  • After compression 15.9 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. Flixbus.al has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (47%)

Requests Now

15

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flix Bus. 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

flixbus.al

flixbus.al

9 ms

www.flixbus.com

www.flixbus.com

31 ms

honeycomb-fonts.css

honeycomb-fonts.css

40 ms

cms_honeycomb.2d1dd9.css

cms_honeycomb.2d1dd9.css

69 ms

styles.09d339.css

styles.09d339.css

83 ms

flixbus.png

flixbus.png

73 ms

flix-icons.esm.js

flix-icons.esm.js

36 ms

flix-icons.js

flix-icons.js

40 ms

main.2f875b.js

main.2f875b.js

72 ms

classToggler.js

classToggler.js

36 ms

dropdown.js

dropdown.js

38 ms

popup.js

popup.js

38 ms

cc.js

cc.js

281 ms

pulse.js

pulse.js

40 ms

US_Cali_FlixBus_New-Design_mobile.jpg

US_Cali_FlixBus_New-Design_mobile.jpg

72 ms

map-teaser-us.png

map-teaser-us.png

70 ms

roboto-latin-400-normal.woff

roboto-latin-400-normal.woff

4 ms

roboto-latin-700-normal.woff

roboto-latin-700-normal.woff

7 ms

datadog-rum.js

datadog-rum.js

27 ms

Accessibility Review

flixbus.al accessibility score

100

Accessibility Issues

Best Practices

flixbus.al 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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

flixbus.al SEO score

82

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Encoding

    UTF-8

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

flixbus.al

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