VIROLOGY.WS Home | Virology Blog

virology.ws Website Information

Daily Unique Visits: 19,624

Daily Page Views: 117,744

Income Per Day: $235

Estimated Value: $169,200

virology.ws is registered under .WS top-level domain. Please check other sites in .WS zone.

No name server records were found.

and is probably hosted by LINODE-AP Linode, LLC, US. See the full list of other websites hosted by LINODE-AP Linode, LLC, US.

The highest website virology.ws position in Alexa rank database was 43478 and the lowest rank position was 975932. Current position of virology.ws in Alexa rank database is 73085.

Desktop speed score of virology.ws (75/100) is better than the results of 59.78% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of virology.ws (63/100) is better than the results of 9.16% of other sites and means that the page is not mobile-friendly.

Mobile speed score of virology.ws (48/100) is better than the results of 30.32% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

virology.ws 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.


virology.ws 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.


virology.ws server information

Servers Location

virology.ws desktop page speed rank

Last tested: 2019-07-06


Desktop Speed Medium
75/100

virology.ws Desktop Speed Test Quick Summary


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

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

Remove render-blocking JavaScript:

http://www.virology.ws/wp-includes/js/jquery/jquery.js?ver=1.12.4
http://www.virology.ws/wp-includes/js/jquery/jquer…grate.min.js?ver=1.4.1
http://www.virology.ws/wp-content/plugins/google-a…cking.min.js?ver=6.5.4
http://www.virology.ws/wp-content/plugins/wp-googl…google_cse_v2.js?ver=1

Optimize CSS Delivery of the following:

http://www.virology.ws/wp-content/thesis/skins/classic-r/css.css
https://use.typekit.net/rjo5drv.css
https://p.typekit.net/p.css?s=1&k=rjo5drv&ht=tk&f=…2909&app=typekit&e=css
http://www.virology.ws/wp-content/plugins/wp-googl…rch/wgs.css?ver=4.9.10
http://www.virology.ws/wp-content/plugins/wp-googl…ch/wgs2.css?ver=4.9.10

priority - 7Leverage 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://www.virology.ws/wp-content/thesis/skins/classic-r/css.css (expiration not specified)
http://www.virology.ws/wp-content/uploads/2011/05/…hage_model-250x300.jpg (expiration not specified)
http://www.virology.ws/wp-content/uploads/2015/11/blog20.png (expiration not specified)
http://www.virology.ws/wp-content/uploads/2019/03/paulmeasles150pad-1.jpeg (expiration not specified)
http://www.virology.ws/wp-content/uploads/2019/06/…0-22.41.00-300x141.png (expiration not specified)
http://www.virology.ws/wp-content/uploads/2019/07/hav_entry-208x300.png (expiration not specified)
https://use.typekit.net/rjo5drv.css (10 minutes)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://www.googletagmanager.com/gtag/js?id=UA-702124-2 (15 minutes)
https://www.google.com/cse/static/style/look/v3/default.css (50 minutes)
http://cse.google.com/adsense/search/async-ads.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
http://cdn.embed.ly/player-0.0.12.min.js (4 hours)

priority - 6Optimize images

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

Optimize the following images to reduce their size by 60KiB (40% reduction).

Compressing http://www.virology.ws/wp-content/uploads/2019/03/paulmeasles150pad-1.jpeg could save 18.6KiB (83% reduction).
Compressing https://ssl-static.libsyn.com/p/assets/8/3/5/0/835…_TWiM_v3_white2400.jpg could save 7.1KiB (67% reduction).
Compressing https://ssl-static.libsyn.com/p/assets/a/9/e/7/a9e…_TWiV_v3_white2400.jpg could save 7.1KiB (67% reduction).
Compressing https://ssl-static.libsyn.com/p/assets/a/9/e/7/a9e…_TWiV_v3_white2400.jpg could save 7.1KiB (67% reduction).
Compressing http://www.virology.ws/wp-content/uploads/2019/06/…0-22.41.00-300x141.png could save 7KiB (33% reduction).
Compressing http://www.virology.ws/wp-content/uploads/2011/05/…hage_model-250x300.jpg could save 6.3KiB (21% reduction).
Compressing http://www.virology.ws/wp-content/uploads/2019/07/hav_entry-208x300.png could save 5KiB (13% reduction).
Compressing https://www.google.com/cse/static/css/v2/clear.png could save 898B (88% reduction).
Compressing https://yt3.ggpht.com/-46CBP8VAmPE/AAAAAAAAAAI/AAA…rj-c0xffffff/photo.jpg could save 432B (29% reduction).
Compressing http://static.libsyn.com/p/assets/c/c/5/9/cc59d89a…yn_Player_Bug68x20.png could save 217B (18% reduction).
Compressing http://static.libsyn.com/p/assets/c/c/5/9/cc59d89a…yn_Player_Bug68x20.png could save 217B (18% reduction).

priority - 2Reduce server response time

In our test, your server responded in 0.39 seconds.

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

Minifying https://www.google.com/cse/static/element/e1b7867e793369c8/default+en.css could save 3.8KiB (40% reduction) after compression.
Minifying http://www.virology.ws/wp-content/thesis/skins/classic-r/css.css could save 850B (19% reduction) after compression.
Minifying https://www.google.com/cse/static/style/look/v3/default.css could save 512B (19% reduction) after compression.
Minifying https://use.typekit.net/rjo5drv.css could save 283B (40% reduction) after compression.
Minifying http://www.virology.ws/wp-content/plugins/wp-googl…ch/wgs2.css?ver=4.9.10 could save 280B (34% reduction) after compression.
Minifying http://www.virology.ws/wp-content/plugins/wp-googl…rch/wgs.css?ver=4.9.10 could save 207B (29% reduction) after compression.
Minifying http://static.libsyn.com/p/assets/platform/fonts/l…ns:300,400,600,700,800 could save 118B (24% reduction) after compression.

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

Minifying http://html5-player.libsyn.com/embed/episode/id/10…o/custom-color/a53939/ could save 1.7KiB (17% reduction) after compression.
Minifying http://html5-player.libsyn.com/embed/episode/id/10…o/custom-color/166899/ could save 1.7KiB (18% reduction) after compression.
Minifying http://html5-player.libsyn.com/embed/episode/id/10…o/custom-color/166899/ could save 1.7KiB (18% reduction) after compression.

priority - 0Enable 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 478B (42% reduction).

Compressing http://static.libsyn.com/p/assets/platform/customp…/images/lock-black.svg could save 478B (42% reduction).

virology.ws Desktop Resource Breakdown

Total Resources82
Number of Hosts23
Static Resources45
JavaScript Resources19
CSS Resources13

virology.ws mobile page speed rank

Last tested: 2019-01-23


Mobile Speed Bad
48/100

virology.ws Mobile Speed Test Quick Summary


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

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

Remove render-blocking JavaScript:

http://use.typekit.net/pdw2csb.js
http://www.virology.ws/wp-content/plugins/powerpre…layer.min.js?ver=4.2.4
http://www.virology.ws/wp-includes/js/jquery/jquery.js?ver=1.11.2
http://www.virology.ws/wp-includes/js/jquery/jquer…grate.min.js?ver=1.2.1
http://www.virology.ws/wp-content/plugins/sociable/js/sociable.js?ver=4.2.4
http://www.virology.ws/wp-content/plugins/sociable/js/vuible.js?ver=4.2.4
http://www.virology.ws/wp-content/plugins/sociable…favorites.js?ver=4.2.4
http://www.virology.ws/wp-content/plugins/google-a…cking.min.js?ver=6.4.9
http://platform.twitter.com/widgets.js

Use asynchronous versions of the following scripts:

http://apis.google.com/js/plusone.js

Optimize CSS Delivery of the following:

http://www.virology.ws/wp-content/themes/thesis_186/custom/layout.css
http://www.virology.ws/wp-content/themes/thesis_186/custom/custom.css
https://use.typekit.net/c/c25a24/1w;franklin-gothi…f9e9c4b4a688a9ccadd881
http://www.virology.ws/wp-includes/js/mediaelement…yer.min.css?ver=2.16.2
http://www.virology.ws/wp-includes/js/mediaelement…aelement.css?ver=4.2.4
http://www.virology.ws/wp-content/plugins/sociable…sociable.css?ver=4.2.4

priority - 28Leverage 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://www.twiv.tv/TWiM_AA_200.jpg (expiration not specified)
http://www.twiv.tv/TWiP_200.png (expiration not specified)
http://www.twiv.tv/wp-content/uploads/2013/04/NEDILthumb200.png (expiration not specified)
http://www.urbanag.ws/urbag_square_200.jpg (expiration not specified)
http://www.virology.ws/TWiV_200.jpg (expiration not specified)
http://www.virology.ws/pov4.jpg (expiration not specified)
http://www.virology.ws/wp-content/plugins/sociable/images/closelabel.png (expiration not specified)
http://www.virology.ws/wp-content/plugins/sociable/images/more.png (expiration not specified)
http://www.virology.ws/wp-content/themes/thesis_186/custom/custom.css (expiration not specified)
http://www.virology.ws/wp-content/themes/thesis_18…irologyBlog_Banner.jpg (expiration not specified)
http://www.virology.ws/wp-content/themes/thesis_186/custom/layout.css (expiration not specified)
http://www.virology.ws/wp-content/uploads/2011/07/chicken_farm-300x225.jpg (expiration not specified)
http://www.virology.ws/wp-content/uploads/2015/07/9781555819514-300x206.jpg (expiration not specified)
http://www.virology.ws/wp-content/uploads/2015/07/FMD_note-300x220.jpg (expiration not specified)
http://www.virology.ws/wp-content/uploads/2015/07/…621-e1435875613184.jpg (expiration not specified)
http://www.virology.ws/wp-content/uploads/2015/08/IMG_5563-300x300.jpg (expiration not specified)
http://www.virology.ws/wp-content/uploads/2015/08/IMG_5584-150x150.jpg (expiration not specified)
http://www.virology.ws/wp-content/uploads/2015/08/arenavirus-300x288.png (expiration not specified)
http://www.virology.ws/wp-content/uploads/2015/08/filovirion.png (expiration not specified)
http://use.typekit.net/pdw2csb.js (10 minutes)
http://cdn.syndication.twitter.com/widgets/tweetbu…k=__twttr.receiveCount (15 minutes)
http://cdn.syndication.twitter.com/widgets/tweetbu…k=__twttr.receiveCount (15 minutes)
http://cdn.syndication.twitter.com/widgets/tweetbu…k=__twttr.receiveCount (15 minutes)
http://cdn.syndication.twitter.com/widgets/tweetbu…k=__twttr.receiveCount (15 minutes)
http://cdn.syndication.twitter.com/widgets/tweetbu…k=__twttr.receiveCount (15 minutes)
http://cdn.syndication.twitter.com/widgets/tweetbu…k=__twttr.receiveCount (15 minutes)
http://cdn.syndication.twitter.com/widgets/tweetbu…k=__twttr.receiveCount (15 minutes)
http://cdn.syndication.twitter.com/widgets/tweetbu…k=__twttr.receiveCount (15 minutes)
http://cdn.syndication.twitter.com/widgets/tweetbu…k=__twttr.receiveCount (15 minutes)
http://cdn.syndication.twitter.com/widgets/tweetbu…k=__twttr.receiveCount (15 minutes)
http://apis.google.com/js/plusone.js (30 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
https://apis.google.com/js/api.js (30 minutes)
https://apis.google.com/js/plusone.js (30 minutes)
https://oauth.googleusercontent.com/gadgets/js/cor…om:shindig.sha1.js?c=2 (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)
https://ssl.google-analytics.com/ga.js (2 hours)

priority - 15Reduce server response time

priority - 11Optimize images

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

Optimize the following images to reduce their size by 111.3KiB (19% reduction).

Losslessly compressing http://www.virology.ws/wp-content/uploads/2015/07/9781555819514-300x206.jpg could save 27KiB (52% reduction).
Losslessly compressing http://www.virology.ws/wp-content/themes/thesis_18…irologyBlog_Banner.jpg could save 24.5KiB (17% reduction).
Losslessly compressing http://www.urbanag.ws/urbag_square_200.jpg could save 12.5KiB (16% reduction).
Losslessly compressing http://www.virology.ws/wp-content/uploads/2015/08/filovirion.png could save 7.9KiB (20% reduction).
Losslessly compressing http://www.virology.ws/wp-content/uploads/2015/08/IMG_5563-300x300.jpg could save 7.6KiB (22% reduction).
Losslessly compressing http://www.virology.ws/wp-content/uploads/2015/08/IMG_5584-150x150.jpg could save 7.6KiB (50% reduction).
Losslessly compressing http://www.virology.ws/wp-content/uploads/2015/07/…621-e1435875613184.jpg could save 7.5KiB (30% reduction).
Losslessly compressing http://www.virology.ws/TWiV_200.jpg could save 5.4KiB (20% reduction).
Losslessly compressing http://www.twiv.tv/TWiM_AA_200.jpg could save 4.4KiB (19% reduction).
Losslessly compressing http://www.virology.ws/pov4.jpg could save 4.2KiB (18% reduction).
Losslessly compressing http://www.virology.ws/wp-content/uploads/2015/08/arenavirus-300x288.png could save 1.6KiB (3% reduction).
Losslessly compressing http://www.virology.ws/wp-content/uploads/2011/07/chicken_farm-300x225.jpg could save 1.2KiB (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 1.8KiB (2% reduction).

Minifying https://fbstatic-a.akamaihd.net/rsrc.php/v2/yD/r/biaA_H7UJVl.js could save 1.1KiB (2% reduction) after compression.
Minifying https://oauth.googleusercontent.com/gadgets/js/cor…om:shindig.sha1.js?c=2 could save 661B (3% 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.8KiB (36% reduction).

Minifying http://www.virology.ws/wp-content/themes/thesis_186/custom/layout.css could save 1.7KiB (27% reduction) after compression.
Minifying http://www.virology.ws/wp-content/themes/thesis_186/custom/custom.css could save 1.1KiB (75% reduction) after compression.

virology.ws Mobile Resource Breakdown

Total Resources119
Number of Hosts24
Static Resources53
JavaScript Resources37
CSS Resources8

virology.ws mobile page usability

Last tested: 2019-01-23


Mobile Usability Bad
63/100

virology.ws 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.

HOME renders only 3 pixels tall (11 CSS pixels).

THIS WEEK IN VIROLOGY and 6 others render only 3 pixels tall (11 CSS pixels).

Transgenic pig…-mouth disease and 15 others render only 7 pixels tall (22 CSS pixels).

16 AUGUST 2015 and 9 others render only 3 pixels tall (10 CSS pixels).

On the surface…hropomorphism. and 91 others render only 4 pixels tall (15 CSS pixels).

Principles of Virology and 7 others render only 4 pixels tall (15 CSS pixels).

Principles of Virology and 1 others render only 4 pixels tall (15 CSS pixels).

ability of the…to infect mice and 26 others render only 4 pixels tall (15 CSS pixels).

Tweet renders only 3 pixels tall (11 CSS pixels).

0 renders only 3 pixels tall (11 CSS pixels).

9 renders only 3 pixels tall (11 CSS pixels).

Patīk renders only 3 pixels tall (11 CSS pixels).

57 renders only 3 pixels tall (11 CSS pixels).

The genetic di…in the mouse. and 5 others render only 4 pixels tall (15 CSS pixels).

Tweet renders only 3 pixels tall (11 CSS pixels).
18 renders only 3 pixels tall (11 CSS pixels).
1 renders only 3 pixels tall (11 CSS pixels).
Patīk renders only 3 pixels tall (11 CSS pixels).
45 renders only 3 pixels tall (11 CSS pixels).
comments and 5 others render only 4 pixels tall (13 CSS pixels).
Tweet renders only 3 pixels tall (11 CSS pixels).
9 renders only 3 pixels tall (11 CSS pixels).
4 renders only 3 pixels tall (11 CSS pixels).
Patīk renders only 3 pixels tall (11 CSS pixels).
78 renders only 3 pixels tall (11 CSS pixels).
Tweet renders only 3 pixels tall (11 CSS pixels).
0 renders only 3 pixels tall (11 CSS pixels).
4 renders only 3 pixels tall (11 CSS pixels).
Patīk renders only 3 pixels tall (11 CSS pixels).
121 renders only 3 pixels tall (11 CSS pixels).
Because VSV ca…other viruses. renders only 4 pixels tall (15 CSS pixels).
7 renders only 3 pixels tall (12 CSS pixels).
Tweet renders only 3 pixels tall (11 CSS pixels).
22 renders only 3 pixels tall (11 CSS pixels).
22 renders only 3 pixels tall (11 CSS pixels).
Patīk renders only 3 pixels tall (11 CSS pixels).
11 renders only 3 pixels tall (11 CSS pixels).
Tweet renders only 3 pixels tall (11 CSS pixels).
0 renders only 3 pixels tall (11 CSS pixels).
3 renders only 3 pixels tall (11 CSS pixels).
Patīk renders only 3 pixels tall (11 CSS pixels).
70 renders only 3 pixels tall (11 CSS pixels).
Tweet renders only 3 pixels tall (11 CSS pixels).
21 renders only 3 pixels tall (11 CSS pixels).
5 renders only 3 pixels tall (11 CSS pixels).
Patīk renders only 3 pixels tall (11 CSS pixels).
140 renders only 3 pixels tall (11 CSS pixels).
This video can…current setup. renders only 5 pixels tall (16 CSS pixels).
Tweet renders only 3 pixels tall (11 CSS pixels).
21 renders only 3 pixels tall (11 CSS pixels).
0 renders only 3 pixels tall (11 CSS pixels).
Patīk renders only 3 pixels tall (11 CSS pixels).
161 renders only 3 pixels tall (11 CSS pixels).
Tweet renders only 3 pixels tall (11 CSS pixels).
0 renders only 3 pixels tall (11 CSS pixels).
4 renders only 3 pixels tall (11 CSS pixels).
Patīk renders only 3 pixels tall (11 CSS pixels).
71 renders only 3 pixels tall (11 CSS pixels).
Image credit renders only 4 pixels tall (13 CSS pixels).
Tweet renders only 3 pixels tall (11 CSS pixels).
10 renders only 3 pixels tall (11 CSS pixels).
0 renders only 3 pixels tall (11 CSS pixels).
Patīk renders only 3 pixels tall (11 CSS pixels).
54 renders only 3 pixels tall (11 CSS pixels).
← PREVIOUS ENTRIES renders only 3 pixels tall (10 CSS pixels).
Earth’s virology course and 6 others render only 4 pixels tall (13 CSS pixels).

Earth's virology Professor and 15 others render only 4 pixels tall (13 CSS pixels).

there is resea…to be done.... and 10 others render only 4 pixels tall (13 CSS pixels).

Content on thi…censed under a renders only 3 pixels tall (12 CSS pixels).
Creative Commo…on 3.0 License renders only 3 pixels tall (12 CSS pixels).

priority - 12Size 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://www.virology.ws">Home</a> is close to 1 other tap targets.

The tap target <a href="http://www.virology.ws/about/">About</a> and 6 others are close to other tap targets.

The tap target <a href="http://www.vir…atherine-high/">TWiV 350: Vira…Katherine High</a> and 6 others are close to other tap targets.

The tap target <a href="http://www.twi…8/16/twiv-350/">www.twiv.tv</a> and 6 others are close to other tap targets.

The tap target <a id="b" href="https://twitte…herine-high%2F" class="btn">Tweet</a> is close to 1 other tap targets.

The tap target <a id="count" href="https://twitte…herine-high%2F">0</a> is close to 2 other tap targets.

The tap target <div id="plusone" class="Jg">9</div> is close to 1 other tap targets.

The tap target <div id="plusone" class="Jg">9</div> is close to 4 other tap targets.

The tap target <html id="facebook" class="">FacebookPatīkPatīk5857</html> is close to 2 other tap targets.

The tap target <div class="pluginButton p…onDisconnected">Patīk</div> is close to 2 other tap targets.

The tap target <button type="submit"></button> is close to 3 other tap targets.

The tap target <a id="b" href="https://twitte…d-evolution%2F" class="btn">Tweet</a> is close to 3 other tap targets.
The tap target <a id="count" href="https://twitte…d-evolution%2F">18</a> is close to 3 other tap targets.
The tap target <div id="plusone" class="Jg">1</div> is close to 1 other tap targets.
The tap target <div id="plusone" class="Jg">1</div> is close to 3 other tap targets.
The tap target <html id="facebook" class="">FacebookPatīkPatīk4645</html> is close to 1 other tap targets.
The tap target <div class="pluginButton p…onDisconnected">Patīk</div> is close to 1 other tap targets.
The tap target <button type="submit"></button> is close to 2 other tap targets.
The tap target <a href="http://www.vir…tion/#comments">1 comment</a> and 5 others are close to other tap targets.
The tap target <a id="b" href="https://twitte…olioviruses%2F" class="btn">Tweet</a> is close to 3 other tap targets.
The tap target <a id="count" href="https://twitte…olioviruses%2F">9</a> is close to 3 other tap targets.
The tap target <div id="plusone" class="Jg">4</div> is close to 1 other tap targets.
The tap target <div id="plusone" class="Jg">4</div> is close to 3 other tap targets.
The tap target <html id="facebook" class="">FacebookPatīkPatīk7978</html> is close to 1 other tap targets.
The tap target <div class="pluginButton p…onDisconnected">Patīk</div> is close to 1 other tap targets.
The tap target <button type="submit"></button> is close to 2 other tap targets.
The tap target <a id="b" href="https://twitte…te-them-all%2F" class="btn">Tweet</a> is close to 1 other tap targets.
The tap target <a id="count" href="https://twitte…te-them-all%2F">0</a> is close to 2 other tap targets.
The tap target <div id="plusone" class="Jg">4</div> is close to 1 other tap targets.
The tap target <div id="plusone" class="Jg">4</div> is close to 4 other tap targets.
The tap target <html id="facebook" class="">FacebookPatīkPatīk122121</html> is close to 2 other tap targets.
The tap target <div class="pluginButton p…onDisconnected">Patīk</div> is close to 2 other tap targets.
The tap target <button type="submit"></button> is close to 3 other tap targets.
The tap target <a id="b" href="https://twitte…e-in-africa%2F" class="btn">Tweet</a> is close to 3 other tap targets.
The tap target <a id="count" href="https://twitte…e-in-africa%2F">22</a> is close to 3 other tap targets.
The tap target <div id="plusone" class="Jg">22</div> is close to 1 other tap targets.
The tap target <div id="plusone" class="Jg">22</div> is close to 3 other tap targets.
The tap target <html id="facebook" class="">FacebookPatīkPatīk1211</html> is close to 1 other tap targets.
The tap target <div class="pluginButton p…onDisconnected">Patīk</div> is close to 1 other tap targets.
The tap target <button type="submit"></button> is close to 2 other tap targets.
The tap target <a id="b" href="https://twitte…icken-shift%2F" class="btn">Tweet</a> is close to 1 other tap targets.
The tap target <a id="count" href="https://twitte…icken-shift%2F">0</a> is close to 2 other tap targets.
The tap target <div id="plusone" class="Jg">3</div> is close to 1 other tap targets.
The tap target <div id="plusone" class="Jg">3</div> is close to 4 other tap targets.
The tap target <html id="facebook" class="">FacebookPatīkPatīk7170</html> is close to 2 other tap targets.
The tap target <div class="pluginButton p…onDisconnected">Patīk</div> is close to 2 other tap targets.
The tap target <button type="submit"></button> is close to 3 other tap targets.
The tap target <a id="b" href="https://twitte…l-virulence%2F" class="btn">Tweet</a> is close to 3 other tap targets.
The tap target <a id="count" href="https://twitte…l-virulence%2F">21</a> is close to 3 other tap targets.
The tap target <div id="plusone" class="Jg">5</div> is close to 1 other tap targets.
The tap target <div id="plusone" class="Jg">5</div> is close to 3 other tap targets.
The tap target <html id="facebook" class="">FacebookPatīkPatīk141140</html> is close to 1 other tap targets.
The tap target <div class="pluginButton p…onDisconnected">Patīk</div> is close to 1 other tap targets.
The tap target <button type="submit"></button> is close to 2 other tap targets.
The tap target <a id="b" href="https://twitte…rth-edition%2F" class="btn">Tweet</a> is close to 7 other tap targets.
The tap target <a id="count" href="https://twitte…rth-edition%2F">21</a> is close to 7 other tap targets.
The tap target <div id="plusone" class="Jg">0</div> is close to 5 other tap targets.
The tap target <div id="plusone" class="Jg">0</div> is close to 7 other tap targets.
The tap target <html id="facebook" class="">FacebookPatīkPatīk162161</html> is close to 5 other tap targets.
The tap target <div class="pluginButton p…onDisconnected">Patīk</div> is close to 5 other tap targets.
The tap target <button type="submit"></button> is close to 6 other tap targets.
The tap target <a id="b" href="https://twitte…el-roulette%2F" class="btn">Tweet</a> is close to 1 other tap targets.
The tap target <a id="count" href="https://twitte…el-roulette%2F">0</a> is close to 2 other tap targets.
The tap target <div id="plusone" class="Jg">4</div> is close to 1 other tap targets.
The tap target <div id="plusone" class="Jg">4</div> is close to 4 other tap targets.
The tap target <html id="facebook" class="">FacebookPatīkPatīk7271</html> is close to 2 other tap targets.
The tap target <div class="pluginButton p…onDisconnected">Patīk</div> is close to 2 other tap targets.
The tap target <button type="submit"></button> is close to 3 other tap targets.
The tap target <a id="b" href="https://twitte…uth-disease%2F" class="btn">Tweet</a> is close to 3 other tap targets.
The tap target <a id="count" href="https://twitte…uth-disease%2F">10</a> is close to 3 other tap targets.
The tap target <div id="plusone" class="Jg">0</div> is close to 1 other tap targets.
The tap target <div id="plusone" class="Jg">0</div> is close to 3 other tap targets.
The tap target <html id="facebook" class="">FacebookPatīkPatīk5554</html> is close to 1 other tap targets.
The tap target <div class="pluginButton p…onDisconnected">Patīk</div> is close to 1 other tap targets.
The tap target <button type="submit"></button> is close to 2 other tap targets.
The tap target <a href="http://www.fac…weekinvirology">Facebook,</a> and 12 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.

virology.ws HTML validation

Errors

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

Line: 41 Column: 1 - 72
"...</script> <link rel='https://api.w.org/' href='http://www.virology.ws/wp-json/' /> <scri..."

Bad value “100%” for attribute “width” on element “iframe”: Expected a digit but saw “%” instead.

Line: 140 Column: 4 - 333
"...s.</p> <p><iframe src="//html5-player.libsyn.com/embed/episode/id/6004584/height/90/width/830/theme/custom/autonext/no/thumbnail/yes/autoplay/no/preload/no/no_addthis/no/direction/backward/no-cache/true/render-playlist/no/custom-color/166899/" width="100%" height="90" scrolling="no" allowfullscreen="allowfullscreen" data-mce-fragment="1">&lt;sp..." Line: 198 Column: 4 - 333
"...e.</p> <p><iframe src="//html5-player.libsyn.com/embed/episode/id/5979461/height/90/width/830/theme/custom/autonext/no/thumbnail/yes/autoplay/no/preload/no/no_addthis/no/direction/backward/no-cache/true/render-playlist/no/custom-color/166899/" width="100%" height="90" scrolling="no" allowfullscreen="allowfullscreen" data-mce-fragment="1">&lt;sp..." Line: 217 Column: 4 - 333
"...y.</p> <p><iframe src="//html5-player.libsyn.com/embed/episode/id/5978209/height/90/width/830/theme/custom/autonext/no/thumbnail/yes/autoplay/no/preload/no/no_addthis/no/direction/backward/no-cache/true/render-playlist/no/custom-color/166899/" width="100%" height="90" scrolling="no" allowfullscreen="allowfullscreen" data-mce-fragment="1">&lt;sp..." Line: 267 Column: 4 - 333
"...s.</p> <p><iframe src="//html5-player.libsyn.com/embed/episode/id/5959655/height/90/width/830/theme/custom/autonext/no/thumbnail/yes/autoplay/no/preload/no/no_addthis/no/direction/backward/no-cache/true/render-playlist/no/custom-color/166899/" width="100%" height="90" scrolling="no" allowfullscreen="allowfullscreen" data-mce-fragment="1">&lt;sp..."

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

Line: 140 Column: 4 - 333
"...s.</p> <p><iframe src="//html5-player.libsyn.com/embed/episode/id/6004584/height/90/width/830/theme/custom/autonext/no/thumbnail/yes/autoplay/no/preload/no/no_addthis/no/direction/backward/no-cache/true/render-playlist/no/custom-color/166899/" width="100%" height="90" scrolling="no" allowfullscreen="allowfullscreen" data-mce-fragment="1">&lt;sp..." Line: 198 Column: 4 - 333
"...e.</p> <p><iframe src="//html5-player.libsyn.com/embed/episode/id/5979461/height/90/width/830/theme/custom/autonext/no/thumbnail/yes/autoplay/no/preload/no/no_addthis/no/direction/backward/no-cache/true/render-playlist/no/custom-color/166899/" width="100%" height="90" scrolling="no" allowfullscreen="allowfullscreen" data-mce-fragment="1">&lt;sp..." Line: 217 Column: 4 - 333
"...y.</p> <p><iframe src="//html5-player.libsyn.com/embed/episode/id/5978209/height/90/width/830/theme/custom/autonext/no/thumbnail/yes/autoplay/no/preload/no/no_addthis/no/direction/backward/no-cache/true/render-playlist/no/custom-color/166899/" width="100%" height="90" scrolling="no" allowfullscreen="allowfullscreen" data-mce-fragment="1">&lt;sp..." Line: 267 Column: 4 - 333
"...s.</p> <p><iframe src="//html5-player.libsyn.com/embed/episode/id/5959655/height/90/width/830/theme/custom/autonext/no/thumbnail/yes/autoplay/no/preload/no/no_addthis/no/direction/backward/no-cache/true/render-playlist/no/custom-color/166899/" width="100%" height="90" scrolling="no" allowfullscreen="allowfullscreen" data-mce-fragment="1">&lt;sp..."

Text not allowed in element “iframe” in this context.

Line: 140 Column: 334 - 856
"...gment="1">&lt;span data-mce-type=&#8221;bookmark&#8221; class=&#8221;mce_SELRES_start&#8221;&gt;&lt;/span&gt;&amp;lt;span data-mce-type=&#8221;bookmark&#8221; style=&#8221;display: inline-block; width: 0px; overflow: hidden; line-height: 0;&#8221; class=&#8221;mce_SELRES_start&#8221;&amp;gt;&amp;lt;/span&amp;gt;&amp;amp;lt;span data-mce-type=&#8221;bookmark&#8221; style=&#8221;display: inline-block; width: 0px; overflow: hidden; line-height: 0;&#8221; class=&#8221;mce_SELRES_start&#8221;&amp;amp;gt;&amp;amp;lt;/span&amp;amp;gt;</ifra..." Line: 198 Column: 334 - 636
"...gment="1">&lt;span data-mce-type=&#8221;bookmark&#8221; class=&#8221;mce_SELRES_start&#8221;&gt;&lt;/span&gt;&amp;lt;span data-mce-type=&#8221;bookmark&#8221; style=&#8221;display: inline-block; width: 0px; overflow: hidden; line-height: 0;&#8221; class=&#8221;mce_SELRES_start&#8221;&amp;gt;&amp;lt;/span&amp;gt;</ifra..." Line: 217 Column: 334 - 432
"...gment="1">&lt;span data-mce-type=&#8221;bookmark&#8221; class=&#8221;mce_SELRES_start&#8221;&gt;&lt;/span&gt;</ifra..." Line: 267 Column: 334 - 432
"...gment="1">&lt;span data-mce-type=&#8221;bookmark&#8221; class=&#8221;mce_SELRES_start&#8221;&gt;&lt;/span&gt;</ifra..."

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

Line: 337 Column: 1 - 13
"...</script> <gcse:search></gcse..."

Warnings

Empty heading.

Line: 223 Column: 1 - 4
"...e</a></p> <h3></h3> ..."

Element name “gcse:search” cannot be represented as XML 1.0.

Line: 337 Column: 1 - 13
"...</script> <gcse:search></gcse..."

virology.ws similar domains

Similar domains:
www.virology.com
www.virology.net
www.virology.org
www.virology.info
www.virology.biz
www.virology.us
www.virology.mobi
www.irology.ws
www.virology.ws
www.cirology.ws
www.vcirology.ws
www.cvirology.ws
www.firology.ws
www.vfirology.ws
www.fvirology.ws
www.girology.ws
www.vgirology.ws
www.gvirology.ws
www.birology.ws
www.vbirology.ws
www.bvirology.ws
www.vrology.ws
www.vurology.ws
www.viurology.ws
www.vuirology.ws
www.vjrology.ws
www.vijrology.ws
www.vjirology.ws
www.vkrology.ws
www.vikrology.ws
www.vkirology.ws
www.vorology.ws
www.viorology.ws
www.voirology.ws
www.viology.ws
www.vieology.ws
www.vireology.ws
www.vierology.ws
www.vidology.ws
www.virdology.ws
www.vidrology.ws
www.vifology.ws
www.virfology.ws
www.vifrology.ws
www.vitology.ws
www.virtology.ws
www.vitrology.ws
www.virlogy.ws
www.virilogy.ws
www.viroilogy.ws
www.viriology.ws
www.virklogy.ws
www.viroklogy.ws
www.virkology.ws
www.virllogy.ws
www.virollogy.ws
www.virlology.ws
www.virplogy.ws
www.viroplogy.ws
www.virpology.ws
www.viroogy.ws
www.viropogy.ws
www.virolpogy.ws
www.virooogy.ws
www.viroloogy.ws
www.viroology.ws
www.virokogy.ws
www.virolkogy.ws
www.virolgy.ws
www.viroligy.ws
www.viroloigy.ws
www.viroliogy.ws
www.virolkgy.ws
www.virolokgy.ws
www.virollgy.ws
www.virololgy.ws
www.virolpgy.ws
www.virolopgy.ws
www.viroloy.ws
www.virolofy.ws
www.virologfy.ws
www.virolofgy.ws
www.virolovy.ws
www.virologvy.ws
www.virolovgy.ws
www.viroloty.ws
www.virologty.ws
www.virolotgy.ws
www.viroloby.ws
www.virologby.ws
www.virolobgy.ws
www.viroloyy.ws
www.virologyy.ws
www.viroloygy.ws
www.virolohy.ws
www.virologhy.ws
www.virolohgy.ws
www.virolog.ws
www.virologt.ws
www.virologyt.ws
www.virologg.ws
www.virologyg.ws
www.virologgy.ws
www.virologh.ws
www.virologyh.ws
www.virologu.ws
www.virologyu.ws
www.virologuy.ws

virology.ws 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.


virology.ws 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.