PHILEMBASSY.NET Philippine Embassy – Tokyo, Japan | フィリピン 共和国 大使館

philembassy.net Website Information

Daily Unique Visits: 3,339

Daily Page Views: 13,356

Income Per Day: $37

Estimated Value: $19,980

This website is located in Japan and is using following IP address 220.247.10.248. See the complete list of popular websites hosted in Japan.

philembassy.net is registered under .NET top-level domain. Please check other sites in .NET zone.

Website philembassy.net is using the following name servers:

  • buyurl.earth.orderbox-dns.com
  • buyurl.mercury.orderbox-dns.com
  • buyurl.mars.orderbox-dns.com
  • buyurl.venus.orderbox-dns.com

and is probably hosted by VECTANT ARTERIA Networks Corporation, JP. See the full list of other websites hosted by VECTANT ARTERIA Networks Corporation, JP.

The highest website philembassy.net position in Alexa rank database was 10776 and the lowest rank position was 994150. Current position of philembassy.net in Alexa rank database is 375813.

Desktop speed score of philembassy.net (61/100) is better than the results of 37.05% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of philembassy.net (87/100) is better than the results of 28.3% of other sites and means that the page is mobile-friendly.

Mobile speed score of philembassy.net (74/100) is better than the results of 83.2% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

philembassy.net 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.


philembassy.net 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: PHILEMBASSY.NET
Registry Domain ID: 96996796_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.PublicDomainRegistry.com
Registrar URL: http://www.publicdomainregistry.com
Updated Date: 2024-04-18T10:36:49Z
Creation Date: 2003-04-19T15:08:27Z
Registry Expiry Date: 2025-04-19T15:08:27Z
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID: 303
Registrar Abuse Contact Email: abuse-contact@publicdomainregistry.com
Registrar Abuse Contact Phone: +1.2013775952
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.DNSEXIT.COM
Name Server: NS2.DNSEXIT.COM
Name Server: NS3.DNSEXIT.COM
Name Server: NS4.DNSEXIT.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-11-13T06:54:21Z

philembassy.net server information

Servers Location

philembassy.net desktop page speed rank

Last tested: 2019-09-02


Desktop Speed Bad
61/100

philembassy.net Desktop Speed Test Quick Summary


priority - 35Optimize images

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

Optimize the following images to reduce their size by 345.4KiB (44% reduction).

Compressing http://tokyo.philembassy.net/images/slides201506/12_JR_Manila.jpg could save 47.2KiB (41% reduction).
Compressing http://tokyo.philembassy.net/images/slides201506/1_JR_Cebu.jpg could save 42KiB (41% reduction).
Compressing http://tokyo.philembassy.net/images/slides201506/2_JR_Vigan.jpg could save 38.7KiB (39% reduction).
Compressing http://tokyo.philembassy.net/images/slides201506/11_JR_Palawan-a.jpg could save 30.6KiB (33% reduction).
Compressing http://tokyo.philembassy.net/images/slides201506/11_JR_Palawan-b.jpg could save 28.6KiB (34% reduction).
Compressing http://tokyo.philembassy.net/images/slides201506/9_JR_Bohol.jpg could save 27.2KiB (33% reduction).
Compressing and resizing http://tokyo.philembassy.net/wp-content/uploads/20…r-20190827-320x180.jpg could save 17.6KiB (82% reduction).
Compressing http://tokyo.philembassy.net/images/its-more-fun-vert.jpg could save 17.4KiB (39% reduction).
Compressing and resizing http://tokyo.philembassy.net/wp-content/uploads/20…20190829-1-320x180.jpg could save 16.9KiB (82% reduction).
Compressing http://philembassy.net/images/bnr-dotjapan.jpg could save 16.6KiB (71% reduction).
Compressing http://philembassy.net/images/bnr-1343-call-text.jpg could save 15.9KiB (48% reduction).
Compressing http://philembassy.net/images/bnr-dti.jpg could save 13.8KiB (74% reduction).
Compressing and resizing http://tokyo.philembassy.net/wp-content/uploads/20…20190830-2-320x180.jpg could save 13.2KiB (81% reduction).
Compressing and resizing http://tokyo.philembassy.net/wp-content/uploads/20…20190822-1-320x180.jpg could save 12KiB (80% reduction).
Compressing http://philembassy.net/images/bnr-polotokyo.jpg could save 5.8KiB (53% reduction).
Compressing http://tokyo.philembassy.net/wp-content/uploads/20…pe-300x300-150x150.jpg could save 1.6KiB (20% reduction).
Compressing http://tokyo.philembassy.net/wp-content/themes/tokyope2015/images/rss.gif could save 420B (41% reduction).
Compressing https://static.xx.fbcdn.net/rsrc.php/v3/y5/r/OqOE2….png?_nc_x=Ij3Wp8lg5Kz could save 201B (50% reduction).

priority - 20Leverage 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://philembassy.net/images/banner-tfd.png (expiration not specified)
http://philembassy.net/images/bnr-1343-call-text.jpg (expiration not specified)
http://philembassy.net/images/bnr-balinkbayan.png (expiration not specified)
http://philembassy.net/images/bnr-carto-exhibit.png (expiration not specified)
http://philembassy.net/images/bnr-dotjapan.jpg (expiration not specified)
http://philembassy.net/images/bnr-dti.jpg (expiration not specified)
http://philembassy.net/images/bnr-polotokyo.jpg (expiration not specified)
http://philembassy.net/images/bnr-s-red.png (expiration not specified)
http://philembassy.net/wp-content/themes/tokyope2015/images/seal-rp.png (expiration not specified)
http://philembassy.net/wp-content/themes/tokyope2015/images/topheader.png (expiration not specified)
http://philembassy.net/wp-content/themes/tokyope2015/js/dropdowns.js (expiration not specified)
http://philembassy.net/wp-content/themes/tokyope20…overIntent.minified.js (expiration not specified)
http://tokyo.philembassy.net/images/bg_leadarticle.jpg (expiration not specified)
http://tokyo.philembassy.net/images/its-more-fun-vert.jpg (expiration not specified)
http://tokyo.philembassy.net/images/slides201506/11_JR_Palawan-a.jpg (expiration not specified)
http://tokyo.philembassy.net/images/slides201506/11_JR_Palawan-b.jpg (expiration not specified)
http://tokyo.philembassy.net/images/slides201506/12_JR_Manila.jpg (expiration not specified)
http://tokyo.philembassy.net/images/slides201506/1_JR_Cebu.jpg (expiration not specified)
http://tokyo.philembassy.net/images/slides201506/2_JR_Vigan.jpg (expiration not specified)
http://tokyo.philembassy.net/images/slides201506/9_JR_Bohol.jpg (expiration not specified)
http://tokyo.philembassy.net/wp-content/plugins/ev…ar/css/ec-tooltips.css (expiration not specified)
http://tokyo.philembassy.net/wp-content/plugins/ev…ss/events-calendar.css (expiration not specified)
http://tokyo.philembassy.net/wp-content/plugins/se…ideo-js/skins/tube.css (expiration not specified)
http://tokyo.philembassy.net/wp-content/plugins/se…/video-js/video-js.css (expiration not specified)
http://tokyo.philembassy.net/wp-content/plugins/se…ayer/video-js/video.js (expiration not specified)
http://tokyo.philembassy.net/wp-content/themes/tok…015/images/bg-gray.png (expiration not specified)
http://tokyo.philembassy.net/wp-content/themes/tok…images/bg-mid-blue.png (expiration not specified)
http://tokyo.philembassy.net/wp-content/themes/tok…/images/bg-mid-red.png (expiration not specified)
http://tokyo.philembassy.net/wp-content/themes/tok…015/images/magnify.gif (expiration not specified)
http://tokyo.philembassy.net/wp-content/themes/tokyope2015/images/rss.gif (expiration not specified)
http://tokyo.philembassy.net/wp-content/themes/tokyope2015/print.css (expiration not specified)
http://tokyo.philembassy.net/wp-content/uploads/20…pe-300x300-150x150.jpg (expiration not specified)
http://tokyo.philembassy.net/wp-content/uploads/20…20190822-1-320x180.jpg (expiration not specified)
http://tokyo.philembassy.net/wp-content/uploads/20…r-20190827-320x180.jpg (expiration not specified)
http://tokyo.philembassy.net/wp-content/uploads/20…20190829-1-320x180.jpg (expiration not specified)
http://tokyo.philembassy.net/wp-content/uploads/20…20190830-2-320x180.jpg (expiration not specified)
http://tokyo.philembassy.net/wp-content/uploads/20…r-20190902-320x180.jpg (expiration not specified)
http://tokyo.philembassy.net/wp-includes/js/thickbox/loadingAnimation.gif (expiration not specified)
http://tokyo.philembassy.net/wp-includes/js/thickbox/thickbox.css (expiration not specified)
https://cse.google.co.jp/cse/brand?form=cse-search-box&lang=en (30 minutes)
https://seal.beyondsecurity.com/verification-image…rability-scanner-2.gif (60 minutes)

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

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

Remove render-blocking JavaScript:

http://tokyo.philembassy.net/wp-includes/js/jquery/jquery.js?ver=1.12.4
http://tokyo.philembassy.net/wp-includes/js/jquery…grate.min.js?ver=1.4.1
https://code.jquery.com/jquery-migrate-1.2.1.js?ver=1.2.1
http://tokyo.philembassy.net/wp-content/plugins/ev…ry.bgiframe.js?ver=2.1
http://tokyo.philembassy.net/wp-content/plugins/ev…tooltip.min.js?ver=1.3
http://tokyo.philembassy.net/wp-content/plugins/vs…s/vslider.js?ver=5.1.1
http://tokyo.philembassy.net/wp-content/plugins/se…ayer/video-js/video.js
http://philembassy.net/wp-content/themes/tokyope20…overIntent.minified.js
http://philembassy.net/wp-content/themes/tokyope2015/js/dropdowns.js

Optimize CSS Delivery of the following:

http://tokyo.philembassy.net/wp-content/themes/tok…yle.css?v=201704190342
http://tokyo.philembassy.net/wp-content/themes/tok…5/nav.css?t=1506405661
http://tokyo.philembassy.net/wp-includes/css/dist/…tyle.min.css?ver=5.1.1
http://tokyo.philembassy.net/wp-content/plugins/co…css/styles.css?ver=4.5
http://tokyo.philembassy.net/wp-content/plugins/wp…enavi-css.css?ver=2.70
http://tokyo.philembassy.net/wp-content/plugins/dv…yles.min.css?ver=1.3.2
http://tokyo.philembassy.net/wp-includes/js/thickbox/thickbox.css
http://tokyo.philembassy.net/wp-content/plugins/ev…ss/events-calendar.css
http://tokyo.philembassy.net/wp-content/plugins/ev…ar/css/ec-tooltips.css
http://tokyo.philembassy.net/wp-content/plugins/se…/video-js/video-js.css
http://tokyo.philembassy.net/wp-content/plugins/se…ideo-js/skins/tube.css
http://tokyo.philembassy.net/wp-content/plugins/wa…widget.css?ver=1.9.4.4

priority - 1Minify 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 13KiB (40% reduction).

Minifying http://tokyo.philembassy.net/wp-content/plugins/se…ayer/video-js/video.js could save 6.6KiB (44% reduction) after compression.
Minifying https://code.jquery.com/jquery-migrate-1.2.1.js?ver=1.2.1 could save 2.2KiB (40% reduction) after compression.
Minifying http://tokyo.philembassy.net/wp-content/plugins/ev…ry.bgiframe.js?ver=2.1 could save 1.3KiB (67% reduction) after compression.
Minifying http://tokyo.philembassy.net/wp-content/plugins/vs…s/vslider.js?ver=5.1.1 could save 1.3KiB (35% reduction) after compression.
Minifying http://tokyo.philembassy.net/wp-includes/js/thickb…ox.js?ver=3.1-20121105 could save 1.2KiB (32% reduction) after compression.
Minifying http://tokyo.philembassy.net/wp-content/plugins/ev…tooltip.min.js?ver=1.3 could save 228B (13% reduction) after compression.
Minifying http://philembassy.net/wp-content/themes/tokyope20…overIntent.minified.js could save 182B (26% reduction) after compression.

priority - 0Reduce server response time

In our test, your server responded in 0.25 seconds.

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 3.9KiB (30% reduction).

Minifying http://tokyo.philembassy.net/wp-content/plugins/se…/video-js/video-js.css could save 1.7KiB (50% reduction) after compression.
Minifying http://tokyo.philembassy.net/wp-content/themes/tok…yle.css?v=201704190342 could save 842B (19% reduction) after compression.
Minifying http://tokyo.philembassy.net/wp-content/plugins/se…ideo-js/skins/tube.css could save 465B (34% reduction) after compression.
Minifying http://tokyo.philembassy.net/wp-content/plugins/ev…ss/events-calendar.css could save 284B (22% reduction) after compression.
Minifying http://tokyo.philembassy.net/wp-content/themes/tok…5/nav.css?t=1506405661 could save 274B (21% reduction) after compression.
Minifying http://tokyo.philembassy.net/wp-content/plugins/ev…ar/css/ec-tooltips.css could save 250B (44% reduction) after compression.
Minifying http://tokyo.philembassy.net/wp-content/plugins/wa…widget.css?ver=1.9.4.4 could save 152B (17% 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 1.6KiB (11% reduction).

Minifying http://philembassy.net/ could save 1.6KiB (11% reduction) after compression.

philembassy.net Desktop Resource Breakdown

Total Resources65
Number of Hosts8
Static Resources44
JavaScript Resources17
CSS Resources13

philembassy.net mobile page speed rank

Last tested: 2019-08-27


Mobile Speed Medium
74/100

philembassy.net Mobile Speed Test Quick Summary


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

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

Remove render-blocking JavaScript:

http://tokyo.philembassy.net/wp-includes/js/jquery/jquery.js?ver=1.12.4
http://tokyo.philembassy.net/wp-includes/js/jquery…grate.min.js?ver=1.4.1
http://tokyo.philembassy.net/wp-content/themes/car…1/js/mobile.js?ver=1.0
https://code.jquery.com/jquery-migrate-1.2.1.js?ver=1.2.1
http://tokyo.philembassy.net/wp-content/plugins/ev…ry.bgiframe.js?ver=2.1
http://tokyo.philembassy.net/wp-content/plugins/ev…tooltip.min.js?ver=1.3
http://tokyo.philembassy.net/wp-includes/js/thickb…ox.js?ver=3.1-20121105
http://tokyo.philembassy.net/wp-content/plugins/vs…s/vslider.js?ver=5.1.1

Optimize CSS Delivery of the following:

http://tokyo.philembassy.net/wp-content/themes/car…n-mobile-1.1/style.css
http://tokyo.philembassy.net/wp-content/themes/car…e-1.1/css/advanced.css
http://tokyo.philembassy.net/wp-content/themes/car…bile-1.1/css/touch.css

priority - 1Leverage 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://tokyo.philembassy.net/wp-includes/js/thickbox/loadingAnimation.gif (expiration not specified)

priority - 1Minify 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 6.2KiB (37% reduction).

Minifying https://code.jquery.com/jquery-migrate-1.2.1.js?ver=1.2.1 could save 2.2KiB (40% reduction) after compression.
Minifying http://tokyo.philembassy.net/wp-content/plugins/ev…ry.bgiframe.js?ver=2.1 could save 1.3KiB (67% reduction) after compression.
Minifying http://tokyo.philembassy.net/wp-content/plugins/vs…s/vslider.js?ver=5.1.1 could save 1.3KiB (35% reduction) after compression.
Minifying http://tokyo.philembassy.net/wp-includes/js/thickb…ox.js?ver=3.1-20121105 could save 1.2KiB (32% reduction) after compression.
Minifying http://tokyo.philembassy.net/wp-content/plugins/ev…tooltip.min.js?ver=1.3 could save 228B (13% reduction) after compression.

philembassy.net Mobile Resource Breakdown

Total Resources13
Number of Hosts3
Static Resources2
JavaScript Resources7

philembassy.net mobile page usability

Last tested: 2019-08-27


Mobile Usability Good
87/100

philembassy.net Mobile Usability Test Quick Summary


priority - 10Size 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://tokyo.p…ion-on-mining/">Philippines an…g Aug 22, 2019</a> and 32 others are close to other tap targets.

The tap target <a href="http://tokyo.p…t/wp-login.php">Log in</a> is close to 1 other tap targets.

priority - 3Configure the viewport

Your page specifies a fixed-width mobile viewport. Consider using a responsive viewport to allow your page to render properly on all devices.

philembassy.net HTML validation

Errors

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

Line: 1 Column: 1 - 121
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html..."

The “profile” attribute on the “head” element is obsolete. To declare which “meta” terms are used in the document, instead register the names as meta extensions. To trigger specific UA behaviors, use a “link” element instead.

Line: 4 Column: 57 - 39
"...g="en-US"> <head profile="http://gmpg.org/xfn/11"> <meta..."

Bad value “screen,projection” for attribute “media” on element “link”: Deprecated media type “projection”. For guidance, see the Media Types section in the current Media Queries specification.

Line: 13 Column: 1 - 158
"...大使館" /> <link rel="stylesheet" href="http://tokyo.philembassy.net/wp-content/themes/tokyope2015/style.css?v=201704190342" type="text/css" media="screen,projection" /> <link..." Line: 15 Column: 1 - 154
"...print" /> <link rel="stylesheet" href="http://tokyo.philembassy.net/wp-content/themes/tokyope2015/nav.css?t=1506405661" type="text/css" media="screen,projection" /> <lin..."

A document must not include more than one “meta” element with its “name” attribute set to the value “description”.

Line: 27 Column: 1 - 86
"...s.w.org'> <meta name="description" content="Philippine Embassy - Tokyo, Japan: フィリピン 共和国 大使館" /> <meta..."

Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.

Line: 57 Column: 1 - 78
"...</script> <link rel='https://api.w.org/' href='http://tokyo.philembassy.net/wp-json/' /> <link..."

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

Line: 128 Column: 3 - 78
"...anner"> <img src="/wp-content/themes/tokyope2015/images/seal-rp.png" height="100px"></img>..." Line: 129 Column: 3 - 94
"...></img> <img src="/wp-content/themes/tokyope2015/images/topheader.png" height="100px" width="700px"></img>..."

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

Line: 128 Column: 3 - 78
"...anner"> <img src="/wp-content/themes/tokyope2015/images/seal-rp.png" height="100px"></img>..." Line: 129 Column: 3 - 94
"...></img> <img src="/wp-content/themes/tokyope2015/images/topheader.png" height="100px" width="700px"></img>..." Line: 661 Column: 125 - 158
"...ponline/'><img src='/images/bnr-s-red.png'/></a> <..."

Stray end tag “img”.

Line: 128 Column: 79 - 84
"...t="100px"></img> <im..." Line: 129 Column: 95 - 100
"...h="700px"></img> </div..."

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

Line: 129 Column: 3 - 94
"...></img> <img src="/wp-content/themes/tokyope2015/images/topheader.png" height="100px" width="700px"></img>..."

Attribute “alt” not allowed on element “a” at this point.

Line: 135 Column: 46 - 100
"...age_item"><a href="http://tokyo.philembassy.net/" alt="Homepage">Homepa..." Line: 238 Column: 27 - 110
"...age_item"><a href="http://tokyo.philembassy.net/webmail/" target="_top" alt="Embassy Webmail">Embass..."

Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)

Line: 248 Column: 1 - 38
"...tions --> <style type="text/css" media="screen"> #slid..."

Element “h4” not allowed as child of element “span” in this context. (Suppressing further errors from this subtree.)

Line: 312 Column: 27 - 30
"... <span><h4>セブ</h4..." Line: 316 Column: 27 - 30
"... <span><h4>ビガン</h..." Line: 320 Column: 27 - 30
"... <span><h4>ボホール</..." Line: 324 Column: 27 - 30
"... <span><h4>マニラ</h..." Line: 331 Column: 27 - 30
"... <span><h4>パラワン</..." Line: 335 Column: 27 - 30
"... <span><h4>パラワン</..."

Element “input” is missing required attribute “alt”.

Line: 394 Column: 5 - 138
"...;" /> <input type="image" name="sa" src="http://tokyo.philembassy.net/wp-content/themes/tokyope2015/images/magnify.gif" id="searchsubmit" /> </for..."

Element “p” not allowed as child of element “span” in this context. (Suppressing further errors from this subtree.)

Line: 411 Column: 41 - 43
"...justify;"><p>Diplom..."

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

Line: 495 Column: 1 - 8
"... <br> <center><div c..."

The “scrolling” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 660 Column: 1 - 327
"...l> <br /> <iframe src="https://www.facebook.com/plugins/like.php?href=https%3A%2F%2Fwww%2Ffacebook.com%2FPHLinJapan%2F&width=265&layout=standard&action=like&size=small&show_faces=true&share=false&height=80&appId" width="265" height="80" style="border:none;overflow:hidden" scrolling="no" frameborder="0" allowTransparency="true"></iframe></div..."

The “frameborder” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 660 Column: 1 - 327
"...l> <br /> <iframe src="https://www.facebook.com/plugins/like.php?href=https%3A%2F%2Fwww%2Ffacebook.com%2FPHLinJapan%2F&width=265&layout=standard&action=like&size=small&show_faces=true&share=false&height=80&appId" width="265" height="80" style="border:none;overflow:hidden" scrolling="no" frameborder="0" allowTransparency="true"></iframe></div..."

The “allowtransparency” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 660 Column: 1 - 327
"...l> <br /> <iframe src="https://www.facebook.com/plugins/like.php?href=https%3A%2F%2Fwww%2Ffacebook.com%2FPHLinJapan%2F&width=265&layout=standard&action=like&size=small&show_faces=true&share=false&height=80&appId" width="265" height="80" style="border:none;overflow:hidden" scrolling="no" frameborder="0" allowTransparency="true"></iframe></div..."

No space between attributes.

Line: 677 Column: - 59
"...seas Filipinos'' One Stop Onli..."

Saw “'” when expecting an attribute name. Probable cause: “=” missing immediately before.

Line: 677 Column: - 59
"...seas Filipinos'' One Stop Onli..."

Quote “'” in attribute name. Probable cause: Matching quote missing somewhere earlier.

Line: 677 Column: - 107
"...pora Engagement'></a> <br /><b..."

Attribute “'” not allowed on element “img” at this point.

Line: 677 Column: 58 - 108
"...='_blank'><img src='/images/bnr-balinkbayan.png' alt='Overseas Filipinos'' One Stop Online Portal for Diaspora Engagement'></a> <..."

Attribute “one” not allowed on element “img” at this point.

Line: 677 Column: 58 - 108
"...='_blank'><img src='/images/bnr-balinkbayan.png' alt='Overseas Filipinos'' One Stop Online Portal for Diaspora Engagement'></a> <..."

Attribute “stop” not allowed on element “img” at this point.

Line: 677 Column: 58 - 108
"...='_blank'><img src='/images/bnr-balinkbayan.png' alt='Overseas Filipinos'' One Stop Online Portal for Diaspora Engagement'></a> <..."

Attribute “online” not allowed on element “img” at this point.

Line: 677 Column: 58 - 108
"...='_blank'><img src='/images/bnr-balinkbayan.png' alt='Overseas Filipinos'' One Stop Online Portal for Diaspora Engagement'></a> <..."

Attribute “portal” not allowed on element “img” at this point.

Line: 677 Column: 58 - 108
"...='_blank'><img src='/images/bnr-balinkbayan.png' alt='Overseas Filipinos'' One Stop Online Portal for Diaspora Engagement'></a> <..."

Attribute “for” not allowed on element “img” at this point.

Line: 677 Column: 58 - 108
"...='_blank'><img src='/images/bnr-balinkbayan.png' alt='Overseas Filipinos'' One Stop Online Portal for Diaspora Engagement'></a> <..."

Attribute “diaspora” not allowed on element “img” at this point.

Line: 677 Column: 58 - 108
"...='_blank'><img src='/images/bnr-balinkbayan.png' alt='Overseas Filipinos'' One Stop Online Portal for Diaspora Engagement'></a> <..."

Attribute “engagement'” not allowed on element “img” at this point.

Line: 677 Column: 58 - 108
"...='_blank'><img src='/images/bnr-balinkbayan.png' alt='Overseas Filipinos'' One Stop Online Portal for Diaspora Engagement'></a> <..."

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: 684 Column: 1 - 49
"...ar_wrap"> <table summary="Event Calendar" id="wp-calendar"> <capt..."

Element “tbody” not allowed as child of element “table” in this context. (Suppressing further errors from this subtree.)

Line: 700 Column: 14 - 7
"...r></tfoot> <tbody><tr> <..."

Warnings

Attribute “'” is not serializable as XML 1.0.

Line: 677 Column: 58 - 108
"...='_blank'><img src='/images/bnr-balinkbayan.png' alt='Overseas Filipinos'' One Stop Online Portal for Diaspora Engagement'></a> <..."

Attribute “engagement'” is not serializable as XML 1.0.

Line: 677 Column: 58 - 108
"...='_blank'><img src='/images/bnr-balinkbayan.png' alt='Overseas Filipinos'' One Stop Online Portal for Diaspora Engagement'></a> <..."

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

Line: 1050 Column: 98 - 251
"...assy.net"><img src="https://seal.beyondsecurity.com/verification-images/tokyo.philembassy.net/vulnerability-scanner-2.gif" alt="Website Security Test" border="0" /></a> <..."

philembassy.net similar domains

Similar domains:
www.philembassy.com
www.philembassy.net
www.philembassy.org
www.philembassy.info
www.philembassy.biz
www.philembassy.us
www.philembassy.mobi
www.hilembassy.net
www.philembassy.net
www.ohilembassy.net
www.pohilembassy.net
www.ophilembassy.net
www.lhilembassy.net
www.plhilembassy.net
www.lphilembassy.net
www.pilembassy.net
www.pbilembassy.net
www.phbilembassy.net
www.pbhilembassy.net
www.pgilembassy.net
www.phgilembassy.net
www.pghilembassy.net
www.pyilembassy.net
www.phyilembassy.net
www.pyhilembassy.net
www.puilembassy.net
www.phuilembassy.net
www.puhilembassy.net
www.pjilembassy.net
www.phjilembassy.net
www.pjhilembassy.net
www.pnilembassy.net
www.phnilembassy.net
www.pnhilembassy.net
www.phlembassy.net
www.phulembassy.net
www.phiulembassy.net
www.phjlembassy.net
www.phijlembassy.net
www.phklembassy.net
www.phiklembassy.net
www.phkilembassy.net
www.pholembassy.net
www.phiolembassy.net
www.phoilembassy.net
www.phiembassy.net
www.phipembassy.net
www.philpembassy.net
www.phiplembassy.net
www.phioembassy.net
www.philoembassy.net
www.phikembassy.net
www.philkembassy.net
www.philmbassy.net
www.philwmbassy.net
www.philewmbassy.net
www.philwembassy.net
www.philsmbassy.net
www.philesmbassy.net
www.philsembassy.net
www.phildmbassy.net
www.philedmbassy.net
www.phildembassy.net
www.philrmbassy.net
www.philermbassy.net
www.philrembassy.net
www.philebassy.net
www.philenbassy.net
www.philemnbassy.net
www.philenmbassy.net
www.philejbassy.net
www.philemjbassy.net
www.philejmbassy.net
www.philekbassy.net
www.philemkbassy.net
www.philekmbassy.net
www.philemassy.net
www.philemvassy.net
www.philembvassy.net
www.philemvbassy.net
www.philemgassy.net
www.philembgassy.net
www.philemgbassy.net
www.philemhassy.net
www.philembhassy.net
www.philemhbassy.net
www.philemnassy.net
www.philembnassy.net
www.philembssy.net
www.philembqssy.net
www.philembaqssy.net
www.philembqassy.net
www.philembwssy.net
www.philembawssy.net
www.philembwassy.net
www.philembsssy.net
www.philembasssy.net
www.philembsassy.net
www.philembzssy.net
www.philembazssy.net
www.philembzassy.net
www.philembasy.net
www.philembawsy.net
www.philembaswsy.net
www.philembaesy.net
www.philembasesy.net
www.philembaessy.net
www.philembadsy.net
www.philembasdsy.net
www.philembadssy.net
www.philembazsy.net
www.philembaszsy.net
www.philembaxsy.net
www.philembasxsy.net
www.philembaxssy.net
www.philembaasy.net
www.philembasasy.net
www.philembaassy.net
www.philembaswy.net
www.philembasswy.net
www.philembasey.net
www.philembassey.net
www.philembasdy.net
www.philembassdy.net
www.philembaszy.net
www.philembasszy.net
www.philembasxy.net
www.philembassxy.net
www.philembasay.net
www.philembassay.net
www.philembass.net
www.philembasst.net
www.philembassyt.net
www.philembassty.net
www.philembassg.net
www.philembassyg.net
www.philembassgy.net
www.philembassh.net
www.philembassyh.net
www.philembasshy.net
www.philembassu.net
www.philembassyu.net
www.philembassuy.net

philembassy.net 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.


philembassy.net 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.