Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

3.3 sec in total

First Response

839 ms

Resources Loaded

2.4 sec

Page Rendered

111 ms

runbus.net screenshot

About Website

Click here to check amazing Runbus content for India. Otherwise, check out these important facts you probably never knew about runbus.net

Visit runbus.net

Key Findings

We analyzed Runbus.net page load time and found that the first response time was 839 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

runbus.net performance score

0

Network Requests Diagram

runbus.net

839 ms

4776.js

1527 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original Runbus.net, 50% (1 request) were made to Ppc.netnet44.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Ppc.netnet44.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 582 B (45%)

Content Size

1.3 kB

After Optimization

712 B

In fact, the total size of Runbus.net main page is 1.3 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 836 B which makes up the majority of the site volume.

HTML Optimization

-48%

Potential reduce by 399 B

  • Original 836 B
  • After minification 832 B
  • After compression 437 B

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 399 B or 48% of the original size.

JavaScript Optimization

-40%

Potential reduce by 183 B

  • Original 458 B
  • After minification 416 B
  • After compression 275 B

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 183 B or 40% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

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

SEO Factors

runbus.net SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Runbus.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Runbus.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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