2.3 sec in total
173 ms
2 sec
148 ms
Click here to check amazing San Francisco Sightseeing content for United States. Otherwise, check out these important facts you probably never knew about sanfranciscosightseeing.com
Gray Line San Francisco - the #1 choice for sightseeing in San Francisco. Choose from over 20 different tours and see the city like never before!
Visit sanfranciscosightseeing.comWe analyzed Sanfranciscosightseeing.com page load time and found that the first response time was 173 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
sanfranciscosightseeing.com performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value12.4 s
0/100
25%
Value8.4 s
18/100
10%
Value180 ms
91/100
30%
Value0
100/100
15%
Value12.4 s
14/100
10%
173 ms
117 ms
71 ms
139 ms
206 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 93% of them (43 requests) were addressed to the original Sanfranciscosightseeing.com, 7% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (565 ms) belongs to the original domain Sanfranciscosightseeing.com.
Page size can be reduced by 294.3 kB (18%)
1.7 MB
1.4 MB
In fact, the total size of Sanfranciscosightseeing.com main page is 1.7 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. 40% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 35.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. 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 35.3 kB or 83% of the original size.
Potential reduce by 42.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. San Francisco Sightseeing images are well optimized though.
Potential reduce by 166.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 166.0 kB or 71% of the original size.
Potential reduce by 50.1 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. Sanfranciscosightseeing.com needs all CSS files to be minified and compressed as it can save up to 50.1 kB or 79% of the original size.
Number of requests can be reduced by 19 (44%)
43
24
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of San Francisco Sightseeing. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
sanfranciscosightseeing.com
173 ms
en
117 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
71 ms
css_vZ_wrMQ9Og-YPPxa1q4us3N7DsZMJa-14jShHgRoRNo.css
139 ms
css_8qbdSouD-7IGaCZYrjcAAUaT5s6PvldRn484Uayuvik.css
206 ms
css_UnYrCs7KCDFf_NWIhGcz1jvmmQkBUycEED8ySEU_mds.css
207 ms
css_rBojg_C3s11Fxa5odV6ltpNQrVX5CCWZwanXFkNF5us.css
209 ms
css_rOBXeOq9L13zN16SAzZ1mo3phokuyGfKHiMcxjoCmYk.css
212 ms
jquery.js
280 ms
jquery.once.js
215 ms
drupal.js
274 ms
views_slideshow.js
276 ms
jquery.bgiframe.js
295 ms
jquery.hoverIntent.js
279 ms
superfish.js
278 ms
nice_menus.js
341 ms
jquery.cycle.all.min.js
413 ms
views_slideshow_cycle.js
349 ms
googleanalytics.js
345 ms
common.js
347 ms
jquery.formalize.js
348 ms
omega-mediaqueries.js
406 ms
analytics.js
70 ms
bg-blue.jpg
82 ms
bg-city.png
148 ms
logo.png
280 ms
fb.png
147 ms
golden-gate-bridge.jpg
255 ms
bg.png
80 ms
GoldenGate.jpg
220 ms
cable_car.jpg
491 ms
grand2_0.jpg
287 ms
muir.jpg
285 ms
sfss5.jpg
494 ms
yosemite_national.jpg
391 ms
Yosemite2_0.jpg
415 ms
monterey-golf-panorama.jpg
353 ms
MontereyBay.jpg
423 ms
wine_panoramic_wine.jpg
491 ms
Napavalleyvineyard.jpg
528 ms
img-1.jpg
564 ms
img-2_0.jpg
565 ms
arrow-right.png
564 ms
collect
12 ms
fb.png
423 ms
collect
4 ms
sanfranciscosightseeing.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
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
Form elements do not have associated labels
sanfranciscosightseeing.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
sanfranciscosightseeing.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sanfranciscosightseeing.com 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 Sanfranciscosightseeing.com 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.
sanfranciscosightseeing.com
Open Graph description is not detected on the main page of San Francisco Sightseeing. 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: