Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

681busterminal.com

681 Bus Terminal V2 - 681 巴士總站 V2

Page Load Speed

3.2 sec in total

First Response

675 ms

Resources Loaded

2.4 sec

Page Rendered

168 ms

681busterminal.com screenshot

About Website

Welcome to 681busterminal.com homepage info - get ready to check 681 Bus Terminal best content for Hong Kong right away, or after learning these important things about 681busterminal.com

巴士,專線小巴,九巴,新巴,龍運,城巴,新大嶼山巴士,路線資料

Visit 681busterminal.com

Key Findings

We analyzed 681busterminal.com page load time and found that the first response time was 675 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

681busterminal.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value3,310 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

681busterminal.com

675 ms

swfobject_modified.js

218 ms

AC_RunActiveContent.js

405 ms

show_ads.js

6 ms

ga.js

31 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 24% of them (6 requests) were addressed to the original 681busterminal.com, 20% (5 requests) were made to Pagead2.googlesyndication.com and 20% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain 681busterminal.com.

Page Optimization Overview & Recommendations

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

Content Size

291.6 kB

After Optimization

253.4 kB

In fact, the total size of 681busterminal.com main page is 291.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. 30% of websites need less resources to load. Images take 215.8 kB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 3.7 kB

  • Original 6.3 kB
  • After minification 6.0 kB
  • After compression 2.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. 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 3.7 kB or 59% of the original size.

Image Optimization

-3%

Potential reduce by 6.9 kB

  • Original 215.8 kB
  • After minification 208.8 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. 681 Bus Terminal images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 27.5 kB

  • Original 69.5 kB
  • After minification 60.8 kB
  • After compression 42.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 27.5 kB or 40% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (35%)

Requests Now

23

After Optimization

15

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

Accessibility Review

681busterminal.com accessibility score

78

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

High

<object> elements do not have alternate text

Best Practices

681busterminal.com 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

681busterminal.com SEO score

58

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

High

Document uses plugins

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    ZH

  • Encoding

    BIG5

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 681busterminal.com 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 Chinese language. Our system also found out that 681busterminal.com main page’s claimed encoding is big5. 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 681 Bus Terminal. 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: