www.prayforjapan.jp analysis, site info, backlinks and seo
www.prayforjapan.jp - pray for japan 東北太平洋沖地震、海外からの応援メッセージ集 prayforjapan.jp
www.prayforjapan.jp scores a 3,1 out of 10 on our optimalisation scale. This is a little below average. We have identified 16 keywords. This page seems optimized for the keyword 'instagramh'
summary
This is the summary of our www.prayforjapan.jp analysis. Please check for detailed info under their tabs.
| Site | www.prayforjapan.jp (visit site) |
| Page Title | pray for japan 東北太平洋沖地震、海外からの応援メッセージ集 prayforjapan.jp |
| Keyword density | aufffd badgeplz brclr brds com facebook iframe incls instagramh like mocchicc none pbclr prayforjapan svc top |
| SEO Summary | 0% meta description relevance, 20% link relevance, 0% heading relevance, 147 page errors |
| Server info | Location: ,Japan |
No backlinks were found for this domain or backlink search was skipped
Content & Html
Analyzed html, text, tags, links, headings, keywords and more
We found 147 html errors and warings !
>> Read More !
SEO score of www.prayforjapan.jp
3,1
>> Read More !
www.prayforjapan.jp navigation and internal link structure
We have scanned www.prayforjapan.jp for internal links and found links on this page. We found 0 base folders and 1 folders on this site. Easy to follow navigation helps your visitors navigate through your website efficiently and improves the website experience. It is even more important for seach engines while it helps them spider your website and find the most important content.
We did not find an easy to follow navigation structure on www.prayforjapan.jp. Consider improving navigation on this page.
No internal links were found for this www.prayforjapan.jp. r-domain advises to create an easy to follow link structure.
www.prayforjapan.jp html info
HTML stands for Hypertext Markup Language, a standardized system for tagging text files to achieve font, color, graphic, and hyperlink effects on World Wide Web pages.
Html / text ratio
Try to keep your html as short as possible. Html only describes your content. There is no benefit in having a page with lots of html tags. A bloated page will slow down your site and harm user experience.
The html ratio of this page is 6,07
Page Errors
Html errors at best slow down your website (since a browser has to guess at the meaning) and in worst case render your page unviewable. Therefor make shure there are no html errors on your page !
line 10 column 26 - Warning: replacing invalid character code 140
line 10 column 27 - Warning: replacing invalid character code 151
line 10 column 36 - Warning: replacing invalid character code 139
line 10 column 39 - Warning: replacing invalid character code 150
line 10 column 41 - Warning: replacing invalid character code 156
line 10 column 44 - Warning: replacing invalid character code 156
line 10 column 45 - Warning: replacing invalid character code 135
line 10 column 47 - Warning: replacing invalid character code 128
line 10 column 48 - Warning: discarding invalid character code 129
line 10 column 53 - Warning: replacing invalid character code 150
line 10 column 55 - Warning: discarding invalid character code 129
line 10 column 55 - Warning: replacing invalid character code 139
line 10 column 57 - Warning: replacing invalid character code 130
line 10 column 58 - Warning: replacing invalid character code 137
line 10 column 60 - Warning: discarding invalid character code 129
line 10 column 63 - Warning: replacing invalid character code 156
line 10 column 65 - Warning: discarding invalid character code 143
line 10 column 67 - Warning: replacing invalid character code 131
line 10 column 70 - Warning: replacing invalid character code 131
line 10 column 71 - Warning: replacing invalid character code 131
line 10 column 73 - Warning: replacing invalid character code 130
line 10 column 76 - Warning: replacing invalid character code 131
line 10 column 79 - Warning: replacing invalid character code 130
line 10 column 82 - Warning: replacing invalid character code 155
line 10 column 83 - Warning: replacing invalid character code 134
line 43 column 101 - Warning: <img> element not empty or not closed
line 49 column 171 - Warning: discarding invalid character code 129
line 49 column 171 - Warning: replacing invalid character code 147
line 49 column 173 - Warning: discarding invalid character code 129
line 49 column 175 - Warning: replacing invalid character code 130
line 49 column 178 - Warning: replacing invalid character code 131
line 49 column 181 - Warning: replacing invalid character code 131
line 49 column 182 - Warning: replacing invalid character code 136
line 49 column 184 - Warning: replacing invalid character code 131
line 49 column 187 - Warning: replacing invalid character code 131
line 49 column 190 - Warning: replacing invalid character code 130
line 49 column 191 - Warning: replacing invalid character code 146
line 49 column 193 - Warning: discarding invalid character code 129
line 49 column 195 - Warning: discarding invalid character code 129
line 49 column 197 - Warning: discarding invalid character code 129
line 49 column 199 - Warning: replacing invalid character code 131
line 49 column 200 - Warning: replacing invalid character code 150
line 49 column 202 - Warning: replacing invalid character code 131
line 49 column 203 - Warning: replacing invalid character code 131
line 49 column 205 - Warning: replacing invalid character code 130
line 49 column 208 - Warning: replacing invalid character code 131
line 49 column 209 - Warning: replacing invalid character code 158
line 49 column 211 - Warning: replacing invalid character code 131
line 49 column 214 - Warning: replacing invalid character code 130
line 49 column 217 - Warning: discarding invalid character code 129
line 49 column 222 - Warning: replacing invalid character code 138
line 49 column 302 - Warning: discarding invalid character code 129
line 49 column 302 - Warning: replacing invalid character code 147
line 49 column 304 - Warning: discarding invalid character code 129
line 49 column 306 - Warning: replacing invalid character code 130
line 49 column 309 - Warning: replacing invalid character code 131
line 49 column 312 - Warning: replacing invalid character code 131
line 49 column 313 - Warning: replacing invalid character code 136
line 49 column 315 - Warning: replacing invalid character code 131
line 49 column 318 - Warning: replacing invalid character code 131
line 49 column 321 - Warning: replacing invalid character code 130
line 49 column 322 - Warning: replacing invalid character code 146
line 49 column 324 - Warning: discarding invalid character code 129
line 49 column 326 - Warning: discarding invalid character code 129
line 49 column 328 - Warning: discarding invalid character code 129
line 49 column 330 - Warning: replacing invalid character code 131
line 49 column 331 - Warning: replacing invalid character code 150
line 49 column 333 - Warning: replacing invalid character code 131
line 49 column 334 - Warning: replacing invalid character code 131
line 49 column 336 - Warning: replacing invalid character code 130
line 49 column 339 - Warning: replacing invalid character code 131
line 49 column 340 - Warning: replacing invalid character code 158
line 49 column 342 - Warning: replacing invalid character code 131
line 49 column 345 - Warning: replacing invalid character code 130
line 49 column 348 - Warning: discarding invalid character code 129
line 49 column 353 - Warning: replacing invalid character code 138
line 53 column 70 - Warning: replacing invalid character code 131
line 53 column 72 - Warning: discarding invalid character code 129
line 53 column 75 - Warning: replacing invalid character code 139
line 53 column 77 - Warning: replacing invalid character code 130
line 53 column 78 - Warning: replacing invalid character code 139
line 53 column 80 - Warning: discarding invalid character code 129
line 53 column 82 - Warning: discarding invalid character code 129
line 53 column 84 - Warning: replacing invalid character code 130
line 53 column 85 - Warning: replacing invalid character code 132
line 53 column 87 - Warning: discarding invalid character code 129
line 53 column 87 - Warning: discarding invalid character code 141
line 53 column 164 - Warning: replacing invalid character code 128
line 53 column 165 - Warning: replacing invalid character code 128
line 53 column 213 - Warning: <img> element not empty or not closed
line 53 column 291 - Warning: <img> element not empty or not closed
line 57 column 57 - Warning: <img> element not empty or not closed
line 61 column 57 - Warning: replacing invalid character code 128
line 61 column 58 - Warning: replacing invalid character code 128
line 62 column 60 - Warning: unescaped & or unknown entity "&t"
line 62 column 64 - Warning: unescaped & or unknown entity "&brclr"
line 62 column 77 - Warning: unescaped & or unknown entity "&bgclr"
line 62 column 84 - Warning: unescaped & or unknown entity "&px"
line 62 column 89 - Warning: unescaped & or unknown entity "&py"
line 62 column 94 - Warning: unescaped & or unknown entity "&pb"
line 62 column 99 - Warning: unescaped & or unknown entity "&brds"
line 62 column 106 - Warning: unescaped & or unknown entity "&incls"
line 62 column 114 - Warning: unescaped & or unknown entity "&svc"
line 62 column 129 - Warning: unescaped & or unknown entity "&pbclr"
line 61 column 77 - Warning: <br> element not empty or not closed
line 105 column 211 - Warning: discarding invalid character code 129
line 105 column 213 - Warning: discarding invalid character code 129
line 105 column 215 - Warning: discarding invalid character code 129
line 105 column 217 - Warning: discarding invalid character code 129
line 105 column 217 - Warning: replacing invalid character code 155
line 105 column 219 - Warning: discarding invalid character code 129
line 105 column 221 - Warning: discarding invalid character code 129
line 105 column 221 - Warning: replacing invalid character code 134
line 105 column 223 - Warning: discarding invalid character code 129
line 105 column 225 - Warning: discarding invalid character code 129
line 105 column 227 - Warning: discarding invalid character code 129
line 115 column 73 - Warning: <img> element not empty or not closed
line 116 column 68 - Warning: unescaped & or unknown entity "&t"
line 116 column 72 - Warning: unescaped & or unknown entity "&bgclr"
line 116 column 83 - Warning: unescaped & or unknown entity "&brclr"
line 116 column 96 - Warning: unescaped & or unknown entity "&px"
line 116 column 101 - Warning: unescaped & or unknown entity "&py"
line 116 column 106 - Warning: unescaped & or unknown entity "&pb"
line 116 column 111 - Warning: unescaped & or unknown entity "&brds"
line 116 column 118 - Warning: unescaped & or unknown entity "&incls"
line 116 column 126 - Warning: unescaped & or unknown entity "&svc"
line 116 column 141 - Warning: unescaped & or unknown entity "&pbclr"
line 43 column 101 - Warning: <img> lacks "alt" attribute
line 49 column 1 - Warning: <a> proprietary attribute "data-hatena-bookmark-title"
line 49 column 1 - Warning: <a> proprietary attribute "data-hatena-bookmark-layout"
line 49 column 408 - Warning: <script> proprietary attribute "async"
line 50 column 1 - Warning: <a> proprietary attribute "data-text"
line 50 column 1 - Warning: <a> proprietary attribute "data-count"
line 50 column 1 - Warning: <a> proprietary attribute "data-via"
line 50 column 1 - Warning: <a> proprietary attribute "data-related"
line 52 column 1 - Warning: <iframe> proprietary attribute "allowtransparency"
line 53 column 213 - Warning: <img> lacks "alt" attribute
line 53 column 291 - Warning: <img> lacks "alt" attribute
line 57 column 57 - Warning: <img> lacks "alt" attribute
line 62 column 1 - Warning: <iframe> proprietary attribute "allowtransparency"
line 66 column 1 - Warning: <script> inserting "type" attribute
line 67 column 1 - Warning: <script> inserting "type" attribute
line 115 column 73 - Warning: <img> lacks "alt" attribute
line 116 column 9 - Warning: <iframe> proprietary attribute "allowtransparency"
line 118 column 1 - Warning: <script> inserting "type" attribute
line 119 column 1 - Warning: <script> inserting "type" attribute
Info: Document content looks like XHTML 1.0 Transitional
147 warnings, 0 errors were found!
Repair broken html
r-domain lets you repair the broken html. Click on the button below to let r-domain fetch your page and show the repaired output. Copy the output to your site and test it there !
www.prayforjapan.jp server info
A good server setup can make a huge difference for website performance and may even enhance the ratings in the search engine results since page speed has become an issue.
Http request info
| 'HTTP response code | 200 |
| Download time | 1,335824 seconds |
| Filesize | 5873 bytes |
Server headers
Server headers are the response the server sends before the actual content. A correct server setup can speed up a site and free up server resources. Make sure that all headers are set correct. For example dont cache dynamic content and dont close connections unless there is a good reason.
| HTTP/1.1 200 OK | |
| Date: Sat, 26 May 2012 05:17:41 GMT | The Date header represents the time when the message was generated, regardless of caching that happened since. It is used by caches as input to expiration calculations, and to detect clock drift. |
| Server: Apache | The Server header contains information about the software used by the origin server to handle the request. The server used here is Apache |
| Last-Modified: Wed, 16 May 2012 07:39:57 GMT | The Last-Modified header indicates the time that the origin server believes the representation was last modified. The value is Wed, 16 May 2012 07:39:57 GMT |
| ETag: "1bed181d-16f1-6d004d40" | An ETag is an opaque identifier assigned by a web server to a specific version of a resource found at a URL. If the resource content at that URL ever changes, a new and different ETag is assigned. Used in this manner ETags are similar to fingerprints, and they can be quickly compared to determine if two versions of a resource are the same or are different. "1bed181d-16f1-6d004d40" |
| Accept-Ranges: bytes | |
| Content-Length: 5873 | The Content-Length header indicates the size of the body, in number of bytes. In responses to the HEAD method, it indicates the size of the body that would have been sent had the request been a GET. If Content-Length is incorrect, persistent connections will not work, and caches may not store the response (since they can't be sure if they have the whole response). The content length is 5873 bytes |
| Vary: Accept-Encoding | |
| Content-Type: text/html | The Content-Type entity-header field indicates the media type of the entity-body sent to the recipient or, in the case of the HEAD method, the media type that would have been sent had the request been a GET. . The value is text/html |
Server location
Server location is important because a server that is located near the customer will serve pages faster then a server located far away
| IP Adress | 112.78.219.164 |
| Country Code | JP |
| Country Code 3 | JPN |
| Country Name | Japan |
www.prayforjapan.jp stylesheet info
Cascading Style Sheets (CSS) is a style sheet language used to describe the presentation semantics (the look and formatting) of a document written in a markup language.
Stylesheets in the head of the document
No css files were found on this page.
www.prayforjapan.jp inline stylesheet info
No inline css was detected on this page
Backlink analysis for www.prayforjapan.jp
Backlinks leading into a domain are of great important for the search engine results of a page. Each link from a website counts as a 'vote' for that websites. Links from trusted, related and high quality domains have more weight then other links.
Gathering links is often referred to as link building. If you do not have enought quility links to a domain you better start to build those links !
There are currently 0 links leading into www.prayforjapan.jp
There are a below average amount of backinks. Link building should be a priority for this site. Try to get links from hight quality websites to your site.
Links to external pages from www.prayforjapan.jp
|
www.twitter.com tweet - twitter.com/share |
|
www.prayforjapan.jp 心に残るつぶやき( inspiring and heart-warming tweets ) - prayforjapan.jp/message |
|
www.twitter.com @mocchicc - twitter.com/mocchicc |
www.prayforjapan.jp javascript info
Javascript is a scripting language to enable Web authors to design interactive sites. On this page we found 4 external javascripts and 4 internal javascripts on www.prayforjapan.jp
Javascripts in the head of the page
http://b.st-hatena.com/js/bookmark_button.js
http://platform.twitter.com/widgets.js
http://widgets.twimg.com/j/2/widget.js
http://widgets.twimg.com/j/2/widget.js
www.prayforjapan.jp inline javascript info
The following inline javascript snippets were found on this page:
if (navigator.useragent.indexof('iphone') != -1) {
document.write('<link rel="stylesheet" type="text/css" href="iphone.css">');
document.write('<meta name="viewport" content="width=480,maximum-scale=0.6667,user-scalable=no"> ');
document.write('<meta name="apple-mobile-web-app-status-bar-style" content="black">');
document.write('<meta name="format-detection" content="telephone=no">');
document.write('<link rel="apple-touch-icon" href="apple-touch-icon.png">');
document.write('<meta name="apple-mobile-web-app-capable" content="yes">');
}else {
document.write('<link rel="stylesheet" type="text/css" href="pc.css">');
}
var _gaq = _gaq || [];
_gaq.push(['_setaccount', 'ua-22004002-1']);
_gaq.push(['_trackpageview']);
(function() {
var ga = document.createelement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getelementsbytagname('script')[0]; s.parentnode.insertbefore(ga, s);
})();
new twtr.widget({
version: 2,
type: 'search',
search: '#prayforjapan',
interval: 2000,
title: '#prayforjapan',
subject: 'twitter',
width: 'auto',
height: 444,
theme: {
shell: {
background: 'none',
color: '#444444'
},
tweets: {
background: 'none',
color: '#444444',
links: '#888888'
}
},
features: {
scrollbar: false,
loop: false,
live: true,
hashtags: true,
timestamp: true,
avatars: true,
toptweets: false,
behavior: 'default'
}
}).render().start();
new twtr.widget({
version: 2,
type: 'search',
search: '#prayforjapan',
interval: 1400,
title: '#prayforjapan',
subject: 'twitter',
width: 'auto',
height: 500,
theme: {
shell: {
background: 'none',
color: '#444444'
},
tweets: {
background: 'none',
color: '#444444',
links: '#d2d2d2'
}
},
features: {
scrollbar: false,
loop: false,
live: true,
hashtags: true,
timestamp: true,
avatars: true,
toptweets: true,
behavior: 'default'
}
}).render().start();
www.prayforjapan.jp content analysis
On this page the content of www.prayforjapan.jp is analyzed for internal coherence.
In other words: r-domain checks if elements on the site (headings, meta tags, link anchor text etc) are in sync with the rest of the contents of the page.
Any element on a page should reflect to some degree the main subject of the page.
If an elemts matches the most important content of the page is is displayed in green. If it does not match is is displayed in red
Domain
| Site | www.prayforjapan.jp |
| Domain length | 19 characters |
| Domain relevance |
found the keyword prayforjapan in domain name ! |
Head
The head element is a container for all the elements int he head of a page. Elements inside head can fort example include scripts, instruct the browser where to find style sheets, provide meta information. We analyzed the follwoing tags in the head section: <title>, <link>, <meta>,<script>, and <style>.
| Page Title | pray for japan 東北太平洋沖地震、海外からの応援メッセージ集 prayforjapan.jp |
| Page Title relevance |
33% match pray japan prayforjapan |
| Meta Description | no page description found (0 chars) |
| Meta Deascription relevance |
0% match No title found ! |
| Meta Keywords | no keywords found |
| Meta keyword relevance |
0% match No meta keywords found ! |
| Meta | text/html; charset=utf-8 |
Content
Content is the most important thing on a website. Content can be indexed by seach engines. They provide most of a websites traffic. Tags such as headings (h1 .. h6), paragraphs (p) can be used to structure the text on the page. Tags as bold (b / strong) or italic (i / em) can be used the empasize important text. Images can be used to further explain or just to brighten up a page and can be describud using the alt tag. Links can be used to direct users to another page. All elements have in common that they use text and text can be indexed !
| Keyword density | aufffd badgeplz brclr brds com facebook iframe incls instagramh like mocchicc none pbclr prayforjapan svc top |
| Wordcount | 147 words found on www.prayforjapan.jp |
| Links |
3 links found on page containing the following anchor texts tweet, 心に残るつぶやき( inspiring and heart-warming tweets ), @mocchicc, |
| Link anchor relevance |
20% match tweet inspiring heart-warming tweets mocchicc |
| Headings |
0 headings found on page containing the following texts No headings found ! |
| Headings relevance |
0% match No headings found on this page! |
| Emphasis (bold and italic) |
2 bold or italic tags found on page containing the following texts 心に残るつぶやき( inspiring and heart-warming tweets ), instagram, |
| Bold and italic tag relevance |
0% match inspiring heart-warming tweets instagram |
| Image alt tags |
6 image alt tags found on page containing the following texts , このエントリーをはてなブックマークに追加, , , , , |
| Image alt tag relevance |
0% match No image alt tags found on this page ! |
www.prayforjapan.jp seo score expained
Below are the scores we calculated for different parts of www.prayforjapan.jp.
If any score is below 100 optimalisation is possible. If any score is below 40 improving this score should be a priority.
Not all scores are weighted equally in our final SEO score.
More detailed information for any suggestion can be count under the tabs.
Relatively unimportant optimalisation tips are not included in this summary.
| Item | Score | Factor | Suggestion | |
|---|---|---|---|---|
|
|
PageTitle | 100 | 0,3 | Far too many sites lack a page title. A page title is the first thing that shows in the search results so always use the title element. |
|
|
Title relevance | 43 | 2,3 | A title should reflect the contents of a site. This site has a 33 % match |
|
|
Title Length | 70 | 0,7 | Try to keep your title between 40 and 66 characters. Your title was 98 characters long |
|
|
Meta Description | 0 | 0,2 | A meta description is the second thing that shows in the search results so always use the meta description. |
|
|
Meta Description Length | 0 | 0,7 | The meta description should be between 145 and 160 characters. This meta description was 1 characters long |
|
|
Meta description relevance | 0 | 0,7 | Meta Description should reflect the contents of a site. This site has a 0 % match |
|
|
Folder structure | 60 | 1,4 | We have not detected an easy to follow directory structure on this page. Make sure your directory structure is easy to follow. |
|
|
Headings | 0 | 1,6 | Headers should reflect the contents of a site. This site has a 0 % match |
|
|
Links | 60 | 1,6 | Link anchors should to some degree reflect the contents of a site. This site has a 20 % match |
|
|
Image alt tags | 0 | 0,5 | Image alt tags should to some degree reflect the contents of a site. This site has a 0 % match |
|
|
Html ratio | 10 | 1,1 | Try to keep the html / text ratio as low as possible. More html means longer loading times. Layout should be handled in a serpate css file |
|
|
Page errors | 27 | 2 | If this score is not 100 check the html very carefully. We found 147 errors and warnings |
|
|
WordCount | 20 | 1,1 | An ideal page contains between 400 and 600 words.This page contains 148 words |
Analyse your website !
| Please enter your domain name |