domstat.net

Website loading time

during the test: 1.03 s

cable connection (average): 1.16 s

DSL connection (average): 1.3 s

modem (average): 8.42 s

HTTP headers

HTTP/1.0 301 Moved Permanently

Connection: close

Date: Tue, 18 Oct 2011 06:57:44 GMT

Server: Cherokee/1.2

Location: http://www.alobbs.com/

Content-Length: 352

Content-Type: text/html

HTTP/1.0 200 OK

Connection: close

Date: Tue, 18 Oct 2011 06:57:44 GMT

Server: Cherokee/1.2

Content-Type: text/html

Information about DNS servers

Received from the first DNS server

Request to the server "alobbs.com"
You used the following DNS server:
DNS Name: ns3.cdmon.net
DNS Server Address: 95.211.8.207#53
DNS server aliases:

HEADER opcode: REQUEST, status: NOERROR, id: 19571
flag: qr aa rd REQUEST: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 3

REQUEST SECTION:
alobbs.com. IN ANY

ANSWER SECTION:
alobbs.com. 2560 IN SOA ns1.cdmon.net. hostmaster.alobbs.com. 1279094450 10000 3600 604800 21600
alobbs.com. 21600 IN NS ns1.cdmon.net.
alobbs.com. 21600 IN NS ns2.cdmon.net.
alobbs.com. 21600 IN NS ns3.cdmon.net.
alobbs.com. 900 IN TXT "v=spf1 a mx mx:lists.octality.com include:aspmx.googlemail.com ptr:cdmon.com ~all"
alobbs.com. 900 IN MX 10 ASPMX.L.GOOGLE.com.
alobbs.com. 900 IN MX 30 ASPMX3.GOOGLEMAIL.com.
alobbs.com. 900 IN MX 30 ASPMX2.GOOGLEMAIL.com.
alobbs.com. 900 IN MX 20 ALT1.ASPMX.L.GOOGLE.com.
alobbs.com. 900 IN MX 20 ALT2.ASPMX.L.GOOGLE.com.
alobbs.com. 900 IN MX 30 ASPMX4.GOOGLEMAIL.com.
alobbs.com. 900 IN MX 30 ASPMX5.GOOGLEMAIL.com.
alobbs.com. 900 IN A 91.121.104.184

SECTION NOTES:
ns1.cdmon.net. 86400 IN A 212.36.74.129
ns2.cdmon.net. 86400 IN A 212.36.75.129
ns3.cdmon.net. 86400 IN A 95.211.8.207

Received 472 bytes from address 95.211.8.207#53 in 82 ms

Received from the second DNS server

Request to the server "alobbs.com"
You used the following DNS server:
DNS Name: ns1.cdmon.net
DNS Server Address: 212.36.74.129#53
DNS server aliases:

HEADER opcode: REQUEST, status: NOERROR, id: 55380
flag: qr aa rd REQUEST: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 3

REQUEST SECTION:
alobbs.com. IN ANY

ANSWER SECTION:
alobbs.com. 2560 IN SOA ns1.cdmon.net. hostmaster.alobbs.com. 1279094450 10000 3600 604800 21600
alobbs.com. 21600 IN NS ns1.cdmon.net.
alobbs.com. 21600 IN NS ns2.cdmon.net.
alobbs.com. 21600 IN NS ns3.cdmon.net.
alobbs.com. 900 IN TXT "v=spf1 a mx mx:lists.octality.com include:aspmx.googlemail.com ptr:cdmon.com ~all"
alobbs.com. 900 IN MX 10 ASPMX.L.GOOGLE.com.
alobbs.com. 900 IN MX 30 ASPMX3.GOOGLEMAIL.com.
alobbs.com. 900 IN MX 30 ASPMX2.GOOGLEMAIL.com.
alobbs.com. 900 IN MX 20 ALT1.ASPMX.L.GOOGLE.com.
alobbs.com. 900 IN MX 20 ALT2.ASPMX.L.GOOGLE.com.
alobbs.com. 900 IN MX 30 ASPMX4.GOOGLEMAIL.com.
alobbs.com. 900 IN MX 30 ASPMX5.GOOGLEMAIL.com.
alobbs.com. 900 IN A 91.121.104.184

SECTION NOTES:
ns1.cdmon.net. 86400 IN A 212.36.74.129
ns2.cdmon.net. 86400 IN A 212.36.75.129
ns3.cdmon.net. 86400 IN A 95.211.8.207

Received 472 bytes from address 212.36.74.129#53 in 102 ms

Subdomains (the first 50)

Typos (misspells)

Location

IP: 91.121.104.184

continent: EU, country: France (FRA), city:

Website value

rank in the traffic statistics:

There is not enough data to estimate website value.

Basic information

website build using CSS

code weight: 51.74 KB

text per all code ratio: 66 %

title: News | Alvaro's web site

description:

keywords:

encoding: utf-8

language: en

Website code analysis

one word phrases repeated minimum three times

two word phrases repeated minimum three times

three word phrases repeated minimum three times

B tags

U tags

How to Enable Front-Line Cache

Click vServer on Top menu Select the Virtual Server Behavior tab Click Rule Management Click on the "+" button to add new rules Select the Tasks section Select the Content Caching wizard The wizard provides two configuration options that cover most of the use cases of the cache mechanism: Store Cacheable Dynamic Responses: This option will cache all the responses that are explicitly subject to be stored in a cache. That is, responses including the Cache-Control or Expires headers. If you are trying to speeding up a Web application this is the way to go. Store Encoded Responses from Static files: Cherokee will store a copy of the encoded (GZip or Deflate) version of static files, so when they are subsequently requested, the server does not need to compress it again. Additionally, the wizard allows you to configure an administrative interface from which entries in the cache can be purged remotely. We have implemented a PURGE interface, for the sake of consistency with other Proxy-cache projects. Manual: It's also possible to enable the Cache capabilities of Cherokee in finer-grain, per-rule way. Starting in Cherokee 1.2.98 a new "Caching" tab has been incorporated to the Rule management interface. It allows you to define whether or not the content may be cached, and which responses are subject to this process. The Responses to Cache option is specially relevant in the section. It defines if the explicitly cacheable responses are the only responses that can be cached, or if the server should apply a much more aggressive caching policy by storing all the responses except the ones that are explicitly forbidden to cache. There are a few reasons why a response is considered to be non-cacheable: The object was requested over HTTPS The object required authentication The headers of the response forbids its caching. Either of the following header would forbid caching: Control-Cache, with a "no-cache", "no-store", "must-revalidate" or "proxy-revalidate" properties Expires: with a time in the past Pragma: with a "no-cache" value The headers of the response sets a cookie for the client (Cherokee allows you to ignore certain cookies, so they are not taken into account while evaluating the cacheability of a response. This provides an override where content where cookie(s) exist can be made cacheable) How to Test That Front-Line Cache is Working

Further Debugging

I tags

images

headers

H1

News | alo's web site

H2

Exciting times

Front-Line Cache Configuration

Cherokee 1.2.98, New Features

Front-Line Cache

An improved distribution model for Web Apps

Linux Format benchmarks Cherokee

Cherokee Market: The 1st marketplace for Web Apps

Streaming WebM (VP8) One Day Later

Cherokee Summit Big Success

Collaboration Summit & Cherokee Summit

H3

Exciting times

Front-Line Cache Configuration

Cherokee 1.2.98, New Features

Front-Line Cache

An improved distribution model for Web Apps

Linux Format benchmarks Cherokee

Cherokee Market: The 1st marketplace for Web Apps

Streaming WebM (VP8) One Day Later

Cherokee Summit Big Success

Collaboration Summit & Cherokee Summit

H4

H5

H6

internal links

external links