ligo.org Website Information

Daily Unique Visits: 36,595

Daily Page Views: 219,570

Income Per Day: $439

Estimated Value: $316,080

ligo.org is registered under .ORG top-level domain. Please check other sites in .ORG zone.

No name server records were found.

and is probably hosted by CLOUDFLARESPECTRUM Cloudflare, Inc., GB. See the full list of other websites hosted by CLOUDFLARESPECTRUM Cloudflare, Inc., GB.

The highest website ligo.org position in Alexa rank database was 19320 and the lowest rank position was 997854. Current position of ligo.org in Alexa rank database is 39192.

Desktop speed score of ligo.org (77/100) is better than the results of 63.93% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of ligo.org (61/100) is better than the results of 5.47% of other sites and means that the page is not mobile-friendly.

Mobile speed score of ligo.org (58/100) is better than the results of 50.23% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

ligo.org Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.

ligo.org whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.

Domain Name: ligo.org
Registry Domain ID: b74d6731b3834726899303422e8f8a55-LROR
Registrar WHOIS Server: http://whois.domain.com
Registrar URL: http://www.domain.com
Updated Date: 2024-07-01T13:26:22Z
Creation Date: 2002-01-23T20:59:09Z
Registry Expiry Date: 2029-01-23T20:59:09Z
Registrar: Domain.com, LLC
Registrar IANA ID: 886
Registrar Abuse Contact Email: compliance@domain-inc.net
Registrar Abuse Contact Phone: +1.6022262389
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Domain Privacy Service FBO Registrant.
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: FL
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ligo.ligo.caltech.edu
Name Server: mercutio.ni.caltech.edu
Name Server: tepid.ni.caltech.edu
Name Server: ns1.ligo-la.caltech.edu
Name Server: ns1.ligo-wa.caltech.edu
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2024-11-13T02:20:27Z

ligo.org server information

Servers Location

ligo.org desktop page speed rank

Last tested: 2015-10-02

Desktop Speed Medium

77/100

ligo.org Desktop Speed Test Quick Summary

priority - 14Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://player.ooyala.com/iframe.js (expiration not specified)
http://www.ligo.org/css/master.css (expiration not specified)
http://www.ligo.org/images/action-corner-grad.png (expiration not specified)
http://www.ligo.org/images/bbc-radio-ligo.png (expiration not specified)
http://www.ligo.org/images/body-grad.png (expiration not specified)
http://www.ligo.org/images/findusonfacebook.jpeg (expiration not specified)
http://www.ligo.org/images/followusontwitter.jpeg (expiration not specified)
http://www.ligo.org/images/homepage-btn-involved.png (expiration not specified)
http://www.ligo.org/images/homepage-btn-learn.png (expiration not specified)
http://www.ligo.org/images/logo02.gif (expiration not specified)
http://www.ligo.org/images/main-feature-o1-start.png (expiration not specified)
http://www.ligo.org/images/navGrad.gif (expiration not specified)
http://www.ligo.org/images/reddit-teaser-half-size-narrow.png (expiration not specified)
http://www.ligo.org/images/video-teaser-ligo-generations.png (expiration not specified)
http://www.ligo.org/images/video-teaser-ligo-passion-half-size.png (expiration not specified)
http://www.ligo.org/js/rotating-images.js (expiration not specified)
https://analytics.ooyala.com/static/iframe_pinger.js (expiration not specified)
http://api.ooyala.com/v2/discover/similar/assets/R…OopeHPk_9UCCwP8t-LLQWn (60 seconds)
http://api.ooyala.com/v2/discover/similar/assets/g…OopeHPk_9UCCwP8t-LLQWn (60 seconds)
http://player.ooyala.com/player_api/v1/content_tre…UpOqERBzpmZCulyOp6dbu? (4.9 minutes)
http://player.ooyala.com/player_api/v1/metadata/em…opeHPk_9UCCwP8t-LLQWn& (4.9 minutes)
http://player.ooyala.com/player_api/v1/content_tre…wJbfeK2ZfvESRVR-h1pw-? (5 minutes)
http://player.ooyala.com/player_api/v1/metadata/em…opeHPk_9UCCwP8t-LLQWn& (5 minutes)
http://player.ooyala.com/v3/93dbd96f79fa407e8dc06e…latform=flash-priority (8.9 minutes)
http://player.ooyala.com/v3/91ac0f6dcbdf466c84659d…latform=flash-priority (9.9 minutes)
http://imasdk.googleapis.com/js/sdkloader/ima3.js (15 minutes)
http://s0.2mdn.net/instream/video/client.js (15 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-TR24NF (16.2 minutes)

priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://www.ligo.org/js/rotating-images.js

Use asynchronous versions of the following scripts:

http://w.sharethis.com/button/buttons.js

Optimize CSS Delivery of the following:

http://www.ligo.org/css/master.css
http://www.ligo.org/css/master.css

priority - 4Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 33.8KiB (76% reduction).

Compressing http://api.ooyala.com/v2/discover/similar/assets/g…OopeHPk_9UCCwP8t-LLQWn could save 26.6KiB (80% reduction).
Compressing https://analytics.ooyala.com/static/iframe_pinger.js could save 7.1KiB (63% reduction).

priority - 2Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 14.3KiB (4% reduction).

Losslessly compressing http://www.ligo.org/images/reddit-teaser-half-size-narrow.png could save 3.2KiB (12% reduction).
Losslessly compressing http://www.ligo.org/images/action-corner-grad.png could save 2.8KiB (75% reduction).
Losslessly compressing http://www.ligo.org/images/logo02.gif could save 1.2KiB (18% reduction).
Losslessly compressing http://www.ligo.org/images/homepage-btn-learn.png could save 1.1KiB (16% reduction).
Losslessly compressing http://ooyala.purch.com/gweGMyczqavUpOqERBzpmZCulyOp6dbu/promo246821214 could save 947B (1% reduction).
Losslessly compressing http://w.sharethis.com/images/sharethis_16.png could save 924B (80% reduction).
Losslessly compressing http://w.sharethis.com/images/twitter_16.png could save 847B (66% reduction).
Losslessly compressing http://w.sharethis.com/images/linkedin_16.png could save 822B (57% reduction).
Losslessly compressing http://w.sharethis.com/images/facebook_16.png could save 798B (60% reduction).
Losslessly compressing http://w.sharethis.com/images/googleplus_16.png could save 697B (45% reduction).
Losslessly compressing http://www.ligo.org/images/homepage-btn-involved.png could save 650B (11% reduction).
Losslessly compressing http://ooyala.purch.com/R0Y2R5cDrDzwJbfeK2ZfvESRVR-h1pw-/promo237103815 could save 538B (3% reduction).

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 3.7KiB (1% reduction).

Minifying http://player.ooyala.com/v3/91ac0f6dcbdf466c84659d…latform=flash-priority could save 1.6KiB (1% reduction) after compression.
Minifying http://player.ooyala.com/v3/93dbd96f79fa407e8dc06e…latform=flash-priority could save 1.6KiB (1% reduction) after compression.
Minifying http://player.ooyala.com/static/cacheable/19c8f887…fe168a4df8/reporter.js could save 556B (2% reduction) after compression.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 2.6KiB (3% reduction).

Minifying http://imasdk.googleapis.com/js/core/bridge3.108.1_en.html could save 1.1KiB (1% reduction) after compression.
Minifying http://ligo.org/ could save 1KiB (24% reduction) after compression.
Minifying http://edge.sharethis.com/share5x/index.3c401b929c…aced880852aeb0d98.html could save 533B (13% reduction) after compression.

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 522B (26% reduction).

Minifying http://www.ligo.org/css/master.css could save 522B (26% reduction) after compression.

ligo.org Desktop Resource Breakdown

Total Resources	75
Number of Hosts	24
Static Resources	42
JavaScript Resources	23
CSS Resources	2

ligo.org mobile page speed rank

Last tested: 2019-07-06

Mobile Speed Bad

58/100

ligo.org Mobile Speed Test Quick Summary

priority - 40Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://www.ligo.org/js/rotating-images.js

Use asynchronous versions of the following scripts:

https://w.sharethis.com/button/buttons.js

Optimize CSS Delivery of the following:

https://www.ligo.org/css/master.css
https://www.ligo.org/css/master.css

priority - 15Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://pd.sharethis.com/pd/test_oracle (expiration not specified)
https://ws.sharethis.com/button/css/buttons-secure.css (expiration not specified)
https://www.ligo.org/css/master.css (expiration not specified)
https://www.ligo.org/images/Instagram-logo48px.png (expiration not specified)
https://www.ligo.org/images/Twitter_Logo_White_On_Blue.png (expiration not specified)
https://www.ligo.org/images/YouTube_48px.png (expiration not specified)
https://www.ligo.org/images/action-corner-grad.png (expiration not specified)
https://www.ligo.org/images/body-grad.png (expiration not specified)
https://www.ligo.org/images/facebook_58.png (expiration not specified)
https://www.ligo.org/images/frontpg/LIGO_Orrery_v5…re_merger-edit2-sm.png (expiration not specified)
https://www.ligo.org/images/frontpg/gspyglitch3_mod.png (expiration not specified)
https://www.ligo.org/images/frontpg/magazine-read14.png (expiration not specified)
https://www.ligo.org/images/frontpg/scisummarygraphic_mod.png (expiration not specified)
https://www.ligo.org/images/logo02.gif (expiration not specified)
https://www.ligo.org/images/navGrad.gif (expiration not specified)
https://www.ligo.org/js/rotating-images.js (expiration not specified)
https://www.ligo.org/nobel_prize/Nobel-barish-thorne-weiss_edit.png (expiration not specified)
https://t.sharethis.com/1/d/t.dhj?rnd=156240388137…=c010&dmn=www.ligo.org (60 minutes)
https://translate.googleapis.com/translate_static/css/translateelement.css (60 minutes)
https://translate.googleapis.com/translate_static/js/element/main.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 14Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 135.2KiB (27% reduction).

Compressing https://www.ligo.org/images/frontpg/LIGO_Orrery_v5…re_merger-edit2-sm.png could save 68.2KiB (23% reduction).
Compressing https://www.ligo.org/images/frontpg/scisummarygraphic_mod.png could save 55.9KiB (30% reduction).
Compressing and resizing https://www.ligo.org/images/Twitter_Logo_White_On_Blue.png could save 4KiB (84% reduction).
Compressing https://www.ligo.org/images/action-corner-grad.png could save 2.9KiB (80% reduction).
Compressing https://www.ligo.org/images/Instagram-logo48px.png could save 1.4KiB (52% reduction).
Compressing https://www.ligo.org/images/facebook_58.png could save 989B (68% reduction).
Compressing https://www.ligo.org/images/YouTube_48px.png could save 807B (28% reduction).
Compressing https://translate.googleapis.com/translate_static/img/te_ctrl3.gif could save 591B (42% reduction).
Compressing https://www.ligo.org/images/body-grad.png could save 398B (50% reduction).

priority - 4Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 39.8KiB (77% reduction).

Compressing https://www.ligo.org/ could save 32.8KiB (78% reduction).
Compressing https://www.ligo.org/css/master.css could save 5.7KiB (72% reduction).
Compressing https://www.ligo.org/js/rotating-images.js could save 1.2KiB (69% reduction).
Compressing https://pd.sharethis.com/pd/test_oracle could save 127B (30% reduction).

priority - 2Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 20.4KiB (45% reduction).

Minifying https://www.ligo.org/ could save 19.9KiB (48% reduction).
Minifying https://ws.sharethis.com/secure5x/index.html could save 524B (13% reduction) after compression.

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 2.3KiB (30% reduction).

Minifying https://www.ligo.org/css/master.css could save 2.3KiB (30% reduction).

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 652B (31% reduction).

Minifying https://www.ligo.org/js/rotating-images.js could save 542B (32% reduction).
Minifying https://pd.sharethis.com/pd/test_oracle could save 110B (26% reduction).

ligo.org Mobile Resource Breakdown

Total Resources	65
Number of Hosts	25
Static Resources	32
JavaScript Resources	14
CSS Resources	3

ligo.org mobile page usability

Last tested: 2019-07-06

Mobile Usability Bad

61/100

ligo.org Mobile Usability Test Quick Summary

priority - 35Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Select Language renders only 5 pixels tall (13 CSS pixels).

▼ renders only 5 pixels tall (13 CSS pixels).

Our science explained and 7 others render only 5 pixels tall (13 CSS pixels).

Mar 31, 2019 and 10 others render only 5 pixels tall (13 CSS pixels).

LIGO and Virgo…observing runs and 18 others render only 5 pixels tall (13 CSS pixels).

Mar 26, 2019 and 7 others render only 5 pixels tall (13 CSS pixels).

funding acknowledgments and 4 others render only 4 pixels tall (10 CSS pixels).

Connect with us: renders only 5 pixels tall (12 CSS pixels).

priority - 15Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="news.php">News</a> and 7 others are close to other tap targets.

The tap target <a href="/news/index.php#O3NSMay19">LIGO and Virgo…Star Smash-Ups</a> and 33 others are close to other tap targets.

The tap target <a href="contact.php">contact information</a> and 3 others are close to other tap targets.

The tap target <a href="http://www.fac…cCollaboration"></a> and 1 others are close to other tap targets.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 6Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,030 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <span>Select Language</span> falls outside the viewport.
The element <img src="https://www.go…s/cleardot.gif"> falls outside the viewport.
The element <span></span> falls outside the viewport.
The element <img src="https://www.go…s/cleardot.gif"> falls outside the viewport.
The element <span>▼</span> falls outside the viewport.
The element <div id="hdrTier2"></div> falls outside the viewport.
The element <a href="https://www.ligo.caltech.edu/">LIGO Lab site</a> falls outside the viewport.
The element <div class="placeholder"> falls outside the viewport.
The element <div class="clear"> falls outside the viewport.
The element <img src="images/frontpg…raphic_mod.png" class="overlay"> falls outside the viewport.
The element <img src="./nobel_prize/…weiss_edit.png" class="overlay"> falls outside the viewport.
The element <div class="clear"> falls outside the viewport.
The element <div class="clear"> falls outside the viewport.
The element <a href="https://wiki.l…rg/LSC/WebHome" class="internal">LSC internal</a> falls outside the viewport.
The element <img src="images/Instagram-logo48px.png"> falls outside the viewport.

ligo.org HTML validation

Errors

Obsolete doctype. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 90
"...<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html..."

Bad value “description” for attribute “http-equiv” on element “meta”.

Line: 8 Column: 1 - 170
"...n</title> <meta http-equiv="description" content="LIGO Scientific Collaboration (LSC) seeks to detect gravitational waves and use them for exploration of fundamentals of science."> <meta..."

Bad value “keywords” for attribute “http-equiv” on element “meta”.

Line: 9 Column: 1 - 193
"...cience."> <meta http-equiv="keywords" content="LIGO, ligo, LSC, lsc, LIGO Scientific Collaboration, ligo collaboration, gravitational waves, gravity waves, gravitational wave astronomy, gravity physics"> <link..."

Bad value “950px” for attribute “width” on element “img”: Expected a digit but saw “p” instead.

Line: 94 Column: 35 - 218
"...0817.php"><img src="images/GW170817_images/GW170817-frontpg.png" alt="LIGO, Virgo, and partners make first detection of gravitational waves and light from colliding neutron stars" width="950px"></a> ..."

The “width” attribute on the “table” element is obsolete. Use CSS instead.

Line: 147 Column: 1 - 139
"...verflow"> <table width="100%" cellspacing="0" summary="This table lists LSC news, starting with the latest. Table is used for layout purposes only."> <tr>..."

The “cellspacing” attribute on the “table” element is obsolete. Use CSS instead.

Line: 147 Column: 1 - 139
"...verflow"> <table width="100%" cellspacing="0" summary="This table lists LSC news, starting with the latest. Table is used for layout purposes only."> <tr>..."

The “summary” attribute on the “table” element is obsolete. Consider describing the structure of the “table” in a “caption” element or in a “figure” element containing the “table”; or, simplify the structure of the “table” so that no description is needed.

Line: 147 Column: 1 - 139
"...verflow"> <table width="100%" cellspacing="0" summary="This table lists LSC news, starting with the latest. Table is used for layout purposes only."> <tr>..."

The “valign” attribute on the “td” element is obsolete. Use CSS instead.

Line: 150 Column: 5 - 50
"...y."> <tr> <td class="date" valign="top" title="Apr 24 2018">Apr 24..." Line: 151 Column: 68 - 30
"... 2018</td> <td class="text" valign="top"> <a h..." Line: 156 Column: 5 - 50
".../tr> <tr> <td class="date" valign="top" title="Mar 21 2018">Mar 21..." Line: 157 Column: 68 - 30
"... 2018</td> <td class="text" valign="top"> <a h..." Line: 162 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Nov 15, 2017">Nov 15..." Line: 163 Column: 69 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 168 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Oct 16, 2017">Oct 16..." Line: 169 Column: 69 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 174 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Oct 11, 2017">Oct 11..." Line: 175 Column: 69 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 180 Column: 5 - 50
".../tr> <tr> <td class="date" valign="top" title="Oct 3, 2017">Oct 3,..." Line: 181 Column: 67 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 187 Column: 5 - 51
"...tr> <tr> <td class="date" valign="top" title="Sep 27, 2017">Sep 27..." Line: 188 Column: 69 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 193 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Aug 30, 2017">Aug 30..." Line: 194 Column: 69 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 199 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Aug 25, 2017">Aug 25..." Line: 200 Column: 69 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 205 Column: 5 - 50
".../tr> <tr> <td class="date" valign="top" title="Aug 1, 2017">Aug 1,..." Line: 206 Column: 67 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 211 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Jul 20, 2017">Jul 20..." Line: 212 Column: 69 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 217 Column: 5 - 50
".../tr> <tr> <td class="date" valign="top" title="Jul 7, 2017">Jul 7,..." Line: 218 Column: 67 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 223 Column: 5 - 50
".../tr> <tr> <td class="date" valign="top" title="Jun 1, 2017">Jun 16..." Line: 224 Column: 68 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 229 Column: 5 - 50
".../tr> <tr> <td class="date" valign="top" title="Jun 1, 2017">Jun 1,..." Line: 230 Column: 67 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 235 Column: 5 - 50
".../tr> <tr> <td class="date" valign="top" title="Mar 9, 2017">Mar 29..." Line: 236 Column: 68 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 242 Column: 5 - 51
"...tr> <tr> <td class="date" valign="top" title="Mar 15, 2017">Mar 15..." Line: 243 Column: 69 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 248 Column: 5 - 50
".../tr> <tr> <td class="date" valign="top" title="Mar 9, 2017">Mar 9,..." Line: 249 Column: 67 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 262 Column: 5 - 62
"... --> <tr> <td class="date" valign="top" width="30%" title="Feb 3, 2017">Feb 3,..." Line: 263 Column: 79 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 276 Column: 5 - 51
"... --> <tr> <td class="date" valign="top" title="Jan 27, 2017">Jan 27..." Line: 277 Column: 69 - 30
"... 2017</td> <td class="text" valign="top"> <a h..." Line: 282 Column: 5 - 63
".../tr> <tr> <td class="date" valign="top" width="30%" title="Jan 26, 2017">Jan 26..." Line: 283 Column: 81 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 289 Column: 5 - 63
"...tr> <tr> <td class="date" valign="top" width="30%" title="Dec 13, 2016">Dec 13..." Line: 290 Column: 81 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 295 Column: 5 - 50
".../tr> <tr> <td class="date" valign="top" title="Dec 3, 2016">Dec 3,..." Line: 296 Column: 67 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 301 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Nov 30, 2016">Nov 30..." Line: 302 Column: 69 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 307 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Nov 29, 2016">Nov 29..." Line: 308 Column: 69 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 313 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Oct 12, 2016">Oct 12..." Line: 314 Column: 69 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 319 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Sep 14, 2016">Sep 14..." Line: 320 Column: 69 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 325 Column: 5 - 50
".../tr> <tr> <td class="date" valign="top" title="Sep 7, 2016">Sep 7,..." Line: 326 Column: 67 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 331 Column: 5 - 50
".../tr> <tr> <td class="date" valign="top" title="Sep 6, 2016">Sep 6,..." Line: 332 Column: 67 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 337 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Jun 21, 2016">Jun 21..." Line: 338 Column: 69 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 343 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Jun 15, 2016">Jun 15..." Line: 344 Column: 69 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 357 Column: 5 - 50
"... --> <tr> <td class="date" valign="top" title="Jun 2, 2016">Jun 2,..." Line: 358 Column: 67 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 362 Column: 5 - 51
"...</tr> <tr> <td class="date" valign="top" title="May 31, 2016">May 31..." Line: 363 Column: 69 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 368 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="May 16, 2016">May 16..." Line: 369 Column: 69 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 374 Column: 5 - 50
".../tr> <tr> <td class="date" valign="top" title="May 4, 2016">May 4,..." Line: 375 Column: 67 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 380 Column: 5 - 50
".../tr> <tr> <td class="date" valign="top" title="May 2, 2016">May 2,..." Line: 381 Column: 67 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 386 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Apr 20, 2016">Apr 20..." Line: 387 Column: 69 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 392 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Mar 31, 2016">Mar 31..." Line: 393 Column: 69 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 398 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Feb 24, 2016">Feb 24..." Line: 399 Column: 69 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 404 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Feb 17, 2016">Feb 17..." Line: 405 Column: 69 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 410 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Feb 12, 2016">Feb 12..." Line: 411 Column: 69 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 416 Column: 5 - 51
".../tr> <tr> <td class="date" valign="top" title="Feb 11, 2016">Feb 11..." Line: 417 Column: 69 - 30
"... 2016</td> <td class="text" valign="top"> <a h..." Line: 429 Column: 5 - 30
".../tr> <tr> <td class="date" valign="top"> ..." Line: 430 Column: 42 - 30
"...nbsp;</td> <td class="text" valign="top"> See <..."

The “width” attribute on the “td” element is obsolete. Use CSS instead.

Line: 262 Column: 5 - 62
"... --> <tr> <td class="date" valign="top" width="30%" title="Feb 3, 2017">Feb 3,..." Line: 282 Column: 5 - 63
".../tr> <tr> <td class="date" valign="top" width="30%" title="Jan 26, 2017">Jan 26..." Line: 289 Column: 5 - 63
"...tr> <tr> <td class="date" valign="top" width="30%" title="Dec 13, 2016">Dec 13..."

Bad value “320px” for attribute “width” on element “img”: Expected a digit but saw “p” instead.

Line: 636 Column: 37 - 157
"...agazine/"><img src="images/frontpg/magazine-read12.png" alt="Read the latest issue of LIGO Magazine" class="overlay" width="320px"></a> ..."

No space between attributes.

Line: 662 Column: - 192
"...class="overlay"width="330px"><..."

Bad value “330px” for attribute “width” on element “img”: Expected a digit but saw “p” instead.

Line: 662 Column: 70 - 205
"...vity-spy"><img src="images/frontpg/gspyglitch3_mod.png" alt="Gravity Spy: Help classify noise glitches in LIGO data" class="overlay"width="330px"></a><b..." Line: 663 Column: 42 - 209
"...ome.org/"><img src="images/frontpg/screensaver_milkyway_mod.png" alt="Einstein@home: search for gravitational waves and pulsars with your computer" class="overlay" width="330px"></a> <..."

Bad value “340px” for attribute “width” on element “img”: Expected a digit but saw “p” instead.

Line: 726 Column: 33 - 170
"...hp#nobel"><img src="./nobel_prize/Nobel-barish-thorne-weiss_edit.png" alt="Weiss, Barish, Thorne win the Nobel Prize" class="overlay" width="340px"></a> <..." Line: 732 Column: 33 - 163
"...each.php"><img src="images/frontpg/scisummarygraphic_mod.png" alt="Read Science Summaries of our publications" class="overlay" width="340px"></a> <..."

Stray end tag “div”.

Line: 830 Column: 1 - 6
"...ainer--> </div><!--/w..."

Warnings

The document is not mappable to XML 1.0 due to two consecutive hyphens in a comment.

Line: 469 Column: - 80
"...ves' hangout -- how and why we..."

ligo.org similar domains

Similar domains:

www.ligo.com
www.ligo.net
www.ligo.org
www.ligo.info
www.ligo.biz
www.ligo.us
www.ligo.mobi
www.igo.org
www.ligo.org
www.pigo.org
www.lpigo.org
www.pligo.org
www.oigo.org
www.loigo.org
www.oligo.org
www.kigo.org
www.lkigo.org
www.kligo.org
www.lgo.org
www.lugo.org
www.liugo.org
www.luigo.org
www.ljgo.org
www.lijgo.org
www.ljigo.org
www.lkgo.org
www.likgo.org
www.logo.org
www.liogo.org
www.lio.org
www.lifo.org
www.ligfo.org
www.lifgo.org
www.livo.org
www.ligvo.org
www.livgo.org
www.lito.org
www.ligto.org
www.litgo.org
www.libo.org
www.ligbo.org
www.libgo.org
www.liyo.org
www.ligyo.org
www.liygo.org
www.liho.org
www.ligho.org
www.lihgo.org
www.lig.org
www.ligi.org
www.ligoi.org
www.ligio.org
www.ligk.org
www.ligok.org
www.ligko.org
www.ligl.org
www.ligol.org
www.liglo.org
www.ligp.org
www.ligop.org
www.ligpo.org

ligo.org Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.

ligo.org TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.

LIGO.ORG LSC - LIGO Scientific Collaboration

ligo.org Website Information

Advertisement

ligo.org Alexa Rank

ligo.org whois

ligo.org server information

Servers Location

ligo.org desktop page speed rank

ligo.org Desktop Speed Test Quick Summary

priority - 14Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Use asynchronous versions of the following scripts:

Optimize CSS Delivery of the following:

priority - 4Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 33.8KiB (76% reduction).

priority - 2Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 14.3KiB (4% reduction).

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 3.7KiB (1% reduction).

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 2.6KiB (3% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 522B (26% reduction).

ligo.org Desktop Resource Breakdown

ligo.org mobile page speed rank

ligo.org Mobile Speed Test Quick Summary

priority - 40Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Use asynchronous versions of the following scripts:

Optimize CSS Delivery of the following:

priority - 15Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 14Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 135.2KiB (27% reduction).

priority - 4Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 39.8KiB (77% reduction).

priority - 2Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 20.4KiB (45% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 2.3KiB (30% reduction).

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 652B (31% reduction).

ligo.org Mobile Resource Breakdown

ligo.org mobile page usability

ligo.org Mobile Usability Test Quick Summary

priority - 35Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

priority - 15Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 6Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,030 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

ligo.org HTML validation

Errors

Obsolete doctype. Expected “<!DOCTYPE html>”.

Bad value “description” for attribute “http-equiv” on element “meta”.

Bad value “keywords” for attribute “http-equiv” on element “meta”.

Bad value “950px” for attribute “width” on element “img”: Expected a digit but saw “p” instead.

The “width” attribute on the “table” element is obsolete. Use CSS instead.

The “cellspacing” attribute on the “table” element is obsolete. Use CSS instead.