1.8 sec in total
12 ms
1.5 sec
254 ms
Click here to check amazing Community Okta content for United States. Otherwise, check out these important facts you probably never knew about community.okta.com
Visit community.okta.comWe analyzed Community.okta.com page load time and found that the first response time was 12 ms and then it took 1.8 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.
community.okta.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value7.0 s
6/100
25%
Value4.9 s
64/100
10%
Value20 ms
100/100
30%
Value0.078
94/100
15%
Value6.8 s
55/100
10%
12 ms
519 ms
7 ms
14 ms
73 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Community.okta.com, 64% (21 requests) were made to Support.okta.com and 27% (9 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (519 ms) relates to the external source Support.okta.com.
Page size can be reduced by 682.2 kB (73%)
937.3 kB
255.1 kB
In fact, the total size of Community.okta.com main page is 937.3 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. 25% of websites need less resources to load. Javascripts take 892.0 kB which makes up the majority of the site volume.
Potential reduce by 24.1 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 24.1 kB or 53% of the original size.
Potential reduce by 658.1 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 658.1 kB or 74% of the original size.
Number of requests can be reduced by 11 (50%)
22
11
The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Community Okta. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
community.okta.com
12 ms
community
519 ms
stub.js
7 ms
functions.js
14 ms
main.js
73 ms
en_US.js
35 ms
desktopAjax.js
35 ms
picklist.js
35 ms
help-center.min.js
182 ms
VFState.js
40 ms
vendor.min.css
57 ms
all.css
65 ms
community-home.css
181 ms
NetworkTracking.js
64 ms
support.okta.com
208 ms
collect
47 ms
banner-medium-blue-pattern.png
98 ms
T
141 ms
T
140 ms
T
91 ms
T
140 ms
T
141 ms
T
299 ms
KVSoBhzrCzhjzIizNeqz2Ck5az7a_Mahp7A59cHuNQtffHV3gsMdeMJ6Mk6f5Mb.woff
46 ms
ZPknmvaJ7OkkH7BVJmIecJUIq06pnU7AJoio6EY_zKtffHY3gsMdeMJ6Mk6f5Mw.woff
79 ms
Uhoh7WKz7NCVTi3ZpxOYcobBnzl9o73D2QSOuPniCh3ff4x3gsMdeMJ6Mk6f5MI.woff
111 ms
3QUA9b820pm24P8uwCC-V2a_MVXq4hd4ldMFw0sZ5wMffHL3gsMdeMJ6Mk6f5Mj.woff
121 ms
HtoYSVzeXRfn1VHNmwd0wQ_KH8H5OYRuB9zzbqrn0ejffH13gsMdeMJ6Mk6f5MS.woff
142 ms
help-center-icons.woff
43 ms
TdMb1329Rq12Br0YdvDSQ2dEXCsHX9stpz6rMzGxtNSffJ2bMUMdeMJ6Mk6g5MBfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
143 ms
7GzvysT_A4EM3wEMO3USKgQPmE5wfHwwoltI59n0iW6ffV_VMUMdeMJ6Mk6g5MFfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
142 ms
MgrFnfOfAjTImex9j-8l2_Gm4lKXxsFh150emrADeYSffJWbMUMdeMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
141 ms
p.gif
127 ms
community.okta.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
Image elements do not have [alt] attributes
Links do not have a discernible name
community.okta.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
community.okta.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Community.okta.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 Community.okta.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.
community.okta.com
Open Graph description is not detected on the main page of Community Okta. 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: