7.2 sec in total
2.5 sec
4.5 sec
234 ms
Welcome to oadaconvention.com homepage info - get ready to check OADA Convention best content right away, or after learning these important things about oadaconvention.com
Join us for the Oregon Auto Dealers Convention to learn from and network with the brightest minds in the automotive industry.
Visit oadaconvention.comWe analyzed Oadaconvention.com page load time and found that the first response time was 2.5 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
oadaconvention.com performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value7.7 s
3/100
25%
Value14.6 s
1/100
10%
Value3,710 ms
1/100
30%
Value0.003
100/100
15%
Value19.1 s
3/100
10%
2488 ms
184 ms
415 ms
416 ms
177 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Oadaconvention.com, 74% (49 requests) were made to Static.parastorage.com and 6% (4 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Oadaconvention.com.
Page size can be reduced by 534.5 kB (70%)
767.4 kB
232.9 kB
In fact, the total size of Oadaconvention.com main page is 767.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. 65% of websites need less resources to load. HTML takes 615.7 kB which makes up the majority of the site volume.
Potential reduce by 487.0 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 487.0 kB or 79% 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. OADA Convention images are well optimized though.
Potential reduce by 47.5 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 47.5 kB or 43% of the original size.
Number of requests can be reduced by 49 (83%)
59
10
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OADA Convention. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and as a result speed up the page load time.
www.oadaconvention.com
2488 ms
minified.js
184 ms
focus-within-polyfill.js
415 ms
polyfill.min.js
416 ms
bootstrap-features.6df73955.chunk.min.js
177 ms
main.c6b5464c.chunk.min.js
176 ms
lodash.min.js
404 ms
wix-code-sdk-providers.c2f86878.chunk.min.js
403 ms
ooi.16105056.chunk.min.js
570 ms
passwordProtectedPage.72a5f09f.chunk.min.js
542 ms
popups.6d75bea8.chunk.min.js
541 ms
protectedPages.65647ee8.chunk.min.js
545 ms
siteMembers.cee90d6a.chunk.min.js
538 ms
siteScrollBlocker.0fd920dd.chunk.min.js
564 ms
tpaCommons.eaa77134.chunk.min.js
570 ms
tpaWorkerFeature.81313689.chunk.min.js
569 ms
windowMessageRegistrar.60e90c5f.chunk.min.js
568 ms
platform.68d9ada1.chunk.min.js
567 ms
vendors~vendor-react-dom.be7a0676.chunk.min.js
567 ms
vendor-react-dom.6e25e583.chunk.min.js
567 ms
bolt-performance
503 ms
dynamicmodel
568 ms
clientWorker.db19ad4b.bundle.min.js
549 ms
bt
408 ms
bundle.min.js
102 ms
lodash.min.js
19 ms
171 ms
168 ms
149 ms
siteTags.bundle.min.js
459 ms
custom-elements-polyfill.60c09271.chunk.min.js
432 ms
intersection-observer-polyfill.96d30fa3.chunk.min.js
426 ms
thunderboltElements.1e33fcd2.bundle.min.js
426 ms
wix-perf-measure.bundle.min.js
417 ms
activePopup.ff089c32.chunk.min.js
416 ms
dropdownMenu.20f9fe1f.chunk.min.js
410 ms
navigation.f21c0173.chunk.min.js
408 ms
ooiTpaSharedConfig.61d7dd2f.chunk.min.js
402 ms
pageScroll.7cdf291c.chunk.min.js
427 ms
platformPubsub.6afb35b8.chunk.min.js
437 ms
scrollRestoration.32b2c330.chunk.min.js
428 ms
scrollToAnchor.3399e623.chunk.min.js
439 ms
tpa.b483b055.chunk.min.js
436 ms
windowScroll.c190b90c.chunk.min.js
435 ms
backgroundScrub.96774c06.chunk.min.js
438 ms
imageZoom.b662d71b.chunk.min.js
431 ms
pageAnchors.bc7f37fb.chunk.min.js
447 ms
pageTransitions.7896637d.chunk.min.js
427 ms
bootstrap-components.28631e6e.chunk.min.js
427 ms
GoogleMap.bee7c76f.chunk.min.js
440 ms
SiteButton_ButtonLiftedShadow.816ce4ec.chunk.min.js
445 ms
TPA3DCarousel.516c8542.chunk.min.js
447 ms
DropDownMenu_TextSeparatorsMenuButtonSkin.aa2a0be0.chunk.min.js
442 ms
FooterContainer_BevelScreen.a538cc4f.chunk.min.js
445 ms
FiveGridLine.caf9f338.chunk.min.js
447 ms
PinnedLayer.273568ae.chunk.min.js
446 ms
tpa-components.8b2229f2.chunk.min.js
453 ms
feed-page-viewer.min.css
532 ms
ee0c22_9d5d9c0346f74843ae90a2d6853294ce~mv2.png
588 ms
ee0c22_f48818e4171040cdbd554a9897b01ace~mv2_d_3000_1976_s_2.jpg
827 ms
ee0c22_f48818e4171040cdbd554a9897b01ace~mv2_d_3000_1976_s_2.jpg
894 ms
a27d24_74a5c4593cc1454683305dbaa50c80cb~mv2_d_1880_1560_s_2.png
708 ms
WmVKXVcOuffP_qmCpFuyzRsxEYwM7FgeyaSgU71cLG0.woff
480 ms
STBOO2waD2LpX45SXYjQBRsxEYwM7FgeyaSgU71cLG0.woff
480 ms
bt
170 ms
908c4810-64db-4b46-bb8e-823eb41f68c0.woff
27 ms
oadaconvention.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
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
oadaconvention.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
Missing source maps for large first-party JavaScript
oadaconvention.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Oadaconvention.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 Oadaconvention.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.
oadaconvention.com
Open Graph data is detected on the main page of OADA Convention. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: