2 sec in total
181 ms
1.5 sec
293 ms
Click here to check amazing SF Live Bus content. Otherwise, check out these important facts you probably never knew about sflivebus.com
Visit sflivebus.comWe analyzed Sflivebus.com page load time and found that the first response time was 181 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
sflivebus.com performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value9.7 s
0/100
25%
Value5.4 s
55/100
10%
Value210 ms
88/100
30%
Value0.001
100/100
15%
Value8.7 s
36/100
10%
181 ms
143 ms
11 ms
33 ms
48 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 15% of them (13 requests) were addressed to the original Sflivebus.com, 58% (49 requests) were made to Maps.googleapis.com and 12% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (181 ms) belongs to the original domain Sflivebus.com.
Page size can be reduced by 414.7 kB (34%)
1.2 MB
796.5 kB
In fact, the total size of Sflivebus.com main page is 1.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 583.9 kB which makes up the majority of the site volume.
Potential reduce by 50.9 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 50.9 kB or 88% of the original size.
Potential reduce by 14.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. SF Live Bus images are well optimized though.
Potential reduce by 349.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 349.4 kB or 60% of the original size.
Number of requests can be reduced by 32 (41%)
78
46
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SF Live 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 23 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
sflivebus.com
181 ms
www.sflivebus.com
143 ms
animate.min.css
11 ms
font-awesome.min.css
33 ms
buttons.css
48 ms
site.css
49 ms
githubButton.html
41 ms
githubButton.html
47 ms
js
97 ms
firebase.js
74 ms
rsvp.min.js
34 ms
geofire.min.js
44 ms
lodash.min.js
47 ms
sfVehicles.js
46 ms
geofire
116 ms
widgets.js
171 ms
ga.js
24 ms
__utm.gif
25 ms
fontawesome-webfont.woff
26 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
38 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
42 ms
jot
108 ms
common.js
16 ms
util.js
32 ms
marker.js
45 ms
map.js
9 ms
geometry.js
50 ms
poly.js
49 ms
onion.js
23 ms
openhand_8_8.cur
80 ms
ViewportInfoService.GetViewportInfo
126 ms
stats.js
59 ms
controls.js
60 ms
transparent.png
67 ms
undo_poly.png
39 ms
css
108 ms
google4.png
28 ms
mapcnt6.png
55 ms
sv5.png
55 ms
tmapctrl.png
50 ms
cb_scout5.png
54 ms
tmapctrl4.png
49 ms
imgs8.png
66 ms
vt
43 ms
vt
62 ms
vt
38 ms
vt
60 ms
vt
59 ms
vt
63 ms
vt
63 ms
vt
58 ms
vt
68 ms
vt
88 ms
vt
68 ms
vt
67 ms
vt
72 ms
vt
73 ms
vt
99 ms
vt
98 ms
vt
92 ms
vt
97 ms
vt
110 ms
vt
112 ms
vt
109 ms
vt
112 ms
vt
110 ms
vt
112 ms
vt
112 ms
vt
117 ms
vt
115 ms
vt
117 ms
vt
115 ms
vt
113 ms
vt
120 ms
vt
120 ms
vt
122 ms
vt
121 ms
vt
123 ms
vt
124 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
40 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
42 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
62 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
68 ms
vt
99 ms
AuthenticationService.Authenticate
73 ms
sflivebus.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
sflivebus.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
sflivebus.com SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sflivebus.com 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 Sflivebus.com main page’s claimed encoding is . 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.
sflivebus.com
Open Graph description is not detected on the main page of SF Live 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: