CREAM.ORG The Ice Planet

cream.org Website Information

Daily Unique Visits: 14,808

Daily Page Views: 88,848

Income Per Day: $178

Estimated Value: $128,160

This website is located in United Kingdom and is using following IP address 80.87.134.99. See the complete list of popular websites hosted in United Kingdom.

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

Website cream.org is using the following name servers:

  • dns0.positive-internet.com
  • dns1.positive-internet.com

and is probably hosted by The Positive Internet Company Ltd. See the full list of other websites hosted by The Positive Internet Company Ltd.

The highest website cream.org position in Alexa rank database was 90769 and the lowest rank position was 994222. Current position of cream.org in Alexa rank database is 96857.

Desktop speed score of cream.org (84/100) is better than the results of 78.07% of other sites and shows that the page is performing great on desktop computers.

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

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

Advertisement

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


cream.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: CREAM.ORG
Registry Domain ID: D2558794-LROR
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://www.tucows.com
Updated Date: 2021-05-12T14:18:09Z
Creation Date: 1998-02-22T05:00:00Z
Registry Expiry Date: 2029-02-21T05:00:00Z
Registrar Registration Expiration Date:
Registrar: Tucows Domains Inc.
Registrar IANA ID: 69
Registrar Abuse Contact Email: domainabuse@tucows.com
Registrar Abuse Contact Phone: +1.4165350123
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registrant Organization: The DairyNet Collective
Registrant State/Province:
Registrant Country: GB
Name Server: DNS0.POSITIVE-INTERNET.COM
Name Server: DNS1.POSITIVE-INTERNET.COM
DNSSEC: signedDelegation
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/)
>>> Last update of WHOIS database: 2022-02-12T14:25:11Z

cream.org server information

Servers Location

cream.org desktop page speed rank

Last tested: 2019-09-07


Desktop Speed Medium
84/100

cream.org Desktop Speed Test Quick Summary


priority - 9Enable 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 85.1KiB (66% reduction).

Compressing http://cream.org/ could save 82.3KiB (65% reduction).
Compressing http://cream.org/planet.css could save 2.8KiB (72% reduction).

priority - 4Optimize images

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

Optimize the following images to reduce their size by 38KiB (55% reduction).

Compressing and resizing http://cream.org/images/default-hackergotchi.png could save 25.1KiB (72% reduction).
Compressing http://pool.cream.org/offtopic/rum300.jpg could save 12.1KiB (43% reduction).
Compressing http://cream.org/images/planet.png could save 891B (17% reduction).

priority - 3Leverage 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://cream.org/images/background.gif (expiration not specified)
http://cream.org/images/default-hackergotchi.png (expiration not specified)
http://cream.org/images/mainice.jpg (expiration not specified)
http://cream.org/images/planet.png (expiration not specified)
http://cream.org/planet.css (expiration not specified)
http://pool.cream.org/offtopic/rum300.jpg (expiration not specified)

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

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

http://cream.org/planet.css

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 534B (14% reduction).

Minifying http://cream.org/planet.css could save 534B (14% reduction).

cream.org Desktop Resource Breakdown

Total Resources37
Number of Hosts4
Static Resources6
CSS Resources1

cream.org mobile page speed rank

Last tested: 2017-05-29


Mobile Speed Medium
76/100

cream.org Mobile Speed Test Quick Summary


priority - 12Leverage 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://cream.org/images/background.gif (expiration not specified)
http://cream.org/images/default-hackergotchi.png (expiration not specified)
http://cream.org/images/mainice.jpg (expiration not specified)
http://cream.org/images/planet.png (expiration not specified)
http://cream.org/planet.css (expiration not specified)
http://pool.cream.org/offtopic/rum300.jpg (expiration not specified)
https://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75525/ (expiration not specified)
https://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75529/ (expiration not specified)
https://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75532/ (expiration not specified)
https://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75535/ (expiration not specified)
https://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75538/ (expiration not specified)
https://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75541/ (expiration not specified)
https://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75544/ (expiration not specified)
https://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75595/ (expiration not specified)
https://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75598/ (expiration not specified)
https://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75601/ (expiration not specified)

priority - 9Enable 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 85KiB (66% reduction).

Compressing http://cream.org/ could save 82.2KiB (65% reduction).
Compressing http://cream.org/planet.css could save 2.8KiB (72% reduction).

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

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

http://cream.org/planet.css

priority - 1Optimize images

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

Optimize the following images to reduce their size by 12.9KiB (39% reduction).

Compressing http://pool.cream.org/offtopic/rum300.jpg could save 12.1KiB (43% reduction).
Compressing http://cream.org/images/planet.png could save 891B (17% 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 534B (14% reduction).

Minifying http://cream.org/planet.css could save 534B (14% reduction).

cream.org Mobile Resource Breakdown

Total Resources37
Number of Hosts4
Static Resources16
CSS Resources1

cream.org mobile page usability

Last tested: 2017-05-29


Mobile Usability Medium
65/100

cream.org Mobile Usability Test Quick Summary


priority - 40Use 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.

February 24, 2017 and 12 others render only 8 pixels tall (20 CSS pixels).

Mad Mel's Liquid Finale and 12 others render only 6 pixels tall (16 CSS pixels).

he result of d…and its allies and 118 others render only 5 pixels tall (13 CSS pixels).

<div style=…></content> and 367 others render only 5 pixels tall (13 CSS pixels).

by John Walker…2017 01:41 PM and 20 others render only 5 pixels tall (13 CSS pixels).

T and 2 others render only 5 pixels tall (13 CSS pixels).
Even in fabled…n engulfed it, and 13 others render only 5 pixels tall (13 CSS pixels).
th and 2 others render only 4 pixels tall (11 CSS pixels).
. renders only 5 pixels tall (13 CSS pixels).
Subscriptions renders only 5 pixels tall (12 CSS pixels).

The Great Nort…bie Apocalypse and 31 others render only 4 pixels tall (11 CSS pixels).

Last updated: renders only 4 pixels tall (11 CSS pixels).

April 11, 2017 05:29 AM and 1 others render only 4 pixels tall (11 CSS pixels).

All times are UTC. renders only 4 pixels tall (11 CSS pixels).

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 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="http://pubsubh…b.appspot.com/">Mad Mel&#39;s Liquid Finale</a> and 12 others are close to other tap targets.

The tap target <a href="http://wilkins…middleman.html">The Middleman</a> and 36 others are close to other tap targets.

The tap target <a href="https://nickco…xit-and-trump/">by Nick Cohen…2017 02:10 PM</a> and 7 others are close to other tap targets.
The tap target <a href="None">A Commonplace Book</a> and 33 others are close to other tap targets.

cream.org HTML validation

Errors

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

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

The “center” element is obsolete. Use CSS instead.

Line: 60 Column: 4 - 11
"..."> <p> <p><center><img s..." Line: 85 Column: 4 - 11
"..."> <p> <p><center><img s..." Line: 247 Column: 4 - 11
"..."> <p> <p><center><img s..." Line: 272 Column: 4 - 11
"..."> <p> <p><center><img s..." Line: 298 Column: 4 - 11
"..."> <p> <p><center><img s..." Line: 580 Column: 4 - 11
"..."> <p> <p><center><img s..." Line: 605 Column: 4 - 11
"..."> <p> <p><center><img s..." Line: 630 Column: 4 - 11
"..."> <p> <p><center><img s..." Line: 655 Column: 4 - 11
"..."> <p> <p><center><img s..." Line: 681 Column: 4 - 11
"..."> <p> <p><center><img s..."

No “p” element in scope but a “p” end tag seen.

Line: 60 Column: 81 - 84
"...></center></p> <p>In..." Line: 64 Column: 43 - 46
"... here:</p></p> <p cl..." Line: 85 Column: 81 - 84
"...></center></p> <p>In..." Line: 89 Column: 43 - 46
"... here:</p></p> <p cl..." Line: 132 Column: - 512
"......" Line: 159 Column: - 1651
"......" Line: 226 Column: - 390
"......" Line: 247 Column: 81 - 84
"...></center></p> <p>In..." Line: 251 Column: 43 - 46
"... here:</p></p> <p cl..." Line: 272 Column: 81 - 84
"...></center></p> <p>In..." Line: 277 Column: 43 - 46
"... here:</p></p> <p cl..." Line: 298 Column: 81 - 84
"...></center></p> <p>In..." Line: 302 Column: 43 - 46
"... here:</p></p> <p cl..." Line: 344 Column: - 721
"......" Line: 372 Column: - 602
"......" Line: 411 Column: - 383
"......" Line: 442 Column: - 842
"......" Line: 465 Column: - 766
"......" Line: 531 Column: - 401
"......" Line: 559 Column: - 844
"......" Line: 580 Column: 81 - 84
"...></center></p> <p>In..." Line: 584 Column: 43 - 46
"... here:</p></p> <p cl..." Line: 605 Column: 81 - 84
"...></center></p> <p>In..." Line: 609 Column: 43 - 46
"... here:</p></p> <p cl..." Line: 630 Column: 81 - 84
"...></center></p> <p>In..." Line: 634 Column: 43 - 46
"... here:</p></p> <p cl..." Line: 655 Column: 81 - 84
"...></center></p> <p>In..." Line: 660 Column: 43 - 46
"... here:</p></p> <p cl..." Line: 681 Column: 81 - 84
"...></center></p> <p>In..." Line: 685 Column: 43 - 46
"... here:</p></p> <p cl..."

Element “img” is missing required attribute “src”.

Line: 110 Column: 4 - 8
"..."> <p> <p><img></p> <..." Line: 143 Column: 4 - 8
"..."> <p> <p><img></p> <..." Line: 170 Column: 4 - 8
"..."> <p> <p><img></p> <..." Line: 208 Column: 843 - 847
"...rlatanism.<img></p> <..." Line: 355 Column: 4 - 8
"..."> <p> <p><img><br> S..." Line: 383 Column: 4 - 8
"..."> <p> <p><img></p> <..." Line: 422 Column: 4 - 8
"..."> <p> <p><img><br> <..." Line: 455 Column: 4 - 8
"...a></p> <p><img><br> T..." Line: 476 Column: 4 - 8
"..."> <p> <p><img></p> <..." Line: 542 Column: 4 - 8
"..."> <p> <p><img><br> <..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 110 Column: 4 - 8
"..."> <p> <p><img></p> <..." Line: 143 Column: 4 - 8
"..."> <p> <p><img></p> <..." Line: 170 Column: 4 - 8
"..."> <p> <p><img></p> <..." Line: 208 Column: 843 - 847
"...rlatanism.<img></p> <..." Line: 355 Column: 4 - 8
"..."> <p> <p><img><br> S..." Line: 383 Column: 4 - 8
"..."> <p> <p><img></p> <..." Line: 422 Column: 4 - 8
"..."> <p> <p><img><br> <..." Line: 455 Column: 4 - 8
"...a></p> <p><img><br> T..." Line: 476 Column: 4 - 8
"..."> <p> <p><img></p> <..." Line: 542 Column: 4 - 8
"..."> <p> <p><img><br> <..."

Warnings

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.

Line: 132 Column: 244 - 347
"...m/75601/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75601/"></a> <..." Line: 132 Column: 353 - 508
"...01/"></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=nickcohen.net&blog=6160337&post=75601&subd=nicholascohen&ref=&feed=1" width="1" height="1"></p> <p cla..." Line: 159 Column: 1383 - 1486
"...m/75598/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75598/"></a> <..." Line: 159 Column: 1492 - 1647
"...98/"></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=nickcohen.net&blog=6160337&post=75598&subd=nicholascohen&ref=&feed=1" width="1" height="1"></p> <p cla..." Line: 226 Column: 122 - 225
"...m/75595/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75595/"></a> <..." Line: 226 Column: 231 - 386
"...95/"></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=nickcohen.net&blog=6160337&post=75595&subd=nicholascohen&ref=&feed=1" width="1" height="1"></p> <p cla..." Line: 344 Column: 453 - 556
"...m/75544/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75544/"></a> <..." Line: 344 Column: 562 - 717
"...44/"></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=nickcohen.net&blog=6160337&post=75544&subd=nicholascohen&ref=&feed=1" width="1" height="1"></p> <p cla..." Line: 372 Column: 334 - 437
"...m/75541/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75541/"></a> <..." Line: 372 Column: 443 - 598
"...41/"></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=nickcohen.net&blog=6160337&post=75541&subd=nicholascohen&ref=&feed=1" width="1" height="1"></p> <p cla..." Line: 411 Column: 115 - 218
"...m/75538/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75538/"></a> <..." Line: 411 Column: 224 - 379
"...38/"></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=nickcohen.net&blog=6160337&post=75538&subd=nicholascohen&ref=&feed=1" width="1" height="1"></p> <p cla..." Line: 442 Column: 574 - 677
"...m/75535/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75535/"></a> <..." Line: 442 Column: 683 - 838
"...35/"></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=nickcohen.net&blog=6160337&post=75535&subd=nicholascohen&ref=&feed=1" width="1" height="1"></p> <p cla..." Line: 465 Column: 498 - 601
"...m/75532/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75532/"></a> <..." Line: 465 Column: 607 - 762
"...32/"></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=nickcohen.net&blog=6160337&post=75532&subd=nicholascohen&ref=&feed=1" width="1" height="1"></p> <p cla..." Line: 531 Column: 133 - 236
"...m/75529/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75529/"></a> <..." Line: 531 Column: 242 - 397
"...29/"></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=nickcohen.net&blog=6160337&post=75529&subd=nicholascohen&ref=&feed=1" width="1" height="1"></p> <p cla..." Line: 559 Column: 576 - 679
"...m/75525/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/nicholascohen.wordpress.com/75525/"></a> <..." Line: 559 Column: 685 - 840
"...25/"></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=nickcohen.net&blog=6160337&post=75525&subd=nicholascohen&ref=&feed=1" width="1" height="1"></p> <p cla..." Line: 693 Column: 33 - 80
"...ream.org"><img src="images/mainice.jpg" border="0" alt=""></a> ..." Line: 722 Column: 40 - 115
"...net.org/"><img src="images/planet.png" width="80" height="80" alt="Planet" border="0"></a> <..."

This document appears to be written in English. Consider adding “lang="en"” (or variant) to the “html” start tag.

Line: 2 Column: 103 - 6
"...oose.dtd"> <html> ..."

cream.org similar domains

Similar domains:
www.cream.com
www.cream.net
www.cream.org
www.cream.info
www.cream.biz
www.cream.us
www.cream.mobi
www.ream.org
www.cream.org
www.xream.org
www.cxream.org
www.xcream.org
www.dream.org
www.cdream.org
www.dcream.org
www.fream.org
www.cfream.org
www.fcream.org
www.vream.org
www.cvream.org
www.vcream.org
www.ceam.org
www.ceeam.org
www.creeam.org
www.ceream.org
www.cdeam.org
www.crdeam.org
www.cfeam.org
www.crfeam.org
www.cteam.org
www.crteam.org
www.ctream.org
www.cram.org
www.crwam.org
www.crewam.org
www.crweam.org
www.crsam.org
www.cresam.org
www.crseam.org
www.crdam.org
www.credam.org
www.crram.org
www.creram.org
www.crream.org
www.crem.org
www.creqm.org
www.creaqm.org
www.creqam.org
www.crewm.org
www.creawm.org
www.cresm.org
www.creasm.org
www.crezm.org
www.creazm.org
www.crezam.org
www.crea.org
www.crean.org
www.creamn.org
www.creanm.org
www.creaj.org
www.creamj.org
www.creajm.org
www.creak.org
www.creamk.org
www.creakm.org

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


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