ilsos.gov

ilsos.gov is SSL secured

Free website and domain report on ilsos.gov

Last Updated: 7th October, 2022 Update Now
Overview

Snoop Summary for ilsos.gov

This is a free and comprehensive report about ilsos.gov. Ilsos.gov is hosted in Springfield, Illinois in United States on a server with an IP address of 199.15.3.90, where the local currency is USD and English is the local language. Our records indicate that ilsos.gov is owned/operated by Illinois Secretary of State. Ilsos.gov is expected to earn an estimated $230 USD per day from advertising revenue. The sale of ilsos.gov would possibly be worth $167,748 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Ilsos.gov is wildly popular with an estimated 54,335 daily unique visitors. This report was last updated 7th October, 2022.

About ilsos.gov

Site Preview: ilsos.gov ilsos.gov
Title:
Description: Office of the Illinois Secretary of State, Illinois Secretary of State, Illinois Secretary of State Jesse White
Keywords and Tags: change address on driving licence, dmv chicago, dmv naperville, government, illinois, joliet dmv, lake zurich dmv, lombard dmv, midlothian dmv, military, popular, real id, real id illinois, schaumburg dmv, secretary of state
Related Terms: ameren illinois, ameren illinois login, illinois attorney general, illinois attorney general kwame raoul, multi state, ri secretary of state, state refund, state scoop, ts jesse, va state refund
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

3/5 (Great!)

Valuation

$167,748 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 19,668
Alexa Reach:
SEMrush Rank (US): 5,534
SEMrush Authority Score: 53
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 64,164 0
Traffic: 541,003 0
Cost: $323,565 USD $0 USD
Traffic

Visitors

Daily Visitors: 54,335
Monthly Visitors: 1,653,795
Yearly Visitors: 19,832,378
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $230 USD
Monthly Revenue: $6,994 USD
Yearly Revenue: $83,869 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 114,044
Referring Domains: 2,853
Referring IPs: 4,121
Ilsos.gov has 114,044 backlinks according to SEMrush. 69% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve ilsos.gov's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
99% of ilsos.gov's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://lowendbox.com/page/57/
Target: https://www.ilsos.gov/corporatellc/

2
Source: http://lowendbox.com/page/58/
Target: https://www.ilsos.gov/corporatellc/

3
Source: https://lowendbox.com/page/56/
Target: https://www.ilsos.gov/corporatellc/

4
Source: http://uk.koego.com/search?q=ceac%20visa%20check
Target: https://www.ilsos.gov/facilityfinder/facilityfinder?command=getFacilityDetails&facilityId=209

5
Source: http://uk.koego.com/search?q=ceac%20visa%20check
Target: https://www.ilsos.gov/facilityfinder/facilityfinder?command=getFacilityDetails&facilityId=209

Top Ranking Keywords (US)

1
Keyword: real id illinois
Ranked Page: https://realid.ilsos.gov/

2
Keyword: dmv chicago
Ranked Page: https://www.ilsos.gov/facilityfinder/facilityfinder?command=getFacilityDetails&facilityId=306

3
Keyword: change address on driving licence
Ranked Page: https://www.ilsos.gov/addrchange/

4
Keyword: real id
Ranked Page: https://realid.ilsos.gov/

5
Keyword: lombard dmv
Ranked Page: https://www.ilsos.gov/facilityfinder/facilityfinder?command=getFacilityDetails&facilityId=251

Domain Analysis

Value Length
Domain: ilsos.gov 9
Domain Name: ilsos 5
Extension (TLD): gov 3

Page Speed Analysis

Average Load Time: 0.41 seconds
Load Time Comparison: Faster than 97% of sites

PageSpeed Insights

Avg. (All Categories) 78
Performance 92
Accessibility 93
Best Practices 83
SEO 100
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.ilsos.gov/
Updated: 9th September, 2022

0.97 seconds
First Contentful Paint (FCP)
89%
7%
4%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
92

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for ilsos.gov. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.9 s
The time taken for the page to become fully interactive.
Speed Index — 0.9 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 0.9 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://ilsos.gov/
http/1.1
0
70.764999953099
340
0
302
text/html
https://www.ilsos.gov/
h2
71.155999903567
159.37599993777
3634
11519
200
text/html
Document
https://www.ilsos.gov/dist/bs3-3-5/css/bootstrap.css
h2
166.85299994424
238.00099990331
21970
148368
200
text/css
Stylesheet
https://www.ilsos.gov/css/bs3-3-5/custom.css
h2
167.16599999927
252.5729999179
14208
80374
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Roboto:100,300,400,700
h2
167.58099989966
174.90799992811
1536
8196
200
text/css
Stylesheet
https://www.ilsos.gov/scripts/bs3-3-5/nav.js
h2
167.85500000697
228.83699997328
3747
18572
200
application/x-javascript
Script
https://www.ilsos.gov/images/banners/banner-home.jpg
h2
257.89599993732
370.84099999629
59201
58910
200
image/jpeg
Image
https://www.lifegoeson.com/images/sunsmall-li.gif
h2
258.09899996966
374.42599993665
1291
1002
200
image/gif
Image
https://www.ilsos.gov/assets/js/jquery.min.js
h2
239.62199990638
394.54000000842
31297
89500
200
application/x-javascript
Script
https://www.ilsos.gov/dist/bs3-3-5/js/bootstrap.min.js
h2
253.93499992788
305.21799996495
10095
36816
200
application/x-javascript
Script
https://www.ilsos.gov/dist/js/grids.min.js
h2
257.69899995066
302.75799997617
1031
1648
200
application/x-javascript
Script
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
265.29299991671
268.82399991155
11968
11040
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
265.51299996208
269.42299993243
11955
11028
200
font/woff2
Font
https://s.swiftypecdn.com/install/v2/st.js
http/1.1
449.58999997471
490.80599995796
112698
425591
200
text/javascript
Script
https://s.swiftypecdn.com/install/v2/config/hsQtvysn1PapoCJzXVZa.json
http/1.1
557.84999998286
580.41799999774
5160
18753
200
application/json
XHR
https://www.ilsos.gov/images/logo/ilsosgov.png
h2
563.64800001029
625.01600000542
10329
10039
200
image/png
Image
https://www.ilsos.gov/images/seal/seal_black.png
h2
564.00799995754
610.40099989623
10440
10150
200
image/png
Image
https://www.ilsos.gov/images/logo/websitenamegray.png
h2
564.51699999161
658.04899996147
4376
4088
200
image/png
Image
https://www.ilsos.gov/images/icons/facebook.png
h2
564.80399996508
614.13399991579
657
370
200
image/png
Image
https://www.ilsos.gov/images/icons/instagram.png
h2
565.26399997529
584.42899992224
3933
3645
200
image/png
Image
https://www.ilsos.gov/images/icons/twitter.png
h2
565.53999998141
579.9639999168
871
584
200
image/png
Image
https://www.ilsos.gov/images/icons/youtube.png
h2
565.7919999212
713.61999993678
1018
731
200
image/png
Image
https://www.ilsos.gov/images/home_images/searchwhite.svg
h2
569.77099995129
634.17599990498
1053
1315
200
image/svg+xml
Image
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
h2
572.13599991519
575.83099999465
12088
11160
200
font/woff2
Font
https://s.swiftypecdn.com/assets/new_embed-91517c1e71e10890e4017d4c45b2dcd307c1d94998b851abdeefd8780de40d90.css
http/1.1
596.72799997497
1276.801
34451
91625
200
text/css
Stylesheet
https://cc.swiftype.com/cc.js?engine_key=Wk6kxJaxUJD58rziZ12g&url=https%3A%2F%2Fwww.ilsos.gov%2F
http/1.1
1325.588000007
1535.7849999564
279
43
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
164.396
10.559
240.088
6.102
259.74
17.568
282
13.139
404.14
20.029
424.629
26.605
512.606
48.415
561.311
24.178
593.509
7.284
602.113
14.914
1281.95
7.836
1304.929
21.684
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images — Potential savings of 6 KiB
Images can slow down the page's load time. Ilsos.gov should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.ilsos.gov/images/logo/ilsosgov.png
10039
6245
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ilsos.gov should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 8 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ilsos.gov should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.ilsos.gov/css/bs3-3-5/custom.css
14208
4638
https://www.ilsos.gov/dist/bs3-3-5/css/bootstrap.css
21970
3763
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ilsos.gov should consider minifying JS files.
Reduce unused CSS — Potential savings of 65 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ilsos.gov should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://s.swiftypecdn.com/assets/new_embed-91517c1e71e10890e4017d4c45b2dcd307c1d94998b851abdeefd8780de40d90.css
34451
33976
https://www.ilsos.gov/dist/bs3-3-5/css/bootstrap.css
21970
20653
https://www.ilsos.gov/css/bs3-3-5/custom.css
14208
11900
Reduce unused JavaScript — Potential savings of 68 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://s.swiftypecdn.com/install/v2/st.js
112698
69701
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 27 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.ilsos.gov/images/banners/banner-home.jpg
58910
27900.05
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 90 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.ilsos.gov/
89.216
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Ilsos.gov should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://ilsos.gov/
190
https://www.ilsos.gov/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ilsos.gov should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 8 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://s.swiftypecdn.com/install/v2/st.js
8257
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.ilsos.gov/images/banners/banner-home.jpg
0
Avoids enormous network payloads — Total size was 361 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://s.swiftypecdn.com/install/v2/st.js
112698
https://www.ilsos.gov/images/banners/banner-home.jpg
59201
https://s.swiftypecdn.com/assets/new_embed-91517c1e71e10890e4017d4c45b2dcd307c1d94998b851abdeefd8780de40d90.css
34451
https://www.ilsos.gov/assets/js/jquery.min.js
31297
https://www.ilsos.gov/dist/bs3-3-5/css/bootstrap.css
21970
https://www.ilsos.gov/css/bs3-3-5/custom.css
14208
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
12088
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
11968
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
11955
https://www.ilsos.gov/images/seal/seal_black.png
10440
Avoids an excessive DOM size — 273 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
273
Maximum DOM Depth
11
Maximum Child Elements
12
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ilsos.gov should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.ilsos.gov/
111.229
17.712
1.327
https://s.swiftypecdn.com/install/v2/st.js
83.893
71.226
5.825
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
123.031
Style & Layout
59.83
Other
53.124
Rendering
29.706
Parse HTML & CSS
16.28
Script Parsing & Compilation
10.233
Keep request counts low and transfer sizes small — 26 requests • 361 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
26
369626
Script
5
158868
Image
11
93448
Stylesheet
4
72165
Font
3
36011
Other
2
5500
Document
1
3634
Media
0
0
Third-party
9
191426
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
152588
0
37547
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.088969176845285
0.072143726593582
0.047919497282728
0.0024516982433055
0.00082556991142048
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ilsos.gov on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Cumulative Layout Shift — 0.212
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources — Potential savings of 480 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ilsos.gov should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.ilsos.gov/dist/bs3-3-5/css/bootstrap.css
21970
80
https://fonts.googleapis.com/css?family=Roboto:100,300,400,700
1536
230
Serve static assets with an efficient cache policy — 17 resources found
Ilsos.gov can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://s.swiftypecdn.com/install/v2/st.js
300000
112698
https://www.ilsos.gov/images/logo/websitenamegray.png
694177000
4376
https://www.ilsos.gov/images/banners/banner-home.jpg
694298000
59201
https://www.ilsos.gov/images/logo/ilsosgov.png
694335000
10329
https://www.ilsos.gov/images/seal/seal_black.png
697290000
10440
https://www.ilsos.gov/images/icons/twitter.png
697725000
871
https://www.ilsos.gov/images/icons/youtube.png
709600000
1018
https://www.ilsos.gov/images/icons/instagram.png
753550000
3933
https://www.ilsos.gov/images/icons/facebook.png
753550000
657
https://www.ilsos.gov/images/home_images/searchwhite.svg
757147000
1053
https://www.ilsos.gov/dist/bs3-3-5/css/bootstrap.css
1097279000
21970
https://www.ilsos.gov/assets/js/jquery.min.js
1183924000
31297
https://www.ilsos.gov/css/bs3-3-5/custom.css
1183951000
14208
https://www.ilsos.gov/dist/js/grids.min.js
1183964000
1031
https://www.ilsos.gov/dist/bs3-3-5/js/bootstrap.min.js
1190715000
10095
https://www.ilsos.gov/scripts/bs3-3-5/nav.js
1404637000
3747
https://www.lifegoeson.com/images/sunsmall-li.gif
2488288000
1291

Other

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
3.5309999948367
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
3.9099999703467
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
3.6950000794604
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.ilsos.gov/images/banners/banner-home.jpg
https://www.ilsos.gov/images/logo/ilsosgov.png
https://www.ilsos.gov/images/icons/facebook.png
https://www.ilsos.gov/images/icons/instagram.png
https://www.ilsos.gov/images/icons/twitter.png
https://www.ilsos.gov/images/icons/youtube.png
https://www.lifegoeson.com/images/sunsmall-li.gif
93

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ilsos.gov. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Ilsos.gov may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that ilsos.gov should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
3.3.5
jQuery
3.6.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://ilsos.gov/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
5
Medium
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for ilsos.gov. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ilsos.gov on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
22

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of ilsos.gov. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ilsos.gov on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 77
Performance 77
Accessibility 95
Best Practices 83
SEO 99
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.ilsos.gov/
Updated: 9th September, 2022

0.97 seconds
First Contentful Paint (FCP)
92%
5%
3%

0.01 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on mobile
77

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for ilsos.gov. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 50 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Audits

Max Potential First Input Delay — 130 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://ilsos.gov/
http/1.1
0
69.755000062287
340
0
302
text/html
https://www.ilsos.gov/
h2
70.038000121713
631.45300000906
3634
11519
200
text/html
Document
https://www.ilsos.gov/dist/bs3-3-5/css/bootstrap.css
h2
641.16499992087
1069.7079999372
21970
148368
200
text/css
Stylesheet
https://www.ilsos.gov/css/bs3-3-5/custom.css
h2
641.40899991617
848.17200014368
14208
80374
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Roboto:100,300,400,700
h2
641.73300005496
654.8509998247
1617
10093
200
text/css
Stylesheet
https://www.ilsos.gov/scripts/bs3-3-5/nav.js
h2
641.92199986428
722.47700020671
3747
18572
200
application/x-javascript
Script
https://www.ilsos.gov/images/banners/banner-home.jpg
h2
1076.9810001366
1234.8950002342
59201
58910
200
image/jpeg
Image
https://www.lifegoeson.com/images/sunsmall-li.gif
h2
1077.1110001951
1390.7650001347
1291
1002
200
image/gif
Image
https://www.ilsos.gov/assets/js/jquery.min.js
h2
849.65000022203
1180.2920000628
31296
89500
200
application/x-javascript
Script
https://www.ilsos.gov/dist/bs3-3-5/js/bootstrap.min.js
h2
1071.2410002016
1454.8450000584
10095
36816
200
application/x-javascript
Script
https://www.ilsos.gov/dist/js/grids.min.js
h2
1076.8340001814
1295.9650000557
1031
1648
200
application/x-javascript
Script
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
1084.0030000545
1090.8010001294
11968
11040
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
1084.8119999282
1091.1860000342
11956
11028
200
font/woff2
Font
https://s.swiftypecdn.com/install/v2/st.js
http/1.1
1475.1070002094
1507.4769998901
112698
425591
200
text/javascript
Script
https://s.swiftypecdn.com/install/v2/config/hsQtvysn1PapoCJzXVZa.json
http/1.1
1553.517000284
1577.0910000429
5160
18753
200
application/json
XHR
https://www.ilsos.gov/images/logo/ilsosgov.png
h2
1557.3940002359
1637.730000075
10330
10039
200
image/png
Image
https://www.ilsos.gov/images/seal/seal_black.png
h2
1557.5540000573
1750.492000021
10440
10150
200
image/png
Image
https://www.ilsos.gov/images/logo/websitenamegray.png
h2
1557.6949999668
1752.7999999002
4376
4088
200
image/png
Image
https://www.ilsos.gov/images/icons/facebook.png
h2
1557.9369999468
1830.3470001556
657
370
200
image/png
Image
https://www.ilsos.gov/images/icons/instagram.png
h2
1558.1370000727
1757.3850001208
3933
3645
200
image/png
Image
https://www.ilsos.gov/images/icons/twitter.png
h2
1558.3460000344
1638.2659999654
871
584
200
image/png
Image
https://www.ilsos.gov/images/icons/youtube.png
h2
1558.5779999383
1828.7639999762
1018
731
200
image/png
Image
https://www.ilsos.gov/images/home_images/searchwhite.svg
h2
1560.5160002597
1634.9539998919
1053
1315
200
image/svg+xml
Image
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
h2
1563.0769999698
1569.4889998995
12088
11160
200
font/woff2
Font
https://s.swiftypecdn.com/assets/new_embed-91517c1e71e10890e4017d4c45b2dcd307c1d94998b851abdeefd8780de40d90.css
http/1.1
1590.1359999552
1618.7410000712
34451
91625
200
text/css
Stylesheet
https://cc.swiftype.com/cc.js?engine_key=Wk6kxJaxUJD58rziZ12g&url=https%3A%2F%2Fwww.ilsos.gov%2F
http/1.1
1709.9830000661
1969.0350000747
279
43
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
635.341
11.165
1078.101
15.564
1097.364
7.822
1186.134
11.938
1462.69
12.966
1524.377
31.443
1556.1
16.809
1578.855
8.798
1622.258
11.148
1693.863
16.613
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Defer offscreen images — Potential savings of 17 KiB
Time to Interactive can be slowed down by resources on the page. Ilsos.gov should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.ilsos.gov/images/seal/seal_black.png
10150
10150
https://www.ilsos.gov/images/logo/websitenamegray.png
4088
4088
https://www.ilsos.gov/images/icons/instagram.png
3645
3645
Minify CSS — Potential savings of 8 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ilsos.gov should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.ilsos.gov/css/bs3-3-5/custom.css
14208
4638
https://www.ilsos.gov/dist/bs3-3-5/css/bootstrap.css
21970
3763
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ilsos.gov should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 560 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.ilsos.gov/
562.41
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Ilsos.gov should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://ilsos.gov/
630
https://www.ilsos.gov/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ilsos.gov should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 8 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://s.swiftypecdn.com/install/v2/st.js
8257
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 361 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://s.swiftypecdn.com/install/v2/st.js
112698
https://www.ilsos.gov/images/banners/banner-home.jpg
59201
https://s.swiftypecdn.com/assets/new_embed-91517c1e71e10890e4017d4c45b2dcd307c1d94998b851abdeefd8780de40d90.css
34451
https://www.ilsos.gov/assets/js/jquery.min.js
31296
https://www.ilsos.gov/dist/bs3-3-5/css/bootstrap.css
21970
https://www.ilsos.gov/css/bs3-3-5/custom.css
14208
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
12088
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
11968
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
11956
https://www.ilsos.gov/images/seal/seal_black.png
10440
Avoids an excessive DOM size — 273 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
273
Maximum DOM Depth
11
Maximum Child Elements
12
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ilsos.gov should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.ilsos.gov/
339.156
46.156
5.316
https://s.swiftypecdn.com/install/v2/st.js
229.248
189.86
23.492
https://www.ilsos.gov/assets/js/jquery.min.js
116.128
55.308
5.492
Unattributable
107.776
8.652
0.444
Minimizes main-thread work — 0.9 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
323.96
Style & Layout
201.816
Other
178.636
Rendering
75.284
Parse HTML & CSS
54.052
Script Parsing & Compilation
38.816
Keep request counts low and transfer sizes small — 26 requests • 361 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
26
369708
Script
5
158867
Image
11
93449
Stylesheet
4
72246
Font
3
36012
Other
2
5500
Document
1
3634
Media
0
0
Third-party
9
191508
Minimize third-party usage — Third-party code blocked the main thread for 60 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
152588
57.812
37629
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.16398391723633
0.09044549456089
0.0032354212716299
div
0.00067167154947917
0.00022596571180556
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://s.swiftypecdn.com/install/v2/st.js
4814
126
https://s.swiftypecdn.com/install/v2/st.js
5474
66
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ilsos.gov on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Time to Interactive — 4.8 s
The time taken for the page to become fully interactive.
Speed Index — 3.6 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 3.1 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 3.1 s
The time taken for the primary content of the page to be rendered.

Other

Properly size images — Potential savings of 22 KiB
Images can slow down the page's load time. Ilsos.gov should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.ilsos.gov/images/banners/banner-home.jpg
58910
22636
Reduce unused CSS — Potential savings of 65 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ilsos.gov should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://s.swiftypecdn.com/assets/new_embed-91517c1e71e10890e4017d4c45b2dcd307c1d94998b851abdeefd8780de40d90.css
34451
33573
https://www.ilsos.gov/dist/bs3-3-5/css/bootstrap.css
21970
20924
https://www.ilsos.gov/css/bs3-3-5/custom.css
14208
12434
Reduce unused JavaScript — Potential savings of 68 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://s.swiftypecdn.com/install/v2/st.js
112698
69701
Serve images in next-gen formats — Potential savings of 27 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.ilsos.gov/images/banners/banner-home.jpg
58910
27900.05
Serve static assets with an efficient cache policy — 17 resources found
Ilsos.gov can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://s.swiftypecdn.com/install/v2/st.js
300000
112698
https://www.ilsos.gov/assets/js/jquery.min.js
502213000
31296
https://www.ilsos.gov/images/banners/banner-home.jpg
694177000
59201
https://www.ilsos.gov/images/logo/websitenamegray.png
694205000
4376
https://www.ilsos.gov/images/icons/facebook.png
694955000
657
https://www.ilsos.gov/images/home_images/searchwhite.svg
696027000
1053
https://www.ilsos.gov/images/icons/youtube.png
696171000
1018
https://www.ilsos.gov/images/icons/twitter.png
697249000
871
https://www.ilsos.gov/images/seal/seal_black.png
713677000
10440
https://www.ilsos.gov/images/icons/instagram.png
930738000
3933
https://www.ilsos.gov/dist/bs3-3-5/js/bootstrap.min.js
1122484000
10095
https://www.ilsos.gov/dist/js/grids.min.js
1140474000
1031
https://www.ilsos.gov/css/bs3-3-5/custom.css
1172941000
14208
https://www.ilsos.gov/dist/bs3-3-5/css/bootstrap.css
1190628000
21970
https://www.ilsos.gov/scripts/bs3-3-5/nav.js
1404648000
3747
https://www.lifegoeson.com/images/sunsmall-li.gif
1562040000
1291
https://www.ilsos.gov/images/logo/ilsosgov.png
2247739000
10330

Metrics

First Contentful Paint — 3.1 s
The time taken for the first image or text on the page to be rendered.
Cumulative Layout Shift — 0.259
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources — Potential savings of 1,630 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ilsos.gov should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.ilsos.gov/dist/bs3-3-5/css/bootstrap.css
21970
300
https://www.ilsos.gov/css/bs3-3-5/custom.css
14208
150
https://fonts.googleapis.com/css?family=Roboto:100,300,400,700
1617
780
https://www.ilsos.gov/scripts/bs3-3-5/nav.js
3747
150
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
6.798000074923
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
6.3740001060069
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
6.4119999296963
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://www.ilsos.gov/images/banners/banner-home.jpg
https://www.ilsos.gov/images/logo/ilsosgov.png
https://www.ilsos.gov/images/icons/facebook.png
https://www.ilsos.gov/images/icons/instagram.png
https://www.ilsos.gov/images/icons/twitter.png
https://www.ilsos.gov/images/icons/youtube.png
https://www.lifegoeson.com/images/sunsmall-li.gif
First Contentful Paint (3G) — 6120 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ilsos.gov. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Ilsos.gov may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that ilsos.gov should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
3.3.5
jQuery
3.6.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://ilsos.gov/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
5
Medium
99

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for ilsos.gov. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ilsos.gov on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 98% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
58x36

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
30

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of ilsos.gov. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of ilsos.gov on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 199.15.3.90
Continent: North America
Country: United States
United States Flag
Region: Illinois
City: Springfield
Longitude: -89.7379
Latitude: 39.7647
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Illinois Secretary of State
Registration

Domain Registrant

Private Registration: No
Name:
Organization: Illinois Secretary of State
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 95/100
WOT Child Safety: 94/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: ilsos.gov
Issued By: Entrust Certification Authority - L1M
Valid From: 1st March, 2022
Valid To: 2nd March, 2023
Subject: CN = ilsos.gov
O = Illinois Secretary of State
L = Springfield
S = US
Hash: 920229a8
Issuer: CN = Entrust Certification Authority - L1M
OU = See www.entrust.net/legal-terms, (c) 2014 Entrust, Inc. - for authorized use only
O = Entrust, Inc.
S = US
Version: 2
Serial Number: 9912409819342211010302137604420939487
Serial Number (Hex): 07750F89540022F161CFD4677E942EDF
Valid From: 1st March, 2024
Valid To: 2nd March, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:C3:F7:D0:B5:2A:30:AD:AF:0D:91:21:70:39:54:DD:BC:89:70:C7:3A
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.entrust.net/level1m.crl

Certificate Policies: Policy: 2.16.840.1.114028.10.1.2
CPS: https://www.entrust.net/rpa
Policy: 2.23.140.1.1

Authority Information Access: OCSP - URI:http://ocsp.entrust.net
CA Issuers - URI:http://aia.entrust.net/l1m-chain256.cer

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Mar 1 17:14:15.547 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:83:33:7C:9B:7E:BA:10:76:10:71:45:
E7:93:6F:DA:24:5A:92:91:83:35:09:B3:65:13:28:BA:
5F:60:5E:FF:7B:02:21:00:B0:77:37:62:F6:89:D0:81:
D9:62:4C:C2:EA:CB:3F:E9:A9:A8:63:00:A9:F7:8D:65:
10:43:0E:5E:8C:61:E2:EC
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : Mar 1 17:14:15.626 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:D8:39:FD:C4:CE:EA:E6:23:76:22:BD:
FD:1F:D5:C5:6E:E5:17:5B:09:90:AB:2E:73:29:D1:B1:
58:BD:03:29:3B:02:20:4D:E3:AD:D2:B7:F2:70:9A:E1:
12:70:F8:4A:00:4B:13:BB:33:1A:51:7D:1E:F4:6C:45:
83:15:37:CB:98:0B:31
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Mar 1 17:14:15.604 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:8B:BD:6A:75:3E:A7:9F:EA:61:66:B6:
74:E0:7B:BC:44:E7:96:8F:D3:34:99:91:A3:16:BF:2D:
8F:40:23:F1:D2:02:20:53:95:27:88:F7:28:64:14:AA:
CA:1A:EB:92:EF:AE:3A:9C:DC:AE:F5:26:77:10:AC:A1:
EB:2D:B6:B3:F4:C4:D7
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:apps.ilsos.gov
DNS:avoidthescam.net
DNS:cyberdriveillinois.com
DNS:ilbph.org
DNS:illinoisliteracyfoundation.org
DNS:ilsos.net
DNS:lifegoeson.com
DNS:realid.ilsos.gov
DNS:reportitnow.net
DNS:search.ilsos.gov
DNS:secure.ilsos.gov
DNS:sosnet.ilsos.net
DNS:sostrpwb1.ilsos.net
DNS:theillinoisliteracyfoundation.org
DNS:www.avoidthescam.net
DNS:www.cyberdriveillinois.com
DNS:www.ilbph.org
DNS:www.illinoisliteracyfoundation.org
DNS:www.ilsos.gov
DNS:www.ilsos.net
DNS:www.lifegoeson.com
DNS:www.realid.ilsos.gov
DNS:www.reportitnow.net
DNS:www.theillinoisliteracyfoundation.org
DNS:ilsos.gov
Technical

DNS Lookup

A Records

Host IP Address Class TTL
ilsos.gov. 199.15.3.90 IN 300

NS Records

Host Nameserver Class TTL
ilsos.gov. ns1-36.azure-dns.com. IN 21600
ilsos.gov. ns2-36.azure-dns.net. IN 21600
ilsos.gov. ns3-36.azure-dns.org. IN 21600
ilsos.gov. ns4-36.azure-dns.info. IN 21600

MX Records

Priority Host Server Class TTL
10 ilsos.gov. mx1.hc4878-16.iphmx.com. IN 3600
10 ilsos.gov. mx2.hc4878-16.iphmx.com. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
ilsos.gov. ns1-36.azure-dns.com. azuredns-hostmaster.microsoft.com. 3600

TXT Records

Host Value Class TTL
ilsos.gov. \"Illinois IN 3600
ilsos.gov. v=spf1 IN 3600
ilsos.gov. cisco-ci-domain-verification=37258c85e5d24c368c51601d07915ced4dca2cd89f2cefdc012f99c601575683 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Content-Type: text/html
Cache-Control: max-age=180
Date: 9th September, 2022
Strict-Transport-Security: max-age=31536000; includeSubDomains
Last-Modified: 9th September, 2022
ETag: "2cff-5e84201215300"
Accept-Ranges: bytes
Content-Length: 11519
Connection: keep-alive

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns1-36.azure-dns.com
ns2-36.azure-dns.net
ns3-36.azure-dns.org
ns4-36.azure-dns.info
Full Whois: % DOTGOV WHOIS Server ready
Domain Name: ILSOS.GOV
Status: ACTIVE
Security Contact Email: SecurityAdministrator@ilsos.net

>>> Last update of whois database: 2022-10-07T10:56:49Z <<<

Please be advised that this whois server only contains information pertaining
to the .GOV domain. For information for other domains please use the whois
server at RS.INTERNIC.NET.

Nameservers

Name IP Address
ns1-36.azure-dns.com 150.171.10.36
ns2-36.azure-dns.net 150.171.16.36
ns3-36.azure-dns.org 13.107.222.36
ns4-36.azure-dns.info 13.107.206.36
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$32,421 USD 2/5
$335,216 USD 3/5
$65,365 USD 2/5
$15,196 USD 2/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address