loe.org

loe.org is SSL secured

Free website and domain report on loe.org

Last Updated: 16th June, 2022 Update Now
Overview

Snoop Summary for loe.org

This is a free and comprehensive report about loe.org. Loe.org is hosted in Matawan, New Jersey in United States on a server with an IP address of 45.63.17.91, where the local currency is USD and English is the local language. Our records indicate that loe.org is owned/operated by Living on Earth. Loe.org has the potential to be earning an estimated $3 USD per day from advertising revenue. If loe.org was to be sold it would possibly be worth $2,550 USD (based on the daily revenue potential of the website over a 24 month period). Loe.org receives an estimated 1,221 unique visitors every day - a large amount of traffic! This report was last updated 16th June, 2022.

About loe.org

Site Preview: loe.org loe.org
Title: Living On Earth
Description: National Public Radio (NPR) news and information program. Features interviews and commentary on a broad range of topics.
Keywords and Tags: advocacy, ngo, non-profit
Related Terms: npr
Fav Icon:
Age: Over 27 years old
Domain Created: 18th July, 1996
Domain Updated: 18th July, 2020
Domain Expires: 17th July, 2030
Review

Snoop Score

2/5

Valuation

$2,550 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 695,630
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: 1,221
Monthly Visitors: 37,153
Yearly Visitors: 445,538
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $3 USD
Monthly Revenue: $106 USD
Yearly Revenue: $1,270 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: loe.org 7
Domain Name: loe 3
Extension (TLD): org 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.66 seconds
Load Time Comparison: Faster than 53% of sites

PageSpeed Insights

Avg. (All Categories) 59
Performance 75
Accessibility 49
Best Practices 60
SEO 73
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://loe.org
Updated: 2nd March, 2021

1.80 seconds
First Contentful Paint (FCP)
54%
38%
8%

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

Simulate loading on desktop
75

Performance

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

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.8 s
The time taken for the page to become fully interactive.
Total Blocking Time — 20 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.02
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 0.8 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 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 loe.org as laggy when the latency is higher than 0.05 seconds.
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://loe.org/
http/1.1
0
69.721999985632
314
0
301
text/html
https://loe.org/
http/1.1
70.871000003535
184.75899996702
9451
37134
200
text/html
Document
https://loe.org/style.css
http/1.1
201.55900000827
274.55199998803
3911
17082
200
text/css
Stylesheet
https://loe.org/colorbox.css
http/1.1
201.77799998783
245.18299999181
1824
5152
200
text/css
Stylesheet
https://code.jquery.com/jquery-latest.min.js
http/1.1
201.97699998971
222.80300001148
33702
95786
200
application/javascript
Script
https://loe.org/js/jquery-1.3.2.min.js
http/1.1
202.19300000463
330.74000000488
20093
57254
200
application/javascript
Script
https://loe.org/js/jquery.cycle.all.min.js
http/1.1
202.41599995643
322.13799998863
7459
23729
200
application/javascript
Script
https://loe.org/js/jquery.color.js
http/1.1
202.62399996864
223.80099998554
1807
3660
200
application/javascript
Script
https://loe.org/js/jquery.colorbox-min.js
http/1.1
202.93299999321
300.05399999209
4531
9596
200
application/javascript
Script
https://loe.org/images/loenewlogo_registered.gif
http/1.1
323.4109999612
345.87399999145
2444
2159
200
image/gif
Image
https://loe.org/images/search.gif
http/1.1
335.27699997649
362.25999996532
1086
802
200
image/gif
Image
https://loe.org/images/spacer.gif
http/1.1
350.49300000537
369.42800000543
325
43
200
image/gif
Image
https://loe.org/content/2021-02-26/b_MARS_panoramic.jpg
http/1.1
350.69499997189
444.06599999638
100562
100272
200
image/jpeg
Image
https://loe.org/content/2021-02-26/b-INSLEE-Mount_Rainier_crew.jpg
http/1.1
350.86100001354
4213.9209999586
543644
543353
200
image/jpeg
Image
https://loe.org/content/2021-02-12/b_MSL_bottlenose.jpeg
http/1.1
351.01799998665
882.95399997151
184069
183778
200
image/jpeg
Image
https://loe.org/content/2021-02-05/b-GESSNER-leave-it-as-it-is_cover.jpg
http/1.1
351.24599997653
455.28599998215
302285
301995
200
image/jpeg
Image
https://loe.org/content/2021-01-29/b_LENDER_landscape.jpg
http/1.1
351.57999995863
2131.9659999572
198903
198612
200
image/jpeg
Image
https://loe.org/content/2021-01-22/b-CRA-bears_ears.jpg
http/1.1
351.75599996001
493.93299996154
476073
475783
200
image/jpeg
Image
https://loe.org/content/2012-09-14/otterbanner.gif
http/1.1
351.92699998152
1114.1099999659
318324
318034
200
image/gif
Image
https://loe.org/content/2013-12-13/b-Barrow_Offshore_wind_turbines_edit1.jpg
http/1.1
352.05699998187
875.49399997806
138101
137810
200
image/jpeg
Image
https://loe.org/content/2013-06-28/b-air-shot-banner.jpg
http/1.1
352.17199998442
477.49999997905
311307
311016
200
image/jpeg
Image
https://loe.org/content/2021-02-26/t_TEXAS_outages.jpg
http/1.1
352.28799999459
2094.6129999938
33025
32736
200
image/jpeg
Image
https://loe.org/images/read_more.gif
http/1.1
352.38100000424
2312.0340000023
1463
1177
200
image/gif
Image
https://loe.org/content/2021-02-26/t-INSLEE-Mount_Rainier_crew.jpg
http/1.1
352.74299996672
456.29199995892
103826
103535
200
image/jpeg
Image
https://loe.org/content/2021-02-26/t_MARS_panoramic.jpg
http/1.1
352.84299997147
432.41800001124
32915
32626
200
image/jpeg
Image
https://loe.org/content/2021-02-26/t_DYKSTRA_ferret.jpg
http/1.1
352.95299999416
4116.3199999719
37606
37317
200
image/jpeg
Image
https://loe.org/content/2021-02-26/t_BEES_bee.jpg
http/1.1
353.10800001025
3154.2330000084
44850
44561
200
image/jpeg
Image
https://loe.org/content/2021-02-12/t-MSLBLOG-Flukes.jpg
http/1.1
353.29599998659
3163.0649999715
83444
83154
200
image/jpeg
Image
https://loe.org/content/2021-01-29/t_LENDER_landscape.jpg
http/1.1
353.46899996512
3140.2169999783
42071
41782
200
image/jpeg
Image
https://loe.org/images/quotation.gif
http/1.1
353.6829999648
4105.3829999873
1547
1261
200
image/gif
Image
https://loe.org/images/logos/sailors_logo_lg.png
http/1.1
353.88899996178
417.87599999225
48541
48254
200
image/png
Image
https://loe.org/images/logos/logo-light.png
http/1.1
354.04800000833
429.37699996401
28941
28653
200
image/png
Image
https://loe.org/images/logos/UTC_stacked_300dpi.jpg
http/1.1
354.30100001395
3141.9809999643
91322
91032
200
image/jpeg
Image
https://loe.org/images/logos/GranthamFoundationLogo.jpg
http/1.1
354.46399997454
376.70199997956
8606
8319
200
image/jpeg
Image
https://loe.org/images/logos/ef_logo.jpg
http/1.1
355.77500000363
3055.8169999858
18829
18540
200
image/jpeg
Image
https://loe.org/images/promo/Elephant-family-thumbnail.jpg
http/1.1
355.91699997894
1093.9870000002
15633
15344
200
image/jpeg
Image
https://loe.org/images/promo/Smeagull-thumbnail.jpg
http/1.1
356.0919999727
3071.9800000079
12844
12555
200
image/jpeg
Image
https://loe.org/images/logos/PRX_Marks_Full_Color_Horizontal.png
http/1.1
356.24299995834
3307.4439999764
13790
13502
200
image/png
Image
https://loe.org/images/search_bg.gif
http/1.1
381.59899995662
400.73499997379
459
176
200
image/gif
Image
https://loe.org/images/bg_slider3.gif
http/1.1
386.82799995877
4111.2619999913
1384
1098
200
image/gif
Image
https://loe.org/images/rss_3.gif
http/1.1
387.37000001129
4121.5619999566
1546
1260
200
image/gif
Image
https://loe.org/images/rss_4.gif
http/1.1
387.79700000305
4127.6549999602
1487
1201
200
image/gif
Image
https://loe.org/images/IG_Glyph_small.gif
http/1.1
388.18800001172
414.42200000165
2616
2331
200
image/gif
Image
https://loe.org/images/rss_1.gif
http/1.1
388.71699996525
4094.8529999587
1516
1230
200
image/gif
Image
https://loe.org/images/overlay.png
http/1.1
389.37300001271
4099.3249999592
564
279
200
image/png
Image
https://loe.org/images/colorbox/controls.png
http/1.1
440.391000011
459.95799999218
4736
4450
200
image/png
Image
https://loe.org/images/colorbox/border.png
http/1.1
440.70499995723
466.9119999744
1395
1110
200
image/png
Image
https://loe.org/images/colorbox/loading_background.png
http/1.1
441.29300001077
4745.746999979
1531
1245
200
image/png
Image
https://loe.org/images/colorbox/loading.gif
http/1.1
441.73399999272
458.44899996882
9713
9427
200
image/gif
Image
https://loe.org/content/2021-02-26/LOE_210226_WEB.mp3
548.638999986
838.77999999095
0
0
-1
Media
https://loe.org/content/2021-02-26/LOE_210226_A1_The%20Broken%20Grid.mp3
http/1.1
549.91999996128
819.70699998783
399
65536
206
audio/mp3
Media
https://loe.org/content/2021-02-26/LOE_210226_B1_Dykstra.mp3
http/1.1
551.19299999205
656.89599997131
393
65536
206
audio/mp3
Media
https://loe.org/content/2021-02-26/LOE_210226_B2_Science%20Note.mp3
http/1.1
551.78499995964
4857.7709999518
422
65536
206
audio/mp3
Media
https://loe.org/content/2021-02-26/LOE_210226_B3_Inslee.mp3
http/1.1
552.94299998786
709.97999998508
398
65536
206
audio/mp3
Media
https://loe.org/content/2021-02-26/LOE_210226_C1_Mars.mp3
http/1.1
553.8129999768
5004.2869999888
427
65536
206
audio/mp3
Media
data
566.92999997176
567.00300000375
0
177
200
image/svg+xml
Image
data
568.90499999281
568.97199997911
0
351
200
image/svg+xml
Image
https://loe.org/images/colorbox/overlay.png
http/1.1
6749.6599999722
6778.1789999572
465
182
200
image/png
Image
https://loe.org/about/donatesmall.html
http/1.1
6763.5949999676
6785.0500000059
717
755
200
text/html
XHR
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)
214.705
9.764
227.205
6.963
304.565
21.383
362.564
192.727
555.315
8.846
565.968
10.381
591.897
19.708
617.639
12.589
6774.947
15.861
6816.214
22.261
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images — Potential savings of 349 KiB
Images can slow down the page's load time. Loe.org should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://loe.org/images/logos/UTC_stacked_300dpi.jpg
91032
89615
https://loe.org/content/2021-02-12/t-MSLBLOG-Flukes.jpg
83154
62366
https://loe.org/images/logos/sailors_logo_lg.png
48254
43504
https://loe.org/content/2021-01-29/t_LENDER_landscape.jpg
41782
31337
https://loe.org/content/2021-02-26/t-INSLEE-Mount_Rainier_crew.jpg
103535
24266
https://loe.org/images/logos/logo-light.png
28653
23856
https://loe.org/images/logos/ef_logo.jpg
18540
15081
https://loe.org/images/logos/PRX_Marks_Full_Color_Horizontal.png
13502
13037
https://loe.org/content/2021-02-26/t_BEES_bee.jpg
44561
10444
https://loe.org/content/2021-02-26/t_DYKSTRA_ferret.jpg
37317
8746
https://loe.org/images/logos/GranthamFoundationLogo.jpg
8319
7956
https://loe.org/content/2021-02-26/t_TEXAS_outages.jpg
32736
7673
https://loe.org/content/2021-02-26/t_MARS_panoramic.jpg
32626
7647
https://loe.org/images/promo/Elephant-family-thumbnail.jpg
15344
6713
https://loe.org/images/promo/Smeagull-thumbnail.jpg
12555
5493
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Loe.org should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Loe.org should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Loe.org should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Loe.org should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript — Potential savings of 23 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://code.jquery.com/jquery-latest.min.js
33702
23507
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 110 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://loe.org/
114.884
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Loe.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://loe.org/
190
https://loe.org/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Loe.org should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
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
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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://loe.org/content/2021-02-26/b_MARS_panoramic.jpg
0

Diagnostics

Avoids an excessive DOM size — 441 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
441
Maximum DOM Depth
11
Maximum Child Elements
26
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Loe.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.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://loe.org/
180.764
3.2
1.272
https://loe.org/js/jquery-1.3.2.min.js
160.124
95.821
1.777
Unattributable
92.255
7.408
0
https://code.jquery.com/jquery-latest.min.js
73.203
19.963
1.812
Minimizes main-thread work — 0.5 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
142.676
Script Evaluation
127.781
Other
118.065
Rendering
76.474
Parse HTML & CSS
40.943
Script Parsing & Compilation
7.428
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 57 requests • 3,232 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
57
3309636
Image
41
3223788
Script
5
67592
Document
1
9451
Stylesheet
2
5735
Media
6
2039
Other
2
1031
Font
0
0
Third-party
1
33702
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
33702
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
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.016482134111562
0.0011510959343899
0.00076175466246388
0.00076175466246388
div
0.0003437840426673
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task 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://loe.org/js/jquery-1.3.2.min.js
800
96
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

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

Metrics

Largest Contentful Paint — 2.3 s
The timing of the largest text or image that is painted.

Opportunities

Eliminate render-blocking resources — Potential savings of 550 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Loe.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://loe.org/style.css
3911
70
https://loe.org/colorbox.css
1824
150
https://code.jquery.com/jquery-latest.min.js
33702
310
https://loe.org/js/jquery-1.3.2.min.js
20093
230
https://loe.org/js/jquery.cycle.all.min.js
7459
190
https://loe.org/js/jquery.color.js
1807
150
https://loe.org/js/jquery.colorbox-min.js
4531
150
Use video formats for animated content — Potential savings of 183 KiB
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.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://loe.org/content/2012-09-14/otterbanner.gif
318034
187640

Diagnostics

Avoid enormous network payloads — Total size was 3,230 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://loe.org/content/2021-02-26/b-INSLEE-Mount_Rainier_crew.jpg
543644
https://loe.org/content/2021-01-22/b-CRA-bears_ears.jpg
476073
https://loe.org/content/2012-09-14/otterbanner.gif
318324
https://loe.org/content/2013-06-28/b-air-shot-banner.jpg
311307
https://loe.org/content/2021-02-05/b-GESSNER-leave-it-as-it-is_cover.jpg
302285
https://loe.org/content/2021-01-29/b_LENDER_landscape.jpg
198903
https://loe.org/content/2021-02-12/b_MSL_bottlenose.jpeg
184069
https://loe.org/content/2013-12-13/b-Barrow_Offshore_wind_turbines_edit1.jpg
138101
https://loe.org/content/2021-02-26/t-INSLEE-Mount_Rainier_crew.jpg
103826
https://loe.org/content/2021-02-26/b_MARS_panoramic.jpg
100562

Metrics

Speed Index — 3.4 s
The time taken for the page contents to be visibly populated.

Opportunities

Efficiently encode images — Potential savings of 1,662 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://loe.org/content/2021-02-26/b-INSLEE-Mount_Rainier_crew.jpg
543353
390773
https://loe.org/content/2021-01-22/b-CRA-bears_ears.jpg
475783
333791
https://loe.org/content/2021-02-05/b-GESSNER-leave-it-as-it-is_cover.jpg
301995
187282
https://loe.org/content/2013-06-28/b-air-shot-banner.jpg
311016
181362
https://loe.org/content/2021-01-29/b_LENDER_landscape.jpg
198612
136476
https://loe.org/content/2013-12-13/b-Barrow_Offshore_wind_turbines_edit1.jpg
137810
100221
https://loe.org/content/2021-02-26/t-INSLEE-Mount_Rainier_crew.jpg
103535
80917
https://loe.org/content/2021-02-12/t-MSLBLOG-Flukes.jpg
83154
63784
https://loe.org/images/logos/UTC_stacked_300dpi.jpg
91032
44033
https://loe.org/content/2021-02-12/b_MSL_bottlenose.jpeg
183778
41290
https://loe.org/content/2021-02-26/t_BEES_bee.jpg
44561
33284
https://loe.org/content/2021-01-29/t_LENDER_landscape.jpg
41782
31864
https://loe.org/content/2021-02-26/t_DYKSTRA_ferret.jpg
37317
18317
https://loe.org/content/2021-02-26/t_MARS_panoramic.jpg
32626
17814
https://loe.org/content/2021-02-26/b_MARS_panoramic.jpg
100272
16776
https://loe.org/content/2021-02-26/t_TEXAS_outages.jpg
32736
15744
https://loe.org/images/logos/ef_logo.jpg
18540
7953
Serve images in next-gen formats — Potential savings of 2,069 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://loe.org/content/2021-02-26/b-INSLEE-Mount_Rainier_crew.jpg
543353
435529
https://loe.org/content/2021-01-22/b-CRA-bears_ears.jpg
475783
375441
https://loe.org/content/2021-02-05/b-GESSNER-leave-it-as-it-is_cover.jpg
301995
227401
https://loe.org/content/2013-06-28/b-air-shot-banner.jpg
311016
224984
https://loe.org/content/2021-01-29/b_LENDER_landscape.jpg
198612
169952
https://loe.org/content/2013-12-13/b-Barrow_Offshore_wind_turbines_edit1.jpg
137810
125232
https://loe.org/content/2021-02-26/t-INSLEE-Mount_Rainier_crew.jpg
103535
87101
https://loe.org/content/2021-02-12/b_MSL_bottlenose.jpeg
183778
80426
https://loe.org/images/logos/UTC_stacked_300dpi.jpg
91032
71324
https://loe.org/content/2021-02-12/t-MSLBLOG-Flukes.jpg
83154
68956
https://loe.org/content/2021-02-26/b_MARS_panoramic.jpg
100272
48104
https://loe.org/content/2021-02-26/t_BEES_bee.jpg
44561
38449
https://loe.org/content/2021-01-29/t_LENDER_landscape.jpg
41782
36558
https://loe.org/images/logos/sailors_logo_lg.png
48254
36552
https://loe.org/content/2021-02-26/t_DYKSTRA_ferret.jpg
37317
23161
https://loe.org/content/2021-02-26/t_MARS_panoramic.jpg
32626
22350
https://loe.org/content/2021-02-26/t_TEXAS_outages.jpg
32736
21006
https://loe.org/images/logos/ef_logo.jpg
18540
12914
https://loe.org/images/logos/logo-light.png
28653
12787

Diagnostics

Serve static assets with an efficient cache policy — 53 resources found
Loe.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://loe.org/content/2021-02-26/b-INSLEE-Mount_Rainier_crew.jpg
0
543644
https://loe.org/content/2021-01-22/b-CRA-bears_ears.jpg
0
476073
https://loe.org/content/2012-09-14/otterbanner.gif
0
318324
https://loe.org/content/2013-06-28/b-air-shot-banner.jpg
0
311307
https://loe.org/content/2021-02-05/b-GESSNER-leave-it-as-it-is_cover.jpg
0
302285
https://loe.org/content/2021-01-29/b_LENDER_landscape.jpg
0
198903
https://loe.org/content/2021-02-12/b_MSL_bottlenose.jpeg
0
184069
https://loe.org/content/2013-12-13/b-Barrow_Offshore_wind_turbines_edit1.jpg
0
138101
https://loe.org/content/2021-02-26/t-INSLEE-Mount_Rainier_crew.jpg
0
103826
https://loe.org/content/2021-02-26/b_MARS_panoramic.jpg
0
100562
https://loe.org/images/logos/UTC_stacked_300dpi.jpg
0
91322
https://loe.org/content/2021-02-12/t-MSLBLOG-Flukes.jpg
0
83444
https://loe.org/images/logos/sailors_logo_lg.png
0
48541
https://loe.org/content/2021-02-26/t_BEES_bee.jpg
0
44850
https://loe.org/content/2021-01-29/t_LENDER_landscape.jpg
0
42071
https://loe.org/content/2021-02-26/t_DYKSTRA_ferret.jpg
0
37606
https://loe.org/content/2021-02-26/t_TEXAS_outages.jpg
0
33025
https://loe.org/content/2021-02-26/t_MARS_panoramic.jpg
0
32915
https://loe.org/images/logos/logo-light.png
0
28941
https://loe.org/js/jquery-1.3.2.min.js
0
20093
https://loe.org/images/logos/ef_logo.jpg
0
18829
https://loe.org/images/promo/Elephant-family-thumbnail.jpg
0
15633
https://loe.org/images/logos/PRX_Marks_Full_Color_Horizontal.png
0
13790
https://loe.org/images/promo/Smeagull-thumbnail.jpg
0
12844
https://loe.org/images/colorbox/loading.gif
0
9713
https://loe.org/images/logos/GranthamFoundationLogo.jpg
0
8606
https://loe.org/js/jquery.cycle.all.min.js
0
7459
https://loe.org/images/colorbox/controls.png
0
4736
https://loe.org/js/jquery.colorbox-min.js
0
4531
https://loe.org/style.css
0
3911
https://loe.org/images/IG_Glyph_small.gif
0
2616
https://loe.org/images/loenewlogo_registered.gif
0
2444
https://loe.org/colorbox.css
0
1824
https://loe.org/js/jquery.color.js
0
1807
https://loe.org/images/quotation.gif
0
1547
https://loe.org/images/rss_3.gif
0
1546
https://loe.org/images/colorbox/loading_background.png
0
1531
https://loe.org/images/rss_1.gif
0
1516
https://loe.org/images/rss_4.gif
0
1487
https://loe.org/images/read_more.gif
0
1463
https://loe.org/images/colorbox/border.png
0
1395
https://loe.org/images/bg_slider3.gif
0
1384
https://loe.org/images/search.gif
0
1086
https://loe.org/images/overlay.png
0
564
https://loe.org/images/colorbox/overlay.png
0
465
https://loe.org/images/search_bg.gif
0
459
https://loe.org/content/2021-02-26/LOE_210226_C1_Mars.mp3
0
427
https://loe.org/content/2021-02-26/LOE_210226_B2_Science%20Note.mp3
0
422
https://loe.org/content/2021-02-26/LOE_210226_A1_The%20Broken%20Grid.mp3
0
399
https://loe.org/content/2021-02-26/LOE_210226_B3_Inslee.mp3
0
398
https://loe.org/content/2021-02-26/LOE_210226_B1_Dykstra.mp3
0
393
https://loe.org/images/spacer.gif
0
325
https://code.jquery.com/jquery-latest.min.js
86400000
33702
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://loe.org/content/2021-02-26/t-INSLEE-Mount_Rainier_crew.jpg
img
https://loe.org/content/2021-02-26/b_MARS_panoramic.jpg
https://loe.org/images/logos/UTC_stacked_300dpi.jpg
img
https://loe.org/content/2021-02-12/t-MSLBLOG-Flukes.jpg
img
https://loe.org/images/logos/sailors_logo_lg.png
img
https://loe.org/content/2021-01-29/t_LENDER_landscape.jpg
img
https://loe.org/content/2021-02-26/t_TEXAS_outages.jpg
img
https://loe.org/content/2021-02-26/t_MARS_panoramic.jpg
img
https://loe.org/images/logos/logo-light.png
img
https://loe.org/images/logos/ef_logo.jpg
img
https://loe.org/images/logos/PRX_Marks_Full_Color_Horizontal.png
PRI
https://loe.org/images/logos/GranthamFoundationLogo.jpg
img
49

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of loe.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.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<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 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"]`
Loe.org may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Internationalization and localization

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
`<input type="image">` elements do not have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Failing Elements
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
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.
60

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

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.3.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://loe.org/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 6 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
6
Medium

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://loe.org/images/spacer.gif
24 x 23
1 x 1
24 x 23

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
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: net::ERR_CONNECTION_FAILED
73

SEO

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

Crawling and Indexing

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

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.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
Document uses plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.
Element source

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 loe.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 loe.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) 59
Performance 69
Accessibility 49
Best Practices 60
SEO 74
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://loe.org
Updated: 2nd March, 2021

2.44 seconds
First Contentful Paint (FCP)
29%
57%
14%

0.02 seconds
First Input Delay (FID)
92%
6%
2%

Simulate loading on mobile
69

Performance

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

Metrics

Speed Index — 3.1 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 3.1 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.011
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 3.1 s
The time taken for the page's main thread to be quiet enough to handle input.
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://loe.org/
http/1.1
0
57.032000040635
314
0
301
text/html
https://loe.org/
http/1.1
57.856000028551
129.27100004163
9451
37134
200
text/html
Document
https://loe.org/style.css
http/1.1
149.49199999683
213.61700003035
3911
17082
200
text/css
Stylesheet
https://loe.org/colorbox.css
http/1.1
149.82900000177
216.54200006742
1825
5152
200
text/css
Stylesheet
https://code.jquery.com/jquery-latest.min.js
http/1.1
150.18200001214
164.01399997994
33702
95786
200
application/javascript
Script
https://loe.org/js/jquery-1.3.2.min.js
http/1.1
150.42800002266
188.29800002277
20092
57254
200
application/javascript
Script
https://loe.org/js/jquery.cycle.all.min.js
http/1.1
150.68000007886
219.60399998352
7459
23729
200
application/javascript
Script
https://loe.org/js/jquery.color.js
http/1.1
150.95400006976
215.70900001097
1808
3660
200
application/javascript
Script
https://loe.org/js/jquery.colorbox-min.js
http/1.1
151.48500003852
218.28600007575
4531
9596
200
application/javascript
Script
https://loe.org/images/loenewlogo_registered.gif
http/1.1
261.09699998051
281.60300001036
2444
2159
200
image/gif
Image
https://loe.org/images/search.gif
http/1.1
261.72000006773
279.44000007119
1086
802
200
image/gif
Image
https://loe.org/images/spacer.gif
http/1.1
269.88500007428
289.24399998505
325
43
200
image/gif
Image
https://loe.org/content/2021-02-26/b_MARS_panoramic.jpg
http/1.1
270.1240000315
2557.0010000374
100563
100272
200
image/jpeg
Image
https://loe.org/content/2021-02-26/b-INSLEE-Mount_Rainier_crew.jpg
http/1.1
270.40699997451
373.48499998916
543643
543353
200
image/jpeg
Image
https://loe.org/content/2021-02-12/b_MSL_bottlenose.jpeg
http/1.1
270.87700006086
337.95499999542
184068
183778
200
image/jpeg
Image
https://loe.org/content/2021-02-05/b-GESSNER-leave-it-as-it-is_cover.jpg
http/1.1
271.18699997663
3385.3840000229
302286
301995
200
image/jpeg
Image
https://loe.org/content/2021-01-29/b_LENDER_landscape.jpg
http/1.1
271.48400002625
393.33600003738
198903
198612
200
image/jpeg
Image
https://loe.org/content/2021-01-22/b-CRA-bears_ears.jpg
http/1.1
271.80099999532
3476.5690000495
476074
475783
200
image/jpeg
Image
https://loe.org/content/2012-09-14/otterbanner.gif
http/1.1
271.99799998198
738.23400004767
318324
318034
200
image/gif
Image
https://loe.org/content/2013-12-13/b-Barrow_Offshore_wind_turbines_edit1.jpg
http/1.1
272.16499997303
341.88700001687
138100
137810
200
image/jpeg
Image
https://loe.org/content/2013-06-28/b-air-shot-banner.jpg
http/1.1
272.340000025
359.63199997786
311306
311016
200
image/jpeg
Image
https://loe.org/content/2021-02-26/t_TEXAS_outages.jpg
http/1.1
272.63100002892
311.9810000062
33024
32736
200
image/jpeg
Image
https://loe.org/images/read_more.gif
http/1.1
272.79199997429
3283.7770000333
1463
1177
200
image/gif
Image
https://loe.org/content/2021-02-26/t-INSLEE-Mount_Rainier_crew.jpg
http/1.1
273.18000001833
3358.7970000226
103826
103535
200
image/jpeg
Image
https://loe.org/content/2021-02-26/t_MARS_panoramic.jpg
http/1.1
273.87899998575
2270.0900000054
32915
32626
200
image/jpeg
Image
https://loe.org/content/2021-02-26/t_DYKSTRA_ferret.jpg
http/1.1
274.16100003757
970.52600001916
37606
37317
200
image/jpeg
Image
https://loe.org/content/2021-02-26/t_BEES_bee.jpg
http/1.1
274.35099997092
1448.9390000235
44850
44561
200
image/jpeg
Image
https://loe.org/content/2021-02-12/t-MSLBLOG-Flukes.jpg
http/1.1
274.52500001527
2293.8279999653
83444
83154
200
image/jpeg
Image
https://loe.org/content/2021-01-29/t_LENDER_landscape.jpg
http/1.1
274.81500001159
1271.2049999973
42071
41782
200
image/jpeg
Image
https://loe.org/images/quotation.gif
http/1.1
275.06500005256
3291.109999991
1547
1261
200
image/gif
Image
https://loe.org/images/logos/sailors_logo_lg.png
http/1.1
275.27700003702
3322.5559999701
48542
48254
200
image/png
Image
https://loe.org/images/logos/logo-light.png
http/1.1
275.51599999424
2271.078000078
28941
28653
200
image/png
Image
https://loe.org/images/logos/UTC_stacked_300dpi.jpg
http/1.1
275.67400003318
1276.7110000132
91322
91032
200
image/jpeg
Image
https://loe.org/images/logos/GranthamFoundationLogo.jpg
http/1.1
276.49099996779
2250.9009999922
8607
8319
200
image/jpeg
Image
https://loe.org/images/logos/ef_logo.jpg
http/1.1
276.74700005446
1806.2630000059
18829
18540
200
image/jpeg
Image
https://loe.org/images/promo/Elephant-family-thumbnail.jpg
http/1.1
276.9280000357
1551.3920000521
15633
15344
200
image/jpeg
Image
https://loe.org/images/promo/Smeagull-thumbnail.jpg
http/1.1
277.11300004739
3303.0590000562
12844
12555
200
image/jpeg
Image
https://loe.org/images/logos/PRX_Marks_Full_Color_Horizontal.png
http/1.1
277.29700005148
3259.3730000081
13790
13502
200
image/png
Image
https://loe.org/images/search_bg.gif
http/1.1
331.94800000638
348.99600001518
459
176
200
image/gif
Image
https://loe.org/images/bg_slider3.gif
http/1.1
335.7890000334
352.73400007281
1383
1098
200
image/gif
Image
https://loe.org/images/rss_3.gif
http/1.1
336.55800006818
4307.2940000566
1546
1260
200
image/gif
Image
https://loe.org/images/rss_4.gif
http/1.1
337.14700001292
354.70000002533
1486
1201
200
image/gif
Image
https://loe.org/images/IG_Glyph_small.gif
http/1.1
337.72499999031
356.35100002401
2616
2331
200
image/gif
Image
https://loe.org/images/rss_1.gif
http/1.1
338.82200007793
4294.1390000051
1516
1230
200
image/gif
Image
https://loe.org/images/overlay.png
http/1.1
339.30400002282
4266.3480000338
564
279
200
image/png
Image
https://loe.org/images/colorbox/controls.png
http/1.1
402.85700000823
422.26600006688
4736
4450
200
image/png
Image
https://loe.org/images/colorbox/border.png
http/1.1
403.55100005399
421.69800004922
1395
1110
200
image/png
Image
https://loe.org/images/colorbox/loading_background.png
http/1.1
404.04499997385
423.24799997732
1530
1245
200
image/png
Image
https://loe.org/images/colorbox/loading.gif
http/1.1
404.8340000445
4307.8189999796
9714
9427
200
image/gif
Image
https://loe.org/content/2021-02-26/LOE_210226_WEB.mp3
641.96999999695
836.1590000568
0
0
-1
Media
https://loe.org/content/2021-02-26/LOE_210226_A1_The%20Broken%20Grid.mp3
http/1.1
648.34499999415
905.2049999591
399
65536
206
audio/mp3
Media
https://loe.org/content/2021-02-26/LOE_210226_B1_Dykstra.mp3
http/1.1
649.56799999345
777.92300004512
394
65536
206
audio/mp3
Media
https://loe.org/content/2021-02-26/LOE_210226_B2_Science%20Note.mp3
http/1.1
649.8080000747
4459.3750000931
423
65536
206
audio/mp3
Media
https://loe.org/content/2021-02-26/LOE_210226_B3_Inslee.mp3
http/1.1
651.04999998584
4668.4729999397
427
65536
206
audio/mp3
Media
https://loe.org/content/2021-02-26/LOE_210226_C1_Mars.mp3
http/1.1
651.85600006953
4637.9530000268
427
65536
206
audio/mp3
Media
data
661.49299999233
661.57400002703
0
177
200
image/svg+xml
Image
data
664.23500003293
664.32700003497
0
351
200
image/svg+xml
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)
165.915
10.429
180.808
8.312
251.464
40.889
294.465
360.167
654.653
7.086
662.52
13.366
692.62
23.798
819.93
5.206
881.256
5.041
4498.553
5.492
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Loe.org should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Loe.org should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Loe.org should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Loe.org should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript — Potential savings of 23 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://code.jquery.com/jquery-latest.min.js
33702
23507
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 70 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://loe.org/
72.411
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Loe.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://loe.org/
630
https://loe.org/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Loe.org should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
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
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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids an excessive DOM size — 430 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
430
Maximum DOM Depth
11
Maximum Child Elements
26
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Loe.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.
JavaScript execution time — 0.7 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://loe.org/js/jquery-1.3.2.min.js
967.776
478.42
8.612
https://loe.org/
811.432
11.924
6.96
Unattributable
467.884
56.08
0
https://code.jquery.com/jquery-latest.min.js
359.668
107.228
8.628
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 55 requests • 3,231 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
55
3308484
Image
40
3223321
Script
5
67592
Document
1
9451
Stylesheet
2
5736
Media
6
2070
Other
1
314
Font
0
0
Third-party
1
33702
Minimize third-party usage — Third-party code blocked the main thread for 170 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)
33702
172.62
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 — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.010986328125
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 3 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://loe.org/js/jquery.cycle.all.min.js
2347
720
https://code.jquery.com/jquery-latest.min.js
2265
82
Unattributable
1185
53
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

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

Metrics

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

Other

First Meaningful Paint — 3.1 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 5160 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Properly size images — Potential savings of 110 KiB
Images can slow down the page's load time. Loe.org should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://loe.org/images/logos/UTC_stacked_300dpi.jpg
91032
81265
https://loe.org/images/logos/sailors_logo_lg.png
48254
15524
https://loe.org/images/logos/PRX_Marks_Full_Color_Horizontal.png
13502
10297
https://loe.org/images/logos/GranthamFoundationLogo.jpg
8319
5817

Diagnostics

Avoid enormous network payloads — Total size was 3,229 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://loe.org/content/2021-02-26/b-INSLEE-Mount_Rainier_crew.jpg
543643
https://loe.org/content/2021-01-22/b-CRA-bears_ears.jpg
476074
https://loe.org/content/2012-09-14/otterbanner.gif
318324
https://loe.org/content/2013-06-28/b-air-shot-banner.jpg
311306
https://loe.org/content/2021-02-05/b-GESSNER-leave-it-as-it-is_cover.jpg
302286
https://loe.org/content/2021-01-29/b_LENDER_landscape.jpg
198903
https://loe.org/content/2021-02-12/b_MSL_bottlenose.jpeg
184068
https://loe.org/content/2013-12-13/b-Barrow_Offshore_wind_turbines_edit1.jpg
138100
https://loe.org/content/2021-02-26/t-INSLEE-Mount_Rainier_crew.jpg
103826
https://loe.org/content/2021-02-26/b_MARS_panoramic.jpg
100563
Minimize main-thread work — 2.6 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
859.692
Script Evaluation
662.764
Other
530.6
Parse HTML & CSS
295.62
Rendering
254.536
Script Parsing & Compilation
40.268

Metrics

Largest Contentful Paint — 10.9 s
The timing of the largest text or image that is painted.

Other

Max Potential First Input Delay — 720 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 190 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 loe.org as laggy when the latency is higher than 0.05 seconds.

Opportunities

Eliminate render-blocking resources — Potential savings of 1,920 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Loe.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://loe.org/style.css
3911
180
https://loe.org/colorbox.css
1825
180
https://code.jquery.com/jquery-latest.min.js
33702
1080
https://loe.org/js/jquery-1.3.2.min.js
20092
330
https://loe.org/js/jquery.cycle.all.min.js
7459
180
https://loe.org/js/jquery.color.js
1808
180
https://loe.org/js/jquery.colorbox-min.js
4531
180
Efficiently encode images — Potential savings of 1,662 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://loe.org/content/2021-02-26/b-INSLEE-Mount_Rainier_crew.jpg
543353
390773
https://loe.org/content/2021-01-22/b-CRA-bears_ears.jpg
475783
333791
https://loe.org/content/2021-02-05/b-GESSNER-leave-it-as-it-is_cover.jpg
301995
187282
https://loe.org/content/2013-06-28/b-air-shot-banner.jpg
311016
181362
https://loe.org/content/2021-01-29/b_LENDER_landscape.jpg
198612
136476
https://loe.org/content/2013-12-13/b-Barrow_Offshore_wind_turbines_edit1.jpg
137810
100221
https://loe.org/content/2021-02-26/t-INSLEE-Mount_Rainier_crew.jpg
103535
80917
https://loe.org/content/2021-02-12/t-MSLBLOG-Flukes.jpg
83154
63784
https://loe.org/images/logos/UTC_stacked_300dpi.jpg
91032
44033
https://loe.org/content/2021-02-12/b_MSL_bottlenose.jpeg
183778
41290
https://loe.org/content/2021-02-26/t_BEES_bee.jpg
44561
33284
https://loe.org/content/2021-01-29/t_LENDER_landscape.jpg
41782
31864
https://loe.org/content/2021-02-26/t_DYKSTRA_ferret.jpg
37317
18317
https://loe.org/content/2021-02-26/t_MARS_panoramic.jpg
32626
17814
https://loe.org/content/2021-02-26/b_MARS_panoramic.jpg
100272
16776
https://loe.org/content/2021-02-26/t_TEXAS_outages.jpg
32736
15744
https://loe.org/images/logos/ef_logo.jpg
18540
7953
Serve images in next-gen formats — Potential savings of 2,069 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://loe.org/content/2021-02-26/b-INSLEE-Mount_Rainier_crew.jpg
543353
435529
https://loe.org/content/2021-01-22/b-CRA-bears_ears.jpg
475783
375441
https://loe.org/content/2021-02-05/b-GESSNER-leave-it-as-it-is_cover.jpg
301995
227401
https://loe.org/content/2013-06-28/b-air-shot-banner.jpg
311016
224984
https://loe.org/content/2021-01-29/b_LENDER_landscape.jpg
198612
169952
https://loe.org/content/2013-12-13/b-Barrow_Offshore_wind_turbines_edit1.jpg
137810
125232
https://loe.org/content/2021-02-26/t-INSLEE-Mount_Rainier_crew.jpg
103535
87101
https://loe.org/content/2021-02-12/b_MSL_bottlenose.jpeg
183778
80426
https://loe.org/images/logos/UTC_stacked_300dpi.jpg
91032
71324
https://loe.org/content/2021-02-12/t-MSLBLOG-Flukes.jpg
83154
68956
https://loe.org/content/2021-02-26/b_MARS_panoramic.jpg
100272
48104
https://loe.org/content/2021-02-26/t_BEES_bee.jpg
44561
38449
https://loe.org/content/2021-01-29/t_LENDER_landscape.jpg
41782
36558
https://loe.org/images/logos/sailors_logo_lg.png
48254
36552
https://loe.org/content/2021-02-26/t_DYKSTRA_ferret.jpg
37317
23161
https://loe.org/content/2021-02-26/t_MARS_panoramic.jpg
32626
22350
https://loe.org/content/2021-02-26/t_TEXAS_outages.jpg
32736
21006
https://loe.org/images/logos/ef_logo.jpg
18540
12914
https://loe.org/images/logos/logo-light.png
28653
12787
Use video formats for animated content — Potential savings of 183 KiB
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.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://loe.org/content/2012-09-14/otterbanner.gif
318034
187640

Diagnostics

Serve static assets with an efficient cache policy — 52 resources found
Loe.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://loe.org/content/2021-02-26/b-INSLEE-Mount_Rainier_crew.jpg
0
543643
https://loe.org/content/2021-01-22/b-CRA-bears_ears.jpg
0
476074
https://loe.org/content/2012-09-14/otterbanner.gif
0
318324
https://loe.org/content/2013-06-28/b-air-shot-banner.jpg
0
311306
https://loe.org/content/2021-02-05/b-GESSNER-leave-it-as-it-is_cover.jpg
0
302286
https://loe.org/content/2021-01-29/b_LENDER_landscape.jpg
0
198903
https://loe.org/content/2021-02-12/b_MSL_bottlenose.jpeg
0
184068
https://loe.org/content/2013-12-13/b-Barrow_Offshore_wind_turbines_edit1.jpg
0
138100
https://loe.org/content/2021-02-26/t-INSLEE-Mount_Rainier_crew.jpg
0
103826
https://loe.org/content/2021-02-26/b_MARS_panoramic.jpg
0
100563
https://loe.org/images/logos/UTC_stacked_300dpi.jpg
0
91322
https://loe.org/content/2021-02-12/t-MSLBLOG-Flukes.jpg
0
83444
https://loe.org/images/logos/sailors_logo_lg.png
0
48542
https://loe.org/content/2021-02-26/t_BEES_bee.jpg
0
44850
https://loe.org/content/2021-01-29/t_LENDER_landscape.jpg
0
42071
https://loe.org/content/2021-02-26/t_DYKSTRA_ferret.jpg
0
37606
https://loe.org/content/2021-02-26/t_TEXAS_outages.jpg
0
33024
https://loe.org/content/2021-02-26/t_MARS_panoramic.jpg
0
32915
https://loe.org/images/logos/logo-light.png
0
28941
https://loe.org/js/jquery-1.3.2.min.js
0
20092
https://loe.org/images/logos/ef_logo.jpg
0
18829
https://loe.org/images/promo/Elephant-family-thumbnail.jpg
0
15633
https://loe.org/images/logos/PRX_Marks_Full_Color_Horizontal.png
0
13790
https://loe.org/images/promo/Smeagull-thumbnail.jpg
0
12844
https://loe.org/images/colorbox/loading.gif
0
9714
https://loe.org/images/logos/GranthamFoundationLogo.jpg
0
8607
https://loe.org/js/jquery.cycle.all.min.js
0
7459
https://loe.org/images/colorbox/controls.png
0
4736
https://loe.org/js/jquery.colorbox-min.js
0
4531
https://loe.org/style.css
0
3911
https://loe.org/images/IG_Glyph_small.gif
0
2616
https://loe.org/images/loenewlogo_registered.gif
0
2444
https://loe.org/colorbox.css
0
1825
https://loe.org/js/jquery.color.js
0
1808
https://loe.org/images/quotation.gif
0
1547
https://loe.org/images/rss_3.gif
0
1546
https://loe.org/images/colorbox/loading_background.png
0
1530
https://loe.org/images/rss_1.gif
0
1516
https://loe.org/images/rss_4.gif
0
1486
https://loe.org/images/read_more.gif
0
1463
https://loe.org/images/colorbox/border.png
0
1395
https://loe.org/images/bg_slider3.gif
0
1383
https://loe.org/images/search.gif
0
1086
https://loe.org/images/overlay.png
0
564
https://loe.org/images/search_bg.gif
0
459
https://loe.org/content/2021-02-26/LOE_210226_B3_Inslee.mp3
0
427
https://loe.org/content/2021-02-26/LOE_210226_C1_Mars.mp3
0
427
https://loe.org/content/2021-02-26/LOE_210226_B2_Science%20Note.mp3
0
423
https://loe.org/content/2021-02-26/LOE_210226_A1_The%20Broken%20Grid.mp3
0
399
https://loe.org/content/2021-02-26/LOE_210226_B1_Dykstra.mp3
0
394
https://loe.org/images/spacer.gif
0
325
https://code.jquery.com/jquery-latest.min.js
86400000
33702
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://loe.org/content/2021-02-26/t-INSLEE-Mount_Rainier_crew.jpg
img
https://loe.org/content/2021-02-26/b_MARS_panoramic.jpg
https://loe.org/images/logos/UTC_stacked_300dpi.jpg
img
https://loe.org/content/2021-02-12/t-MSLBLOG-Flukes.jpg
img
https://loe.org/images/logos/sailors_logo_lg.png
img
https://loe.org/content/2021-01-29/t_LENDER_landscape.jpg
img
https://loe.org/content/2021-02-26/t_TEXAS_outages.jpg
img
https://loe.org/content/2021-02-26/t_MARS_panoramic.jpg
img
https://loe.org/images/logos/logo-light.png
img
https://loe.org/images/logos/ef_logo.jpg
img
https://loe.org/images/logos/PRX_Marks_Full_Color_Horizontal.png
PRI
https://loe.org/images/logos/GranthamFoundationLogo.jpg
img
49

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of loe.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.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<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 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"]`
Loe.org may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Internationalization and localization

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
`<input type="image">` elements do not have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Failing Elements
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
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.
60

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

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.3.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://loe.org/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 6 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
6
Medium

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://loe.org/images/loenewlogo_registered.gif
200 x 68
200 x 68
400 x 136
https://loe.org/images/spacer.gif
24 x 23
1 x 1
48 x 46

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
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: net::ERR_CONNECTION_FAILED
74

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for loe.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 loe.org on mobile screens.
Document uses legible font sizes — 99.82% 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
.footer p
0.11%
11px
.footer a
0.05%
11px
#slider_controls ul li a
0.02%
11px
99.82%
≥ 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.
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.

Crawling and Indexing

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

Mobile Friendly

Tap targets are not sized appropriately — 68% 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
30x14
38x14
30x14
43x14
36x14
49x14
28x23
28x23
28x23
32x14

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.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
Document uses plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.
Element source

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 loe.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 loe.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: 45.63.17.91
Continent: North America
Country: United States
United States Flag
Region: New Jersey
City: Matawan
Longitude: -74.2307
Latitude: 40.4652
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Vultr Holdings, LLC
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
SNAPNAMES 33, LLC 162.159.133.53
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 4.3/5
WOT Trustworthiness: 85/100
WOT Child Safety: 91/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: loe.org
Issued By: R3
Valid From: 26th February, 2021
Valid To: 27th May, 2021
Subject: CN = loe.org
Hash: 133589d8
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03EF2139002BBAE785CEBF783B5812C7F79A
Serial Number (Hex): 03EF2139002BBAE785CEBF783B5812C7F79A
Valid From: 26th February, 2024
Valid To: 27th May, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Feb 26 07:00:09.323 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:5E:FB:62:5B:1B:D6:16:BD:AD:68:38:CE:
D2:EE:03:CD:3B:61:2D:2D:41:5F:13:2F:C9:99:3A:D5:
16:3A:9F:6E:02:21:00:FE:73:09:ED:25:05:02:04:9B:
C1:44:AF:16:C3:18:3D:39:E7:2E:33:3E:29:2D:C1:4F:
F5:1E:2A:AB:4F:3C:0B
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
Timestamp : Feb 26 07:00:09.525 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:A7:EF:79:22:7C:0E:CF:16:B3:53:B9:
E7:C1:5F:80:21:4D:A9:61:7D:9C:9D:50:17:8F:94:60:
16:77:04:F7:7F:02:21:00:9C:34:1E:87:4A:74:5C:58:
1C:9E:E9:88:7B:7E:35:64:0F:B8:55:5B:DD:F7:FA:8A:
A2:4E:7A:F7:6B:A1:6C:FD
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:loe.org
DNS:stream.loe.org
DNS:www.loe.org
DNS:audio.loe.org
Technical

DNS Lookup

A Records

Host IP Address Class TTL
loe.org. 45.63.17.91 IN 14399

NS Records

Host Nameserver Class TTL
loe.org. ns2.dreamhost.com. IN 14399
loe.org. ns1.dreamhost.com. IN 14399
loe.org. ns3.dreamhost.com. IN 14399

MX Records

Priority Host Server Class TTL
30 loe.org. ASPMX4.GOOGLEMAIL.com. IN 14399
30 loe.org. ASPMX5.GOOGLEMAIL.com. IN 14399
30 loe.org. ASPMX3.GOOGLEMAIL.com. IN 14399
10 loe.org. ASPMX.L.GOOGLE.com. IN 14399
20 loe.org. ALT2.ASPMX.L.GOOGLE.com. IN 14399
20 loe.org. ALT1.ASPMX.L.GOOGLE.com. IN 14399
30 loe.org. ASPMX2.GOOGLEMAIL.com. IN 14399

SOA Records

Domain Name Primary NS Responsible Email TTL
loe.org. ns1.dreamhost.com. hostmaster.dreamhost.com. 14399

TXT Records

Host Value Class TTL
loe.org. google-site-verification=4c2chN_NwhGQPRkdtE7FTLRbOC9HswtXvzjgt2pvrbI IN 14399

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 2nd March, 2021
Server: Apache/2.4.25 (Debian)
Content-Type: text/html; charset=UTF-8

Whois Lookup

Created: 18th July, 1996
Changed: 18th July, 2020
Expires: 17th July, 2030
Registrar: Network Solutions, LLC
Status: clientTransferProhibited
Nameservers: ns1.dreamhost.com
ns2.dreamhost.com
ns3.dreamhost.com
Owner Organization: Living on Earth
Owner State: MA
Owner Country: US
Full Whois: Domain Name: LOE.ORG
Registry Domain ID: D36953-LROR
Registrar WHOIS Server: whois.networksolutions.com
Registrar URL: http://www.networksolutions.com
Updated Date: 2020-07-18T01:43:54Z
Creation Date: 1996-07-18T04:00:00Z
Registry Expiry Date: 2030-07-17T04:00:00Z
Registrar Registration Expiration Date:
Registrar: Network Solutions, LLC
Registrar IANA ID: 2
Registrar Abuse Contact Email: abuse@web.com
Registrar Abuse Contact Phone: +1.8003337680
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registrant Organization: Living on Earth
Registrant State/Province: MA
Registrant Country: US
Name Server: NS1.DREAMHOST.COM
Name Server: NS2.DREAMHOST.COM
Name Server: NS3.DREAMHOST.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/)
>>> Last update of WHOIS database: 2021-03-02T17:24:51Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.

Nameservers

Name IP Address
ns1.dreamhost.com 162.159.26.14
ns2.dreamhost.com 162.159.26.81
ns3.dreamhost.com 162.159.27.84
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
0/5
$173,840,433 USD 5/5
0/5
$14,825 USD 3/5
$3,179 USD 2/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