skokie.org

skokie.org is SSL secured

Free website and domain report on skokie.org

Last Updated: 25th March, 2021 Update Now
Overview

Snoop Summary for skokie.org

This is a free and comprehensive report about skokie.org. Skokie.org is hosted in United States on a server with an IP address of 207.38.72.42, where the local currency is USD and English is the local language. Skokie.org has the potential to be earning an estimated $3 USD per day from advertising revenue. If skokie.org was to be sold it would possibly be worth $1,932 USD (based on the daily revenue potential of the website over a 24 month period). Skokie.org is somewhat popular with an estimated 924 daily unique visitors. This report was last updated 25th March, 2021.

About skokie.org

Site Preview: skokie.org skokie.org
Title: Village of Skokie, Illinois
Description: Information on Village departments, community history and area news.
Keywords and Tags: government, home, military
Related Terms:
Fav Icon:
Age: Over 27 years old
Domain Created: 12th January, 1997
Domain Updated: 6th April, 2020
Domain Expires: 30th November, 2022
Review

Snoop Score

2/5

Valuation

$1,932 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 848,296
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 924
Monthly Visitors: 28,124
Yearly Visitors: 337,260
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $3 USD
Monthly Revenue: $80 USD
Yearly Revenue: $961 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: skokie.org 10
Domain Name: skokie 6
Extension (TLD): org 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.43 seconds
Load Time Comparison: Faster than 93% of sites

PageSpeed Insights

Avg. (All Categories) 67
Performance 51
Accessibility 92
Best Practices 73
SEO 82
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.skokie.org/
Updated: 25th March, 2021

1.81 seconds
First Contentful Paint (FCP)
29%
63%
8%

0.03 seconds
First Input Delay (FID)
89%
7%
4%

Simulate loading on desktop
51

Performance

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

Opportunities

Properly size images — Potential savings of 567 KiB
Images can slow down the page's load time. Skokie.org should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.skokie.org/ImageRepository/Document?documentID=1416
559500
287490
https://www.skokie.org/ImageRepository/Document?documentID=2263
382815
189423
https://www.skokie.org/ImageRepository/Document?documentID=6232
30821
18877
https://www.skokie.org/ImageRepository/Document?documentID=6259
25086
15365
https://www.skokie.org/ImageRepository/Document?documentID=1330
20717
12681
https://www.skokie.org/ImageRepository/Document?documentID=2117
20511
12562
https://www.skokie.org/ImageRepository/Document?documentID=5389
18663
11431
https://www.skokie.org/ImageRepository/Document?documentID=6223
17312
10603
https://www.skokie.org/ImageRepository/Document?documentID=5433
13456
8241
https://www.skokie.org/ImageRepository/Document?documentID=6251
12326
7549
https://www.skokie.org/ImageRepository/Document?documentID=6245
11180
6847
Defer offscreen images — Potential savings of 51 KiB
Time to Interactive can be slowed down by resources on the page. Skokie.org should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.skokie.org/ImageRepository/Document?documentID=2117
20511
20511
https://www.skokie.org/ImageRepository/Document?documentID=5389
18663
18663
https://www.skokie.org/ImageRepository/Document?documentID=5433
13456
13456
Minify CSS — Potential savings of 4 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Skokie.org should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.skokie.org/1072899308.css
53251
3903
Minify JavaScript — Potential savings of 17 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Skokie.org should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.skokie.org/-2031684067.js
76540
12283
https://www.skokie.org/Areas/NewsFlash/Assets/Scripts/Carousel.jquery.js
7056
3254
https://www.skokie.org/Areas/NewsFlash/Assets/Scripts/Easing.1.3.jquery.js
3604
2101
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 10 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://theme.zdassets.com/theme_assets/958586/bae8aa24db8d43595871692a9d259186f2db3fb4.png
13664
10338
Enable text compression — Potential savings of 41 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://analytics.civicplus.com//piwik.js
56050
36639
https://www.skokie.org/Toggle
7056
5021
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Skokie.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://skokie.org/
190
https://www.skokie.org/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Skokie.org 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 9 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://www.skokie.org/237693563.js
9069
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.skokie.org/ImageRepository/Document?documentID=1418
0

Diagnostics

Avoids enormous network payloads — Total size was 1,921 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.skokie.org/ImageRepository/Document?documentID=1416
560307
https://www.skokie.org/ImageRepository/Document?documentID=2263
383622
https://www.skokie.org/237693563.js
160495
https://translate.googleapis.com/element/TE_20210224_00/e/js/element/element_main.js
91946
https://www.skokie.org/-2031684067.js
76540
https://analytics.civicplus.com//piwik.js
56412
https://www.skokie.org/1072899308.css
53251
https://www.skokie.org/901781768.css
52055
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
41832
https://www.skokie.org/
41759
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Skokie.org 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.
Keep request counts low and transfer sizes small — 74 requests • 1,921 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
74
1966695
Image
42
1213799
Script
15
481427
Stylesheet
7
120846
Font
6
82056
Document
1
41759
Other
3
26808
Media
0
0
Third-party
22
294565
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
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.071192182775227
0.021104914917856
0.013759005305563
0.0096789808697555
0.0055968835141275
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 — 19 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://translate.googleapis.com/element/TE_20210224_00/e/js/element/element_main.js
5223
586
https://www.skokie.org/Assets/Scripts/RWD/MediaFramework.js
4785
438
https://www.skokie.org/Areas/NewsFlash/Assets/Scripts/Easing.1.3.jquery.js
3030
243
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
3734
204
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
3532
202
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
4210
184
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
4394
165
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
3938
152
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
4559
132
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
4090
120
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
3273
105
https://translate.googleapis.com/element/TE_20210224_00/e/js/element/element_main.js
4691
94
https://www.skokie.org/237693563.js
2680
85
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
3428
68
https://www.skokie.org/
302
62
https://www.skokie.org/
441
59
Unattributable
364
56
https://www.skokie.org/
251
51
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
3378
50
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name

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.

Other

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://skokie.org/
http/1.1
0
112.2280000709
831
0
302
text/html
https://www.skokie.org/
http/1.1
113.02400007844
1096.7820002697
41759
154711
200
text/html
Document
https://www.skokie.org/901781768.css
http/1.1
1117.9410000332
1384.1699999757
52055
220741
200
text/css
Stylesheet
https://www.skokie.org/1072899308.css
http/1.1
1118.2619999163
1560.6220001355
53251
285896
200
text/css
Stylesheet
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
http/1.1
1118.6299999245
1560.0710003637
41832
91674
200
application/javascript
Script
https://www.skokie.org/-2031684067.js
http/1.1
1119.1030000336
1589.1340002418
76540
220329
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Open+Sans+Condensed:700
h2
1119.6010001004
1138.0179999396
1305
2343
200
text/css
Stylesheet
https://www.skokie.org/Common/Images/AlertCenter/alertBarBlink.svg
http/1.1
1705.9340002015
1994.8920002207
4494
3599
200
image/svg+xml
Image
https://www.skokie.org/ImageRepository/Document?documentID=1404
http/1.1
1706.3670000061
2057.2640001774
1010
207
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1410
http/1.1
1706.7460003309
2056.2550001778
1107
304
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1406
http/1.1
1707.2129999287
1860.4760002345
1166
363
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1442
http/1.1
1707.5080000795
2052.4720000103
3767
2963
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1418
http/1.1
1707.6580002904
1933.2389999181
9035
8231
200
image/png
Image
https://www.skokie.org/Common/Controls/jquery-ui/js/jquery.ui.autocomplete.min.js
http/1.1
1707.8909999691
2098.7019999884
4363
8662
200
application/javascript
Script
https://www.skokie.org/Areas/Layout/Assets/Scripts/Search.js
http/1.1
1708.2640002482
1933.3860003389
1430
617
200
application/javascript
Script
https://www.skokie.org/ImageRepository/Document?documentID=1413
http/1.1
1708.4409999661
2064.0560002066
1679
876
200
image/png
Image
https://code.jquery.com/ui/1.10.3/themes/smoothness/jquery-ui.css
h2
1588.6270003393
1614.5230000839
6471
32046
200
text/css
Stylesheet
https://www.skokie.org/Areas/NewsFlash/Assets/Scripts/Carousel.jquery.js
http/1.1
1708.8990001939
1860.7149999589
7056
16333
200
application/javascript
Script
https://www.skokie.org/Areas/NewsFlash/Assets/Scripts/Easing.1.3.jquery.js
http/1.1
1709.0549999848
2098.937000148
3604
8823
200
application/javascript
Script
https://www.skokie.org/ImageRepository/Document?documentID=6232
http/1.1
1709.1930001043
2198.1410002336
31627
30821
200
image/jpeg
Image
https://www.skokie.org/Assets/Styles/Print.css
http/1.1
1710.194000043
2067.9810000584
2189
2555
200
text/css
Stylesheet
https://www.skokie.org/Areas/Calendar/Assets/Scripts/Calendar.js
http/1.1
1628.3280001953
1995.3540000133
1706
1392
200
application/javascript
Script
https://az416426.vo.msecnd.net/scripts/a/ai.0.js
h2
1709.3470003456
1727.9469999485
23214
96705
200
application/x-javascript
Script
https://www.skokie.org/ImageRepository/Document?documentID=1443
http/1.1
1710.0289999507
1930.5230001919
11113
10308
200
image/png
Image
https://www.skokie.org/237693563.js
http/1.1
1636.9090001099
1928.6960000172
160495
461956
200
text/javascript
Script
https://fonts.gstatic.com/s/opensanscondensed/v15/z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMR7eS2Ao.woff2
h2
1713.5360003449
1724.8610001989
10792
10228
200
font/woff2
Font
https://www.skokie.org/ImageRepository/Document?documentID=1385
http/1.1
1765.7050001435
2062.6290002838
962
159
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1414
http/1.1
1769.4860002957
2050.5480002612
930
127
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1415
http/1.1
1769.820000045
2098.8380000927
10383
9579
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1390
http/1.1
1770.5310001038
2064.3879999407
1615
812
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1392
http/1.1
1771.1820001714
1995.2509999275
1338
535
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1393
http/1.1
1771.7440002598
1861.6969999857
1329
526
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=3617
http/1.1
1775.3640003502
2069.5800003596
1494
691
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1389
http/1.1
1775.5150003359
2069.4760000333
1580
777
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1391
http/1.1
1775.6250002421
1995.1280001551
1463
660
200
image/png
Image
data
1835.3850003332
1835.4830001481
0
42
200
image/gif
Image
https://www.skokie.org/ImageRepository/Document?documentID=1421
http/1.1
2013.2369999774
2235.7450001873
1187
384
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1420
http/1.1
2047.946000006
2234.3510002829
927
124
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1440
http/1.1
2049.7230002657
2266.4890000597
1376
573
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1439
http/1.1
2050.1370001584
2266.1850000732
1696
893
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1435
http/1.1
2050.7800001651
2232.1550003253
1480
677
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1437
http/1.1
2051.0599999689
2266.3770001382
1474
671
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1433
http/1.1
2052.1710002795
2270.9580003284
1309
506
200
image/png
Image
https://www.skokie.org/Toggle
http/1.1
2203.6950001493
2273.0740001425
7882
7056
200
application/json
XHR
https://www.skokie.org/Assets/Scripts/RWD/MediaFramework.js
http/1.1
2312.9839999601
2838.05999998
7791
24592
200
application/javascript
Image
https://fonts.googleapis.com/css?family=Lato:700|Libre+Franklin:700,regular|Montserrat:200,200italic,500,500italic,600,600italic,700,700italic,italic,regular|
h2
2316.0100001842
2337.5770002604
1825
19388
200
text/css
Stylesheet
https://www.skokie.org/Pages/MenuMain/HiddenMainSubMenus?pageID=1&moduleID=&themeID=21&menuContainerID=mainNav&_=1616650900064
http/1.1
2444.9980002828
2595.5460001715
18095
105404
200
text/html
XHR
https://code.jquery.com/ui/1.10.3/themes/smoothness/images/ui-bg_flat_75_ffffff_40x100.png
h2
2445.3340000473
2466.4880000055
578
208
200
image/png
Image
https://translate.google.com/translate_a/element.js?cb=googleTranslateElementInit&_=1616650900384
h2
2744.1710000858
2753.8290000521
2453
4004
200
text/javascript
Script
https://www.skokie.org/ImageRepository/Document?documentID=6259
http/1.1
3335.4780003428
3595.8489999175
25892
25086
200
image/jpeg
Image
https://www.skokie.org/ImageRepository/Document?documentID=1330
http/1.1
3335.7029999606
3596.5240001678
21523
20717
200
image/jpeg
Image
https://www.skokie.org/ImageRepository/Document?documentID=6251
http/1.1
3335.8990000561
3600.0220002607
13132
12326
200
image/jpeg
Image
https://www.skokie.org/ImageRepository/Document?documentID=2117
http/1.1
3336.1940002069
3596.6380001046
21317
20511
200
image/jpeg
Image
https://www.skokie.org/ImageRepository/Document?documentID=6245
http/1.1
3336.5839999169
3596.2760001421
11986
11180
200
image/jpeg
Image
https://www.skokie.org/ImageRepository/Document?documentID=5433
http/1.1
3336.8910001591
3596.8120000325
14262
13456
200
image/jpeg
Image
https://www.skokie.org/ImageRepository/Document?documentID=6223
http/1.1
3337.1850000694
3595.9960003383
18118
17312
200
image/jpeg
Image
https://www.skokie.org/ImageRepository/Document?documentID=5389
http/1.1
3337.4340003356
3596.4069999754
19469
18663
200
image/jpeg
Image
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_ZpC3gnD_vx3rCs.woff2
h2
3507.61900004
3511.8650002405
14204
13640
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_dJE3gnD_vx3rCs.woff2
h2
3509.721999988
3514.9970003404
14174
13612
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v15/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
h2
3517.727999948
3523.5950001515
14272
13708
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v15/JTUQjIg1_i6t8kCHKm459WxRyS7m0dR9pA.woff2
h2
3523.4320000745
3527.5220000185
14587
14024
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_bZF3gnD_vx3rCs.woff2
h2
3541.7420002632
3595.205000136
14027
13464
200
font/woff2
Font
https://www.skokie.org/Assets/Scripts/RWD/MediaFramework.js
http/1.1
3922.1570002846
4137.8720002249
6082
24592
200
application/javascript
Script
https://translate.googleapis.com/translate_static/css/translateelement.css
h2
3924.1490000859
3928.5440002568
3750
18724
200
text/css
Stylesheet
https://translate.googleapis.com/translate_static/js/element/main.js
h2
3925.7360002957
3930.2770001814
2300
4103
200
text/javascript
Script
https://translate.googleapis.com/element/TE_20210224_00/e/js/element/element_main.js
h2
5044.4680000655
5096.7230000533
91946
256226
200
text/javascript
Script
https://www.gstatic.com/images/branding/product/1x/translate_24dp.png
h2
7010.9709999524
7015.0480000302
1388
825
200
image/png
Image
https://www.gstatic.com/images/branding/googlelogo/1x/googlelogo_color_42x16dp.png
h2
7011.5720001049
7015.5330002308
1473
910
200
image/png
Image
https://www.gstatic.com/images/branding/product/2x/translate_24dp.png
h2
7028.6560002714
7032.492000144
2411
1847
200
image/png
Image
https://analytics.civicplus.com//piwik.js
http/1.1
8236.6260001436
8697.4329999648
56412
56050
200
application/javascript
Script
https://www.skokie.org/ImageRepository/Document?documentID=2263
http/1.1
8237.275000196
8597.2740002908
383622
382815
200
image/jpeg
Image
https://www.skokie.org/ImageRepository/Document?documentID=1416
http/1.1
8237.6170000061
8620.7330003381
560307
559500
200
image/jpeg
Image
https://translate.googleapis.com/translate_a/l?client=te&alpha=true&hl=en&cb=callback
h2
8310.4159999639
8321.2749999948
1994
3427
200
application/javascript
Script
https://theme.zdassets.com/theme_assets/958586/bae8aa24db8d43595871692a9d259186f2db3fb4.png
h2
8339.5569999702
8399.207000155
14694
13664
200
image/png
Image
https://analytics.civicplus.com//piwik.php?action_name=Skokie%2C%20IL%20%7C%20Official%20Website&idsite=4074&rec=1&r=339104&h=22&m=41&s=46&url=https%3A%2F%2Fwww.skokie.org%2F&_id=8cd0149758602329&_idts=1616650906&_idvc=1&_idn=0&_refts=0&_viewts=1616650906&send_image=1&cookie=1&res=800x600&gt_ms=985
http/1.1
8736.1030001193
9154.2930002324
295
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)
1184.71
10.791
1199.635
9.332
1468.73
13.157
1645.362
16.046
1669.475
39.296
1719.482
72.134
1791.633
19.397
1816.77
15.274
1836.679
7.022
1844.058
67.832
1912.672
7.369
1920.811
15.805
1936.661
22.518
1963.446
15.016
1980.121
12.416
2027.266
8.611
2079.462
5.128
2090.939
26.424
2117.398
5.368
2123.399
20.249
2149.325
28.753
2178.14
20.679
2210.616
18.461
2229.209
170.939
2400.689
6.358
2411.017
485.491
2896.638
13.723
2924.841
209.723
3134.59
50.81
3185.415
99.058
3284.493
136.031
3421.15
66.375
3490.137
36.464
3527.189
404.876
3932.727
62.309
3995.777
7.086
4022.081
56.366
4083.332
407.209
4491.086
21.488
4517.198
303.612
4821.283
58.598
4880.901
240.288
5127.441
875.057
6002.589
17.996
6020.819
368.3
6396.377
330.236
6731.538
263.139
6999.589
94.405
7095.092
87.072
7182.311
10.473
7192.821
6.182
7213.047
1171.299
8384.389
5.556
8409.558
9.165
8418.798
14.937
8448.622
32.261
8537.656
8.964
8549.309
29.009
8588.43
5.259
8610.112
9.763
8634.196
8.741
8651.595
6.026
8659.966
18.203
8693.929
6.895
8713.795
7.296
8745.154
35.741
8792.054
26.96
8823.252
5.33
8915.522
5.364
9248.463
32.68
9366.282
12.989
9398.499
5.465
9449.658
28.757
9534.693
5.463
9547.215
32.708
9585.127
5.808
9619.954
5.82
9665.019
15.606
9684.037
5.099
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Metrics

First Contentful Paint — 1.0 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 1.4 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.131
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 4.1 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 1.0 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 140 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Skokie.org 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.skokie.org/901781768.css
52055
230
https://www.skokie.org/1072899308.css
53251
310
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
41832
310
https://www.skokie.org/-2031684067.js
76540
390
Remove unused CSS — Potential savings of 95 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Skokie.org 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://www.skokie.org/1072899308.css
53251
49473
https://www.skokie.org/901781768.css
52055
47413
Remove unused JavaScript — Potential savings of 287 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://www.skokie.org/237693563.js
160495
137671
https://translate.googleapis.com/element/TE_20210224_00/e/js/element/element_main.js
91946
66430
https://www.skokie.org/-2031684067.js
76540
51480
https://analytics.civicplus.com//piwik.js
56412
38156

Diagnostics

Serve static assets with an efficient cache policy — 6 resources found
Skokie.org 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://analytics.civicplus.com//piwik.php?action_name=Skokie%2C%20IL%20%7C%20Official%20Website&idsite=4074&rec=1&r=339104&h=22&m=41&s=46&url=https%3A%2F%2Fwww.skokie.org%2F&_id=8cd0149758602329&_idts=1616650906&_idvc=1&_idn=0&_refts=0&_viewts=1616650906&send_image=1&cookie=1&res=800x600&gt_ms=985
0
295
https://az416426.vo.msecnd.net/scripts/a/ai.0.js
1800000
23214
https://translate.googleapis.com/translate_static/css/translateelement.css
3600000
3750
https://translate.googleapis.com/translate_static/js/element/main.js
3600000
2300
https://analytics.civicplus.com//piwik.js
86400000
56412
https://theme.zdassets.com/theme_assets/958586/bae8aa24db8d43595871692a9d259186f2db3fb4.png
86400000
14694
Avoid an excessive DOM size — 1,277 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
1277
Maximum DOM Depth
29
Maximum Child Elements
109
Reduce JavaScript execution time — 2.6 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.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
3266.2
1377.973
2.813
https://translate.googleapis.com/element/TE_20210224_00/e/js/element/element_main.js
1295.855
568.935
12.444
https://www.skokie.org/
1177.36
15.957
8.035
https://www.skokie.org/Assets/Scripts/RWD/MediaFramework.js
874.963
406.297
1.695
Unattributable
350.959
2.908
0.219
https://www.skokie.org/237693563.js
163.772
113.903
46.346
https://www.skokie.org/-2031684067.js
72.898
61.682
5.236
https://az416426.vo.msecnd.net/scripts/a/ai.0.js
50.202
15.835
2.473

Metrics

Speed Index — 2.6 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 4.9 s
The time taken for the page to become fully interactive.
Total Blocking Time — 1,810 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).

Other

Max Potential First Input Delay — 590 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 220 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive skokie.org as laggy when the latency is higher than 0.05 seconds.

Opportunities

Reduce initial server response time — Root document took 980 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.skokie.org/
984.754

Diagnostics

Minimize main-thread work — 7.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)
Style & Layout
3454.644
Script Evaluation
2595.161
Rendering
598.497
Other
487.892
Parse HTML & CSS
91.039
Script Parsing & Compilation
85.665
Garbage Collection
15.013
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/opensanscondensed/v15/z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMR7eS2Ao.woff2
11.324999853969
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_ZpC3gnD_vx3rCs.woff2
4.24600020051
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_dJE3gnD_vx3rCs.woff2
5.2750003524125
https://fonts.gstatic.com/s/montserrat/v15/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
5.8670002035797
https://fonts.gstatic.com/s/montserrat/v15/JTUQjIg1_i6t8kCHKm459WxRyS7m0dR9pA.woff2
4.0899999439716
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_bZF3gnD_vx3rCs.woff2
53.462999872863
Reduce the impact of third-party code — Third-party code blocked the main thread for 420 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)
99990
420.085
85186
0
23214
0
14694
0
7049
0
5272
0
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
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 Failing Elements
https://www.skokie.org/ImageRepository/Document?documentID=6232
https://www.skokie.org/ImageRepository/Document?documentID=6232
https://www.skokie.org/ImageRepository/Document?documentID=6259
https://www.skokie.org/ImageRepository/Document?documentID=1330
https://www.skokie.org/ImageRepository/Document?documentID=2117
https://www.skokie.org/ImageRepository/Document?documentID=5389
https://www.skokie.org/ImageRepository/Document?documentID=6223
https://www.skokie.org/ImageRepository/Document?documentID=5433
https://www.skokie.org/ImageRepository/Document?documentID=6251
https://www.skokie.org/ImageRepository/Document?documentID=6245
https://www.skokie.org/ImageRepository/Document?documentID=1443
https://www.skokie.org/ImageRepository/Document?documentID=1418
https://www.skokie.org/ImageRepository/Document?documentID=1413
https://www.skokie.org/ImageRepository/Document?documentID=1406
https://www.skokie.org/ImageRepository/Document?documentID=1410
https://www.skokie.org/ImageRepository/Document?documentID=1404
92

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of skokie.org. 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.

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 `[alt]` 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 `[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.
`<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"]`
Skokie.org may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
28

ARIA

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.
73

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.

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

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.6.4
jQuery UI
1.8.24
Modernizr
2.5.3
yepnope
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.
URL Map URL
https://az416426.vo.msecnd.net/scripts/a/ai.0.js
https://az416426.vo.msecnd.net/scripts/a/ai.0.js.map
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://skokie.org/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 8 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
3
High

Audits

Registers an `unload` listener
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.
Source
Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for skokie.org. 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 skokie.org 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.
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.

Content Best Practices

Document does not have 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.

Crawling and Indexing

robots.txt is not valid — 1 error found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
32
Sitemap: /sitemap.xml
Invalid sitemap URL

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.
36

Progressive Web App

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 skokie.org 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) 58
Performance 18
Accessibility 82
Best Practices 67
SEO 83
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.skokie.org/
Updated: 25th March, 2021

2.47 seconds
First Contentful Paint (FCP)
19%
68%
13%

0.03 seconds
First Input Delay (FID)
94%
4%
2%

Simulate loading on mobile
18

Performance

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

Opportunities

Properly size images
Images can slow down the page's load time. Skokie.org should consider serving more appropriate-sized images.
Defer offscreen images — Potential savings of 10 KiB
Time to Interactive can be slowed down by resources on the page. Skokie.org should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.skokie.org/ImageRepository/Document?documentID=1443
10308
10308
Minify CSS — Potential savings of 4 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Skokie.org should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.skokie.org/1072899308.css
53251
3903
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression — Potential savings of 5 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.skokie.org/Toggle
7056
5021
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Skokie.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://skokie.org/
630
https://www.skokie.org/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Skokie.org 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.

Diagnostics

Avoids enormous network payloads — Total size was 1,639 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.skokie.org/ImageRepository/Document?documentID=1416
560305
https://www.skokie.org/ImageRepository/Document?documentID=1034
188581
https://www.skokie.org/237693563.js
160495
https://translate.googleapis.com/element/TE_20210224_00/e/js/element/element_main.js
91946
https://www.skokie.org/-2031684067.js
76540
https://www.skokie.org/1072899308.css
53251
https://www.skokie.org/901781768.css
52055
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
41830
https://www.skokie.org/
41653
https://www.skokie.org/ImageRepository/Document?documentID=6232
31625
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Skokie.org 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.
Keep request counts low and transfer sizes small — 71 requests • 1,639 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
71
1678466
Image
37
931379
Script
16
457635
Stylesheet
7
120844
Font
6
82058
Other
4
44897
Document
1
41653
Media
0
0
Third-party
22
260841
Minimize third-party usage — Third-party code blocked the main thread for 70 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)
100169
65.308
85188
0
23212
0
14694
0
7049
0
5272
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
img
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.32521362071164
0.1055980056057
0.041559058936257
0.032124674867394
0.023949610427713
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 — 18 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://www.skokie.org/237693563.js
6870
537
https://www.skokie.org/Assets/Scripts/RWD/MediaFramework.js
13680
363
https://www.skokie.org/Common/Controls/jquery-ui/js/jquery.ui.autocomplete.min.js
8130
285
https://translate.googleapis.com/element/TE_20210224_00/e/js/element/element_main.js
11175
159
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
4530
157
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
7407
137
https://www.skokie.org/Assets/Scripts/RWD/MediaFramework.js
15090
113
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
9090
102
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
8603
102
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
8415
71
https://www.skokie.org/
1789
70
https://www.skokie.org/
701
69
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
8486
64
https://www.skokie.org/
1597
63
https://analytics.civicplus.com//piwik.js
8728
61
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
3900
57
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
8550
53
https://www.skokie.org/
1738
51
Avoid non-composited animations — 7 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name

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.

Other

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://skokie.org/
http/1.1
0
112.59000003338
831
0
302
text/html
https://www.skokie.org/
http/1.1
113.27699990943
877.92199989781
41653
154529
200
text/html
Document
https://www.skokie.org/901781768.css
http/1.1
893.68199999444
1129.716000054
52055
220741
200
text/css
Stylesheet
https://www.skokie.org/1072899308.css
http/1.1
893.86199996807
1131.1540000606
53251
285896
200
text/css
Stylesheet
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
http/1.1
894.09200008959
1155.6859998964
41830
91674
200
application/javascript
Script
https://www.skokie.org/-2031684067.js
http/1.1
894.20800004154
1116.6689998936
76540
220329
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Open+Sans+Condensed:700
h2
894.45300004445
909.63399992324
1305
2343
200
text/css
Stylesheet
https://www.skokie.org/Common/Images/AlertCenter/alertBarBlink.svg
http/1.1
1239.077999955
1371.9750000164
4492
3599
200
image/svg+xml
Image
https://www.skokie.org/ImageRepository/Document?documentID=1404
http/1.1
1239.428000059
1379.2560000438
1008
207
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1410
http/1.1
1239.9100000039
1454.4720000122
1105
304
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1406
http/1.1
1240.0919999927
1376.3089999557
1164
363
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1442
http/1.1
1240.2260000817
1379.4050000142
3765
2963
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1418
http/1.1
1240.3569999151
1377.5480000768
9033
8231
200
image/png
Image
https://www.skokie.org/Common/Controls/jquery-ui/js/jquery.ui.autocomplete.min.js
http/1.1
1240.5610000715
1471.2090000976
4361
8662
200
application/javascript
Script
https://www.skokie.org/Areas/Layout/Assets/Scripts/Search.js
http/1.1
1240.7160000876
1465.441999957
1428
617
200
application/javascript
Script
https://www.skokie.org/ImageRepository/Document?documentID=1413
http/1.1
1240.8660000656
1464.2870000098
1677
876
200
image/png
Image
https://code.jquery.com/ui/1.10.3/themes/smoothness/jquery-ui.css
h2
1141.0920000635
1162.1600000653
6471
32046
200
text/css
Stylesheet
https://www.skokie.org/Areas/NewsFlash/Assets/Scripts/Carousel.jquery.js
http/1.1
1241.1740000825
1375.2150000073
7054
16333
200
application/javascript
Script
https://www.skokie.org/Areas/NewsFlash/Assets/Scripts/Easing.1.3.jquery.js
http/1.1
1241.9390000869
1375.3460000735
3602
8823
200
application/javascript
Script
https://www.skokie.org/ImageRepository/Document?documentID=6232
http/1.1
1242.1319999266
1464.0510000754
31625
30821
200
image/jpeg
Image
https://www.skokie.org/Assets/Styles/Print.css
http/1.1
1242.7300000563
1453.0319999903
2187
2555
200
text/css
Stylesheet
https://www.skokie.org/Areas/Calendar/Assets/Scripts/Calendar.js
http/1.1
1163.0379999988
1379.9060001038
1704
1392
200
application/javascript
Script
https://az416426.vo.msecnd.net/scripts/a/ai.0.js
h2
1242.2960000113
1259.1679999605
23212
96705
200
application/x-javascript
Script
https://www.skokie.org/ImageRepository/Document?documentID=1443
http/1.1
1242.4480000045
1458.3829999901
11111
10308
200
image/png
Image
https://www.skokie.org/237693563.js
http/1.1
1238.6350000743
1442.0459999237
160495
461956
200
text/javascript
Script
https://fonts.gstatic.com/s/opensanscondensed/v15/z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMR7eS2Ao.woff2
h2
1243.860000046
1247.183999978
10792
10228
200
font/woff2
Font
https://www.skokie.org/ImageRepository/Document?documentID=1385
http/1.1
1266.0389998928
1464.1879999544
960
159
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1414
http/1.1
1268.6260000337
1582.9320000485
928
127
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1415
http/1.1
1268.7959999312
1461.8810000829
10381
9579
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1390
http/1.1
1269.2929999903
1583.2090000622
1613
812
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1392
http/1.1
1269.7709999047
1377.6879999787
1336
535
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1393
http/1.1
1270.1650001109
1459.8940000869
1327
526
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=3617
http/1.1
1273.1709999498
1458.4449999966
1492
691
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1389
http/1.1
1273.346999893
1459.380999906
1578
777
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1391
http/1.1
1273.4779999591
1470.4269999638
1461
660
200
image/png
Image
data
1275.7000001147
1275.7449999917
0
42
200
image/gif
Image
https://www.skokie.org/ImageRepository/Document?documentID=1421
http/1.1
1400.3979999106
1458.2599999849
1185
384
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1420
http/1.1
1400.6920000538
1617.1999999788
925
124
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1440
http/1.1
1402.3559999187
1616.9090000913
1374
573
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1439
http/1.1
1402.6510000695
1617.1329999343
1694
893
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1435
http/1.1
1403.2439999282
1468.9519999083
1478
677
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1437
http/1.1
1403.510000091
1454.8200001009
1472
671
200
image/png
Image
https://www.skokie.org/ImageRepository/Document?documentID=1433
http/1.1
1404.155000113
1460.1779999211
1307
506
200
image/png
Image
https://www.skokie.org/Toggle
http/1.1
1480.5260000285
1696.9590000808
7880
7056
200
application/json
XHR
https://www.skokie.org/Assets/Scripts/RWD/quo.debug.js
http/1.1
1728.471999988
2006.2810000964
12672
39906
200
application/javascript
Image
https://www.skokie.org/Assets/Scripts/RWD/MediaFramework.js
http/1.1
1728.6739998963
2003.9180000313
6080
24592
200
application/javascript
Image
https://fonts.googleapis.com/css?family=Lato:700|Libre+Franklin:700,regular|Montserrat:200,200italic,500,500italic,600,600italic,700,700italic,italic,regular|
h2
1731.1909999698
1752.4709999561
1825
19388
200
text/css
Stylesheet
https://www.skokie.org/Pages/MenuMain/HiddenMainSubMenus?pageID=1&moduleID=&themeID=21&menuContainerID=mainNav&_=1616650944596
http/1.1
1817.8459999617
2046.0840000305
18093
105404
200
text/html
XHR
https://code.jquery.com/ui/1.10.3/themes/smoothness/images/ui-bg_flat_75_ffffff_40x100.png
h2
1825.0639999751
1874.4320000987
578
208
200
image/png
Image
https://translate.google.com/translate_a/element.js?cb=googleTranslateElementInit&_=1616650944665
h2
1886.2679998856
1892.2359999269
2453
4004
200
text/javascript
Script
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_ZpC3gnD_vx3rCs.woff2
h2
1924.6410001069
1928.1880001072
14204
13640
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v15/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
h2
1927.2839999758
1931.4830000512
14272
13708
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v15/JTUQjIg1_i6t8kCHKm459WxRyS7m0dR9pA.woff2
h2
1927.8830001131
1930.7929999195
14588
14024
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_dJE3gnD_vx3rCs.woff2
h2
1931.3749999274
1933.997000102
14175
13612
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_bZF3gnD_vx3rCs.woff2
h2
1940.450000111
1944.361000089
14027
13464
200
font/woff2
Font
https://translate.googleapis.com/translate_static/css/translateelement.css
h2
2035.7099999674
2040.3050000314
3750
18724
200
text/css
Stylesheet
https://translate.googleapis.com/translate_static/js/element/main.js
h2
2036.5599999204
2039.8130000103
2299
4103
200
text/javascript
Script
https://www.skokie.org/Assets/Scripts/RWD/quo.debug.js
http/1.1
2059.3610000797
2271.7659999616
9948
39906
200
application/javascript
Script
https://translate.googleapis.com/element/TE_20210224_00/e/js/element/element_main.js
h2
2093.9340000041
2103.5790001042
91946
256226
200
text/javascript
Script
https://www.skokie.org/ImageRepository/Document?documentID=6259
http/1.1
2145.3340000007
2272.9839999229
25890
25086
200
image/jpeg
Image
https://www.skokie.org/ImageRepository/Document?documentID=1330
http/1.1
2146.0690000094
2360.382999992
21521
20717
200
image/jpeg
Image
https://www.gstatic.com/images/branding/product/1x/translate_24dp.png
h2
2220.0410000514
2223.6969999503
1388
825
200
image/png
Image
https://www.gstatic.com/images/branding/googlelogo/1x/googlelogo_color_42x16dp.png
h2
2220.7710000221
2224.445000058
1473
910
200
image/png
Image
https://www.gstatic.com/images/branding/product/2x/translate_24dp.png
h2
2229.4600000605
2232.4439999647
2411
1847
200
image/png
Image
https://translate.googleapis.com/translate_a/l?client=te&alpha=true&hl=en&cb=callback
h2
2268.8680000138
2279.041999951
2174
3427
200
application/javascript
Script
https://www.skokie.org/Assets/Scripts/RWD/MediaFramework.js
http/1.1
2284.4640000258
2356.1080000363
6080
24592
200
application/javascript
Script
https://theme.zdassets.com/theme_assets/958586/bae8aa24db8d43595871692a9d259186f2db3fb4.png
h2
2300.2390000038
2331.7740000784
14694
13664
200
image/png
Image
https://www.skokie.org/Pages/MenuMain/HiddenMainSubMenus?pageID=1&moduleID=&themeID=21&menuContainerID=mainNav&_=1616650945320
http/1.1
2542.4059999641
2770.8610000554
18093
105404
200
text/html
XHR
https://analytics.civicplus.com//piwik.js
http/1.1
2611.462000059
3000.7829999086
22509
56050
200
application/x-javascript
Script
https://www.skokie.org/ImageRepository/Document?documentID=1034
http/1.1
2611.8469999637
2871.6319999658
188581
187776
200
image/jpeg
Image
https://www.skokie.org/ImageRepository/Document?documentID=1416
http/1.1
2612.1360000689
2924.4419999886
560305
559500
200
image/jpeg
Image
https://analytics.civicplus.com//piwik.php?action_name=Skokie%2C%20IL%20%7C%20Official%20Website&idsite=4074&rec=1&r=705120&h=22&m=42&s=25&url=https%3A%2F%2Fwww.skokie.org%2F&_id=157ccd45478df2de&_idts=1616650946&_idvc=1&_idn=0&_refts=0&_viewts=1616650946&send_image=1&cookie=1&res=360x640&gt_ms=765
http/1.1
3025.4359999672
3416.550999973
295
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)
913.646
8.609
925.007
9.404
1163.224
8.655
1172.666
9.183
1194.365
78.419
1272.8
8.795
1294.418
14.291
1309.039
24.692
1335.647
10.198
1345.885
5.369
1422.99
31.464
1458.361
10.192
1470.38
8.201
1495.58
268.744
1764.361
10.98
1784.197
9.262
1794.178
142.606
1936.867
8.473
1949.37
35.736
1985.141
31.982
2017.231
10.176
2038.88
26.46
2069.672
9.474
2090.727
6.23
2097.393
25.508
2126.046
51.132
2177.21
8.233
2185.542
9.381
2212.32
39.664
2252.058
18.812
2270.976
8.01
2293.865
5.048
2307.179
7.176
2322.415
7.247
2330.207
11.376
2394.999
181.509
2576.617
17.179
2593.85
68.587
2663.445
6.838
2677.536
5.82
2683.408
25.275
2718.231
34.925
2753.284
7.131
2766.228
7.451
2782.794
8.833
2799.542
7.469
2808.681
28.156
2836.927
5.922
2842.917
8.201
2852.531
8.388
2865.834
14.043
2883.795
6.111
2899.463
6.105
2916.327
8.346
2924.758
6.923
2933.088
6.285
2949.456
6.382
3041.872
15.344
3516.226
5.285
3521.552
5.045
3968.958
7.514
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Metrics

First Contentful Paint — 3.8 s
The time taken for the first image or text on the page to be rendered.

Other

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

Opportunities

Minify JavaScript — Potential savings of 20 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Skokie.org should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.skokie.org/-2031684067.js
76540
12283
https://www.skokie.org/Areas/NewsFlash/Assets/Scripts/Carousel.jquery.js
7054
3253
https://www.skokie.org/Assets/Scripts/RWD/quo.debug.js
9948
3020
https://www.skokie.org/Areas/NewsFlash/Assets/Scripts/Easing.1.3.jquery.js
3602
2099
Serve images in next-gen formats — Potential savings of 44 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.skokie.org/ImageRepository/Document?documentID=1034
187776
35030
https://theme.zdassets.com/theme_assets/958586/bae8aa24db8d43595871692a9d259186f2db3fb4.png
13664
10338
Avoid serving legacy JavaScript to modern browsers — Potential savings of 9 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://www.skokie.org/237693563.js
9069

Diagnostics

Serve static assets with an efficient cache policy — 6 resources found
Skokie.org 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://analytics.civicplus.com//piwik.php?action_name=Skokie%2C%20IL%20%7C%20Official%20Website&idsite=4074&rec=1&r=705120&h=22&m=42&s=25&url=https%3A%2F%2Fwww.skokie.org%2F&_id=157ccd45478df2de&_idts=1616650946&_idvc=1&_idn=0&_refts=0&_viewts=1616650946&send_image=1&cookie=1&res=360x640&gt_ms=765
0
295
https://az416426.vo.msecnd.net/scripts/a/ai.0.js
1800000
23212
https://translate.googleapis.com/translate_static/css/translateelement.css
3600000
3750
https://translate.googleapis.com/translate_static/js/element/main.js
3600000
2299
https://analytics.civicplus.com//piwik.js
86400000
22509
https://theme.zdassets.com/theme_assets/958586/bae8aa24db8d43595871692a9d259186f2db3fb4.png
86400000
14694
Avoid an excessive DOM size — 1,226 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
1226
Maximum DOM Depth
29
Maximum Child Elements
109
Reduce JavaScript execution time — 3.2 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.skokie.org/
2711.476
60.3
22.98
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
2084.556
1203.104
8.216
https://www.skokie.org/237693563.js
1062.328
999.004
39.88
https://www.skokie.org/Assets/Scripts/RWD/MediaFramework.js
842.376
354.756
6.736
Unattributable
550.076
4.668
0.924
https://translate.googleapis.com/element/TE_20210224_00/e/js/element/element_main.js
256.504
171.04
35.476
https://www.skokie.org/-2031684067.js
237.976
204.324
18.908
https://az416426.vo.msecnd.net/scripts/a/ai.0.js
71.224
42.82
7.724
https://analytics.civicplus.com//piwik.js
64.004
52.768
7.292

Metrics

Speed Index — 7.1 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 11.6 s
The timing of the largest text or image that is painted.
Time to Interactive — 11.9 s
The time taken for the page to become fully interactive.
Total Blocking Time — 1,470 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).
Cumulative Layout Shift — 0.598
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 8.6 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 540 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 170 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive skokie.org as laggy when the latency is higher than 0.05 seconds.
First Contentful Paint (3G) — 8251.5 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 820 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Skokie.org 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.skokie.org/901781768.css
52055
1380
https://www.skokie.org/1072899308.css
53251
1680
https://www.skokie.org/Scripts/2011.3.1115/jquery-1.6.4.min.js
41830
1530
https://www.skokie.org/-2031684067.js
76540
1980
Remove unused CSS — Potential savings of 95 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Skokie.org 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://www.skokie.org/1072899308.css
53251
49455
https://www.skokie.org/901781768.css
52055
47533
Remove unused JavaScript — Potential savings of 249 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://www.skokie.org/237693563.js
160495
136622
https://translate.googleapis.com/element/TE_20210224_00/e/js/element/element_main.js
91946
66430
https://www.skokie.org/-2031684067.js
76540
51563
Reduce initial server response time — Root document took 770 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.skokie.org/
765.642
Preload Largest Contentful Paint image — Potential savings of 1,200 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.skokie.org/ImageRepository/Document?documentID=1034
1200

Diagnostics

Minimize main-thread work — 8.0 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
3129.824
Style & Layout
2111.372
Other
1394.524
Rendering
898.04000000001
Parse HTML & CSS
308.86
Script Parsing & Compilation
173.784
Garbage Collection
32.456
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/opensanscondensed/v15/z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMR7eS2Ao.woff2
3.3239999320358
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_ZpC3gnD_vx3rCs.woff2
3.5470000002533
https://fonts.gstatic.com/s/montserrat/v15/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
4.1990000754595
https://fonts.gstatic.com/s/montserrat/v15/JTUQjIg1_i6t8kCHKm459WxRyS7m0dR9pA.woff2
2.9099998064339
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_dJE3gnD_vx3rCs.woff2
2.6220001745969
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_bZF3gnD_vx3rCs.woff2
3.9109999779612
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
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 Failing Elements
https://www.skokie.org/ImageRepository/Document?documentID=6232
https://www.skokie.org/ImageRepository/Document?documentID=6232
https://www.skokie.org/ImageRepository/Document?documentID=6259
https://www.skokie.org/ImageRepository/Document?documentID=1330
https://www.skokie.org/ImageRepository/Document?documentID=1443
https://www.skokie.org/ImageRepository/Document?documentID=1418
https://www.skokie.org/ImageRepository/Document?documentID=1413
https://www.skokie.org/ImageRepository/Document?documentID=1406
https://www.skokie.org/ImageRepository/Document?documentID=1410
https://www.skokie.org/ImageRepository/Document?documentID=1404
82

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of skokie.org. 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 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.
`[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.

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.
`<object>` elements have `[alt]` 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 `[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.
`<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"]`
Skokie.org may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[aria-hidden="true"]` elements contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
Failing Elements
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
Failing Elements
ARIA IDs are not unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.
Failing Elements

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
28

Names and labels

Links do not 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.

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.
67

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.

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.
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

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.6.4
jQuery UI
1.8.24
Modernizr
2.5.3
yepnope
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.
URL Map URL
https://az416426.vo.msecnd.net/scripts/a/ai.0.js
https://az416426.vo.msecnd.net/scripts/a/ai.0.js.map
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://skokie.org/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 8 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
3
High

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.skokie.org/ImageRepository/Document?documentID=1442
150 x 182
150 x 182
300 x 364
https://www.skokie.org/ImageRepository/Document?documentID=1418
331 x 100
489 x 147
662 x 200
https://www.skokie.org/ImageRepository/Document?documentID=1413
81 x 81
81 x 81
162 x 162
https://www.skokie.org/ImageRepository/Document?documentID=1404
36 x 36
36 x 36
72 x 72
https://www.skokie.org/ImageRepository/Document?documentID=1406
36 x 36
36 x 36
72 x 72
https://www.skokie.org/ImageRepository/Document?documentID=1410
36 x 36
36 x 36
72 x 72

Audits

Registers an `unload` listener
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.
Source
Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for skokie.org. 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 skokie.org on mobile screens.
Document uses legible font sizes — 99.97% 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
.goog-te-gadget
0.03%
11px
99.97%
≥ 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.
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.

Mobile Friendly

Tap targets are not sized appropriately — 91% 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
45x18
64x18
79x18
89x18
52x18

Content Best Practices

Document does not have 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.

Crawling and Indexing

robots.txt is not valid — 1 error found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
32
Sitemap: /sitemap.xml
Invalid sitemap URL

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.
42

Progressive Web App

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 skokie.org 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: 207.38.72.42
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Icon Enterprises, Inc.
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.73.232.111
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: www.skokie.org
Issued By: Sectigo RSA Domain Validation Secure Server CA
Valid From: 14th April, 2020
Valid To: 14th April, 2021
Subject: CN = www.skokie.org
Hash: 9e7fcf78
Issuer: CN = Sectigo RSA Domain Validation Secure Server CA
O = Sectigo Limited
S = GB
Version: 2
Serial Number: 0xEE997F865BBE49D2FA1577967A7F81F3
Serial Number (Hex): EE997F865BBE49D2FA1577967A7F81F3
Valid From: 14th April, 2024
Valid To: 14th April, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:8D:8C:5E:C4:54:AD:8A:E1:77:E9:9B:F9:9B:05:E1:B8:01:8D:61:E1
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.2.7
CPS: https://sectigo.com/CPS
Policy: 2.23.140.1.2.1

Authority Information Access: CA Issuers - URI:http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
OCSP - URI:http://ocsp.sectigo.com

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Apr 14 09:10:04.732 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:05:EF:B7:82:B6:80:C9:28:A1:2C:54:AE:
62:AD:5C:FA:53:8F:9B:6A:6E:B3:25:7B:E4:28:B5:1F:
BD:94:FF:57:02:20:5A:D6:D1:C4:83:FB:72:68:3E:08:
D8:BF:FB:3D:3D:EC:B8:98:D8:16:01:DE:3B:12:2A:AA:
95:A6:7C:03:94:D3
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
Timestamp : Apr 14 09:10:04.772 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:AB:25:9C:37:E8:5A:DA:C3:45:02:38:
7A:5F:BE:B7:85:D0:BD:E8:51:32:B7:F5:B7:F7:AA:BD:
64:B8:52:9A:DC:02:21:00:AA:B8:E2:6D:65:46:A0:0D:
F0:40:EA:A0:22:8E:DB:F8:EA:8B:03:2D:8C:2A:15:11:
A2:BC:06:77:13:0A:E3:BB
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:skokie.org
DNS:www.skokie.org
Technical

DNS Lookup

A Records

Host IP Address Class TTL
skokie.org. 207.38.72.42 IN 1799

NS Records

Host Nameserver Class TTL
skokie.org. ns49.domaincontrol.com. IN 3599
skokie.org. ns50.domaincontrol.com. IN 3599

MX Records

Priority Host Server Class TTL
0 skokie.org. skokie-org.mail.protection.outlook.com. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
skokie.org. ns49.domaincontrol.com. dns.jomax.net. 3599

TXT Records

Host Value Class TTL
skokie.org. MS=ms28000793 IN 3599
skokie.org. v=spf1 IN 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Cache-Control: private, s-maxage=600,no-transform
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/8.5
Date: 25th March, 2021
Content-Length: 154711
ETag: " "
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: *
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Security-Policy: frame-ancestors 'self' https://*.granicus.com http://*.granicus.com https://platform.civicplus.com https://account.civicplus.com https://analytics.civicplus.com; img-src * data:; worker-src * data

Whois Lookup

Created: 12th January, 1997
Changed: 6th April, 2020
Expires: 30th November, 2022
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: ns49.domaincontrol.com
ns50.domaincontrol.com
Owner Organization: Village of Skokie
Owner State: Illinois
Owner Country: US
Owner Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=SKOKIE.ORG
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=SKOKIE.ORG
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=SKOKIE.ORG
Full Whois: Domain Name: SKOKIE.ORG
Registry Domain ID: D656874-LROR
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2020-06-04T08:59:42Z
Creation Date: 1997-12-01T05:00:00Z
Registrar Registration Expiration Date: 2022-11-30T05:00:00Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited
Registrant Organization: Village of Skokie
Registrant State/Province: Illinois
Registrant Country: US
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=SKOKIE.ORG
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=SKOKIE.ORG
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=SKOKIE.ORG
Name Server: NS49.DOMAINCONTROL.COM
Name Server: NS50.DOMAINCONTROL.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-03-25T05:41:33Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

Nameservers

Name IP Address
ns49.domaincontrol.com 97.74.104.25
ns50.domaincontrol.com 173.201.72.25
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$3,114 USD 2/5
$905 USD
$10 USD
0/5
$1,874 USD 1/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5

Sites hosted on the same IP address