1.7 sec in total
163 ms
1.2 sec
354 ms
Click here to check amazing Geotix content for United States. Otherwise, check out these important facts you probably never knew about geotix.com
Leverage the reach of our events network! Anyone can fulfill demand for your tickets… now let’s start increasing your demand.
Visit geotix.comWe analyzed Geotix.com page load time and found that the first response time was 163 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 30% of websites can load faster.
geotix.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value5.6 s
17/100
25%
Value11.4 s
5/100
10%
Value8,910 ms
0/100
30%
Value0.112
86/100
15%
Value29.3 s
0/100
10%
163 ms
151 ms
28 ms
39 ms
33 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Geotix.com, 36% (42 requests) were made to Fonts.gstatic.com and 33% (39 requests) were made to Evvnt.com. The less responsive or slowest element that took the longest time to load (315 ms) relates to the external source Googletagmanager.com.
Page size can be reduced by 196.2 kB (13%)
1.5 MB
1.3 MB
In fact, the total size of Geotix.com main page is 1.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 923.5 kB which makes up the majority of the site volume.
Potential reduce by 184.4 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 184.4 kB or 82% of the original size.
Potential reduce by 5 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. Geotix images are well optimized though.
Potential reduce by 11.7 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. This website has mostly compressed JavaScripts.
Potential reduce by 103 B
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. Geotix.com has all CSS files already compressed.
Number of requests can be reduced by 40 (63%)
64
24
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geotix. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
geotix.com
163 ms
evvnt.com
151 ms
pagenavi-css.css
28 ms
login.css
39 ms
jquery.min.js
33 ms
jquery-migrate.min.js
28 ms
jq-sticky-anything.min.js
46 ms
headerScript.min.js
87 ms
tp.min.js
28 ms
font-awesome.min.css
48 ms
event-creator.js
24 ms
js
68 ms
algoliasearch.min.js
33 ms
autocomplete.min.js
36 ms
MeetingsEmbedCode.js
65 ms
22104341.js
78 ms
stickThis.js
25 ms
scripts.min.js
25 ms
jquery.fitvids.js
31 ms
common.js
27 ms
fbevents.js
48 ms
evvntlogo.png
21 ms
evvnt_LinkedIn_Cover_Crowd-scaled-1-980x245-1.jpg
56 ms
gannett-usatoday-logo.png
61 ms
hearst-logo.png
56 ms
adams-publishing-group-logo.png
61 ms
The_Seattle_Times_logo.svg-4.png
61 ms
trib-total-media-logo.png
56 ms
wick-communications-logo.png
76 ms
soldout.png
194 ms
everythingyouneed.png
174 ms
trustpilot.png
77 ms
GoogleReviews.png
76 ms
yelp-reviews.png
77 ms
evnntlogoWHITE.png
195 ms
S6uyw4BMUTPHjxAwWA.woff
66 ms
S6uyw4BMUTPHjxAwWw.ttf
74 ms
S6u9w4BMUTPHh7USSwaPHw.woff
173 ms
S6u9w4BMUTPHh7USSwaPHA.ttf
194 ms
S6u8w4BMUTPHh30AUi-s.woff
242 ms
S6u8w4BMUTPHh30AUi-v.ttf
243 ms
S6u9w4BMUTPHh6UVSwaPHw.woff
195 ms
S6u9w4BMUTPHh6UVSwaPHA.ttf
242 ms
S6u9w4BMUTPHh50XSwaPHw.woff
241 ms
S6u9w4BMUTPHh50XSwaPHA.ttf
243 ms
places.js
50 ms
main.js
61 ms
cBjaQ0JcnRg
186 ms
maxresdefault.jpg
166 ms
evvnt-discovery-call
182 ms
et-divi-dynamic-37814-late.css
173 ms
0-6-1-270x270-1-150x150-2.jpg
173 ms
Evvnt_Rework_Final-Favicon-512-red-1.png
179 ms
1516855359794.jpg
252 ms
BebasNeue-Regular.ttf
178 ms
JTUSjIg69CK48gW7PXooxW4.ttf
172 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff
77 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
78 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff
79 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
80 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff
97 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
78 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff
98 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
175 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff
176 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf
176 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff
175 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
175 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff
175 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
205 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff
206 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf
206 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff
205 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf
206 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvgUE.ttf
175 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvgUE.ttf
175 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vgUE.ttf
174 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZogUE.ttf
173 ms
KFOlCnqEu92Fr1MmWUlfChc-.woff
205 ms
KFOlCnqEu92Fr1MmWUlfChc9.ttf
245 ms
KFOlCnqEu92Fr1MmYUtfChc-.woff
240 ms
KFOlCnqEu92Fr1MmYUtfChc9.ttf
245 ms
KFOlCnqEu92Fr1MmEU9fChc-.woff
240 ms
KFOlCnqEu92Fr1MmEU9fChc9.ttf
245 ms
KFOmCnqEu92Fr1Mu7GxM.woff
243 ms
KFOmCnqEu92Fr1Mu7GxP.ttf
277 ms
KFOlCnqEu92Fr1MmSU5fChc-.woff
281 ms
KFOlCnqEu92Fr1MmSU5fChc9.ttf
282 ms
modules.woff
209 ms
KFOkCnqEu92Fr1MmgVxGIzQ.woff
273 ms
www-player.css
65 ms
www-embed-player.js
126 ms
base.js
126 ms
bundle.production.js
159 ms
book-info-early-requester.js
161 ms
project_with_deps.css
195 ms
configure-monitoring.js
219 ms
bundle.production.js
219 ms
project.js
267 ms
KFOkCnqEu92Fr1MmgVxGIzc.ttf
257 ms
gtm.js
315 ms
fb.js
234 ms
collectedforms.js
245 ms
conversations-embed.js
276 ms
22104341.js
233 ms
banner.js
312 ms
cBjaQ0JcnRg
128 ms
main.js
63 ms
www-embed-player.js
50 ms
base.js
88 ms
style.min.css
36 ms
ad_status.js
155 ms
zF_vPuIB9TmKXIhqGvs4Q-1RpaRIMS8epygYjX9fevg.js
112 ms
embed.js
38 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
25 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
26 ms
id
20 ms
geotix.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
Links do not have a discernible name
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.
geotix.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
Browser errors were logged to the console
Page has valid source maps
geotix.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geotix.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 Geotix.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.
geotix.com
Open Graph data is detected on the main page of Geotix. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: