1.7 sec in total
100 ms
1.3 sec
308 ms
Welcome to sandiegowhalewatching.com homepage info - get ready to check San Diego Whale Watching best content right away, or after learning these important things about sandiegowhalewatching.com
San Diego is one of the best locations in the world for whale watching and dolphin adventures! Join us on year-round tours & experience nature & stunning views!
Visit sandiegowhalewatching.comWe analyzed Sandiegowhalewatching.com page load time and found that the first response time was 100 ms and then it took 1.6 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.
sandiegowhalewatching.com performance score
name
value
score
weighting
Value14.8 s
0/100
10%
Value35.3 s
0/100
25%
Value30.4 s
0/100
10%
Value33,330 ms
0/100
30%
Value0.783
5/100
15%
Value97.2 s
0/100
10%
100 ms
140 ms
117 ms
98 ms
143 ms
Our browser made a total of 156 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Sandiegowhalewatching.com, 55% (86 requests) were made to Cityexperiences.com and 13% (21 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (928 ms) relates to the external source My.cityexperiences.com.
Page size can be reduced by 849.9 kB (34%)
2.5 MB
1.7 MB
In fact, the total size of Sandiegowhalewatching.com main page is 2.5 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. Only a small number of websites need less resources to load. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 387.5 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 387.5 kB or 83% of the original size.
Potential reduce by 0 B
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 Diego Whale Watching images are well optimized though.
Potential reduce by 457.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 457.4 kB or 25% of the original size.
Potential reduce by 5.0 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. Sandiegowhalewatching.com has all CSS files already compressed.
Number of requests can be reduced by 112 (85%)
132
20
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of San Diego Whale Watching. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 87 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
sandiegowhalewatching.com
100 ms
140 ms
autoptimize_2945ee4b273a1549074e183c356ae863.css
117 ms
autoptimize_single_f0a21b1ef4a430d4261638f4256fb783.css
98 ms
css
143 ms
animate.min.css
103 ms
font-awesome.min.css
105 ms
bootstrap.min.css
86 ms
ekko-lightbox.css
145 ms
mui.min.css
168 ms
autoptimize_single_f3bc779100ee8c39623386b00d8ba5d0.css
97 ms
autoptimize_single_196404bab8c125cb8f0bad580f4d7f76.css
94 ms
slick.min.css
159 ms
autoptimize_single_e5d706b050e4b6666e484eb30a9e3f11.css
150 ms
daterangepicker.min.css
149 ms
main.min.css
142 ms
select2.min.css
140 ms
autoptimize_single_2ed42af9a672959f6a1baba2df4d1ab5.css
159 ms
autoptimize_single_8bca77fc83a21799193da01768ee659d.css
215 ms
autoptimize_single_8a49c5a89ef908273daff6913bf83147.css
204 ms
autoptimize_single_9a9ec6e7b73d6ba2d58ab1b040dc4391.css
301 ms
autoptimize_single_fe2ca4662d6e95b97d65ba2b64a99617.css
168 ms
autoptimize_single_e8661b85db07042b015335f42951b9b2.css
205 ms
autoptimize_single_cfcf1453ff34ec26769c613d970586fa.css
198 ms
autoptimize_single_b2dc63d6587ba3f6fc78cbd58617ee20.css
188 ms
js_composer.min.css
226 ms
lodash.min.js
242 ms
wp-polyfill-inert.min.js
220 ms
regenerator-runtime.min.js
223 ms
wp-polyfill.min.js
243 ms
autop.min.js
243 ms
blob.min.js
243 ms
block-serialization-default-parser.min.js
247 ms
react.min.js
249 ms
hooks.min.js
263 ms
deprecated.min.js
261 ms
dom.min.js
275 ms
react-dom.min.js
267 ms
escape-html.min.js
269 ms
element.min.js
280 ms
is-shallow-equal.min.js
283 ms
i18n.min.js
287 ms
keycodes.min.js
332 ms
priority-queue.min.js
333 ms
compose.min.js
333 ms
popper.min.js
142 ms
ekko-lightbox.min.js
160 ms
bootstrap.min.js
140 ms
mustache.min.js
150 ms
moment.min.js
156 ms
daterangepicker.min.js
140 ms
main.min.js
148 ms
select2.min.js
149 ms
slick.min.js
158 ms
optimize.js
174 ms
top_experiences.js
928 ms
FA__DOMContentLoadedEventDispatcher.js
141 ms
enterprise.js
146 ms
mui.min.js
143 ms
6070.js
400 ms
polyfill.min.js
142 ms
sdk.js
178 ms
tour.js
538 ms
autoptimize_single_8ce5a994f3f83897eb46e555087edd0b.css
314 ms
private-apis.min.js
247 ms
redux-routine.min.js
246 ms
data.min.js
244 ms
html-entities.min.js
241 ms
shortcode.min.js
246 ms
blocks.min.js
221 ms
dom-ready.min.js
197 ms
css2
24 ms
css2
27 ms
a11y.min.js
191 ms
url.min.js
179 ms
ChatButtonCityCruises
71 ms
api-fetch.min.js
163 ms
moment.min.js
159 ms
date.min.js
152 ms
primitives.min.js
162 ms
rich-text.min.js
152 ms
warning.min.js
146 ms
components.min.js
155 ms
keyboard-shortcuts.min.js
134 ms
notices.min.js
142 ms
preferences-persistence.min.js
143 ms
preferences.min.js
144 ms
style-engine.min.js
145 ms
token-list.min.js
148 ms
wordcount.min.js
150 ms
block-editor.min.js
152 ms
core-data.min.js
145 ms
media-utils.min.js
137 ms
reusable-blocks.min.js
140 ms
server-side-render.min.js
144 ms
editor.min.js
142 ms
jquery.min.js
143 ms
jquery-migrate.min.js
148 ms
autoptimize_single_646770b51e7bdb72f5e6d8bc9a007dcd.js
108 ms
autoptimize_single_204c06bd8fe811ad891b5e35cbe2a042.js
112 ms
autoptimize_single_b462da7198b22d70182b59781e191b9d.js
112 ms
autoptimize_single_886e016515f5de3bd7d6f6b7a77fbb4b.js
114 ms
autoptimize_single_237327d753042111b351ca79666c2e53.js
112 ms
hb_cookie_required.js
175 ms
hb_cookie_performance.js
175 ms
hb_cookie_functional.js
174 ms
hb_cookie_targeting.js
174 ms
hb_cookie_social.js
173 ms
js_composer_front.min.js
174 ms
main.latest.js
174 ms
autoptimize_4123cdb9502771a17ea9ceb722d25cf2.js
174 ms
j.php
121 ms
CE-Logo-CMYK-Horizontal-FullColor400.png
119 ms
loading-gif.gif
302 ms
CITY-EXPERIENCES-TM.svg
306 ms
CITY-CRUISES-TM.svg
304 ms
NIAGARA-CITY-CRUISES-TM.svg
304 ms
BOSTON-HARBOR-CITY-CRUISES-TM.svg
437 ms
ALCATRAZ-CITY-CRUISES-TM.svg
441 ms
STATUE-CITY-CRUISES-TM.svg
439 ms
WALKS.svg
440 ms
DEVOUR.svg
436 ms
CITY-FERRY-ANCHORED-BY-HORNBLOWER-TM.svg
437 ms
wgarrowdown.png
42 ms
rect_mate.png
46 ms
pxiEyp8kv8JHgFVrFJA.ttf
155 ms
pxiByp8kv8JHgFVrLGT9V1s.ttf
353 ms
pxiByp8kv8JHgFVrLDz8V1s.ttf
417 ms
pxiByp8kv8JHgFVrLFj_V1s.ttf
416 ms
pxiGyp8kv8JHgFVrLPTedw.ttf
414 ms
pxiByp8kv8JHgFVrLEj6V1s.ttf
414 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
383 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
384 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
426 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
423 ms
fontawesome-webfont.woff
50 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYi1UA.ttf
427 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4i1UA.ttf
426 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYi1UA.ttf
427 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-1UA.ttf
427 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-1UA.ttf
467 ms
pxiGyp8kv8JHgFVrJJLedw.ttf
405 ms
pxiDyp8kv8JHgFVrJJLmg1hlEA.ttf
463 ms
pxiDyp8kv8JHgFVrJJLm21llEA.ttf
463 ms
pxiDyp8kv8JHgFVrJJLmv1plEA.ttf
463 ms
pxiAyp8kv8JHgFVrJJLmE3tF.ttf
463 ms
pxiDyp8kv8JHgFVrJJLmr19lEA.ttf
464 ms
wforms-3-11.js
268 ms
Icon-simple-instagram.svg
301 ms
Icon-simple-facebook.svg
301 ms
Icon-simple-tiktok.svg
299 ms
x-twitter-brands-solid-1.svg
300 ms
recaptcha__en.js
332 ms
app.js
283 ms
utag.js
280 ms
main.js
78 ms
sandiegowhalewatching.com accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
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.
sandiegowhalewatching.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
sandiegowhalewatching.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 Sandiegowhalewatching.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 Sandiegowhalewatching.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.
sandiegowhalewatching.com
Open Graph data is detected on the main page of San Diego Whale Watching. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: