Tools & Wizards About Us

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

nearbus.net

NearBus

Page Load Speed

1.3 sec in total

First Response

181 ms

Resources Loaded

858 ms

Page Rendered

222 ms

About Website

Visit nearbus.net now to see the best up-to-date Near Bus content for United States and also check out these interesting facts you probably never knew about nearbus.net

An Internet of Things Open Project

Visit nearbus.net

Key Findings

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

Performance Metrics

nearbus.net performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value1.9 s

100/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

nearbus.net

181 ms

style_.css

80 ms

ga.js

8 ms

widgets.js

142 ms

39.png

50 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 74% of them (14 requests) were addressed to the original Nearbus.net, 11% (2 requests) were made to Google-analytics.com and 11% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (441 ms) relates to the external source Platform.twitter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 58.7 kB (13%)

Content Size

453.5 kB

After Optimization

394.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nearbus.net main page is 453.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. 25% of websites need less resources to load. Images take 418.6 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 10.6 kB

  • Original 14.9 kB
  • After minification 12.4 kB
  • After compression 4.3 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 2.5 kB, which is 17% 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 10.6 kB or 71% of the original size.

Image Optimization

-11%

Potential reduce by 47.2 kB

  • Original 418.6 kB
  • After minification 371.4 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. Obviously, Near Bus needs image optimization as it can save up to 47.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.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

-31%

Potential reduce by 868 B

  • Original 2.8 kB
  • After minification 2.8 kB
  • After compression 1.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. Nearbus.net needs all CSS files to be minified and compressed as it can save up to 868 B or 31% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

17

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

nearbus.net accessibility score

54

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

nearbus.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

nearbus.net SEO score

67

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nearbus.net can be misinterpreted by Google and other search engines. Our service has detected that English 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 Nearbus.net 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

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