1.2 sec in total
473 ms
762 ms
0 ms
Click here to check amazing Go Viator content for United States. Otherwise, check out these important facts you probably never knew about go.viator.com
Find and book city tours, helicopter tours, day trips, show tickets, sightseeing day tours, popular activities and things to do in hundreds of destinations worldwide
Visit go.viator.comWe analyzed Go.viator.com page load time and found that the first response time was 473 ms and then it took 762 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
go.viator.com performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value6.5 s
9/100
25%
Value5.6 s
53/100
10%
Value5,260 ms
0/100
30%
Value0
100/100
15%
Value22.2 s
1/100
10%
473 ms
90 ms
96 ms
106 ms
105 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Go.viator.com, 2% (1 request) were made to Viator.com. The less responsive or slowest element that took the longest time to load (473 ms) relates to the external source Viator.com.
Page size can be reduced by 207.8 kB (81%)
255.4 kB
47.6 kB
In fact, the total size of Go.viator.com main page is 255.4 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. 70% of websites need less resources to load. HTML takes 255.4 kB which makes up the majority of the site volume.
Potential reduce by 207.8 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 207.8 kB or 81% of the original size.
Number of requests can be reduced by 57 (90%)
63
6
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Go Viator. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.viator.com
473 ms
elasticApm.f14bc83b.js
90 ms
HOME.9fd2af3c.css
96 ms
GoogleTagManager.6817.475c28e2.css
106 ms
NavigationOverlay.9945.7bd1e630.css
105 ms
HelpNavItem.6687.76b23e87.css
106 ms
HeroShelf.8207.8c37d40b.css
103 ms
HeroSlider.6115.03e31323.css
99 ms
TopDestinationsShelf.7851.8a16c82b.css
107 ms
Slider.1754.99b899af.css
113 ms
TopAttractionsShelf.5009.cac07efe.css
111 ms
TopToursShelf.623.82be33e6.css
112 ms
WarmDestinationsShelf.7831.283605a0.css
108 ms
FooterForViator.5310.71ac323f.css
106 ms
flag_en.png
144 ms
nophoto360x240.png
143 ms
get-on-google-play.svg
137 ms
download-on-app-store.svg
132 ms
vendor-758c3076.a23fc0fe.js
131 ms
vendor-49d0a293.e00348e4.js
139 ms
vendor-5990cceb.1be7fcc4.js
138 ms
vendor-72fcc22f.47cd9072.js
142 ms
vendor-82cc9b98.0adf93fb.js
140 ms
vendor-d2eb5610.2da3ed48.js
143 ms
vendor-2b4841d6.4d303f3b.js
145 ms
vendor-d77768cf.f1d6e30f.js
141 ms
vendor-790b778e.40aac6da.js
146 ms
vendor-bb3d84b5.d30f3ed9.js
142 ms
vendor-f82e0cd2.28eb0e63.js
143 ms
vendor-ed7dbfea.350ae13c.js
144 ms
vendor-03f1fe65.6c4c732f.js
151 ms
vendor-0bc0478e.7c3dc3cd.js
154 ms
vendor-79baf4e4.2ff0135b.js
145 ms
vendor-e8ee3528.73d64711.js
152 ms
vendor-e5bca7e4.29899443.js
151 ms
vendor-21c62866.a5e1493b.js
150 ms
vendor-27545368.f7e2f86f.js
152 ms
9515.19a11426.js
93 ms
3389.f3e8c24f.js
87 ms
5252.b5f347b5.js
84 ms
HOME.9fd2af3c.js
82 ms
GoogleTagManager-475c28e2.js
78 ms
HelpCenterProvider-b3519fef.js
80 ms
9526-9bd8bee1.js
81 ms
NavigationOverlay-7bd1e630.js
79 ms
LanguageNavItem-85946006.js
80 ms
CurrencyNavItem-47b925e0.js
78 ms
HelpNavItem-76b23e87.js
78 ms
BookingsNavItem-44574865.js
44 ms
AccountNavItem-d4ae9cb4.js
45 ms
1374.6f16a54b.js
43 ms
8807-896acc2a.js
50 ms
6964.7cafaa10.js
43 ms
HeroShelf-8c37d40b.js
40 ms
HeroSlider-03e31323.js
41 ms
TopDestinationsShelf-8a16c82b.js
41 ms
Slider-99b899af.js
42 ms
880-b2ed95fc.js
41 ms
TopAttractionsShelf-cac07efe.js
41 ms
2693.f8926507.js
40 ms
TopToursShelf-82be33e6.js
40 ms
WarmDestinationsShelf-283605a0.js
40 ms
FooterForViator-71ac323f.js
40 ms
HelpCenter-2c17a858.js
40 ms
go.viator.com accessibility score
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
Form elements do not have associated labels
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.
go.viator.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
go.viator.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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Go.viator.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Go.viator.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.
go.viator.com
Open Graph data is detected on the main page of Go Viator. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: