Show

Amung.us whos.amung.us - real-time stats!

Free real-time stats for your website or blog! No account setup required. Customize your widget today and get started!

Need help with your SEO?
Online Status
Offline

Server IP address resolved: No
Http response code: None
Last Checked: 09/16/2019

Amung.us receives about twenty thousand unique visitors and forty thousand pageviews per day. The estimated value of amung.us is seven hundred thousand USD. Each unique visitor makes about 1.84 pageviews on average.

Over the time amung.us has been ranked as high as 1,997 in the world, while most of its traffic comes from Brazil, where it reached as high as 2,399 position.

We recommend moving amung.us server from United States to Brazil, as it will speed up amung.us page load time for the majority of their users.

At the time of the last check (July 04, 2019) amung.us has a valid and up-to-date SSL certificate that expires on May 25, 2020.

According to Google Safe Browsing, Google Safe Search, Symantec and Web of Trust amung.us is quite a safe domain.

Mobile-Friendly test indicates that amung.us is well optimized for mobile and tablet devices.

Global Rank
18,302
Average Load Time
1.92sec
Links In Count
18,680
Website Value
$657,000
Overview
Last Updated: 09/22/2019
Overall result - "amung.us" is SAFE.
We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.
Norton Connect Safe
Last Updated: 01/12/2019
NCS "amung.us" OK.

Norton ConnectSafe evaluates amung.us for any unsafe and insecure content. The results are critical for families with young children.

Google Safe Search
Last Updated: 01/30/2019
GSS "amung.us" OK.

SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.

Google Safe Browsing
Last Updated: 01/09/2019
Malware not found at "amung.us".
"amung.us" is not a phishing page.
"amung.us" does not install unwanted software.
"amung.us" does not contain harmfull applications.
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.
Site Advisor
Last Updated: 01/09/2019
SA "amung.us" OK.

McAfee assesses amung.us for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze amung.us for mature or inappropriate content, only security checks are evaluated.

Web of Trust
Last Updated: 01/09/2019
WOT "amung.us" GOOD.

The WOT calculates reputation of the amung.us. This reputation system receives ratings from users and information from third-party sources, assesses the amung.us for safety features and confirms, whether amung.us is suitable for children.

SSL Information
Domain whos.amung.us
Issuer GeoTrust EV RSA CA 2018
Algorithm RSA-SHA256
Valid form 03/09/2018
Expiration 05/25/2020
Signed Certificate is not self signed
Additional Domains whos.amung.us
amung.us
assets.amung.us
waust.at
widgets.amung.us
www.amung.us
Server Location
Chicago
Illinois
United States
ASN Information

ASN ID: 32748
ASN Title: STEADFAST - Steadfast, US

Last Update: 05/29/2019

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

ASNumber: 32748
ASName: STEADFAST
ASHandle: AS32748
RegDate: 2004-07-16
Updated: 2016-08-11
Ref: https://rdap.arin.net/registry/autnum/32748

OrgName: Steadfast
OrgId: SNL-74
Address: 725 S Wells St
Address: 8th Floor
City: Chicago
StateProv: IL
PostalCode: 60607
Country: US
RegDate: 2016-02-04
Updated: 2017-01-28
Comment: Please submit all reports of abuse to
Comment: abuse@steadfast.net. Reports sent to
Comment: other addresses will not be processed.
Ref: https://rdap.arin.net/registry/entity/SNL-74

ReferralServer: rwhois://rwhois.steadfast.net:4321

OrgAbuseHandle: ABUSE959-ARIN
OrgAbuseName: Steadfast Networks Abuse Department
OrgAbusePhone: +1-312-602-2688
OrgAbuseEmail: abuse@steadfast.net
OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE959-ARIN

OrgTechHandle: NOG3-ARIN
OrgTechName: Steadfast Networks Network Operations Center
OrgTechPhone: +1-312-602-2689
OrgTechEmail: noc@steadfast.net
OrgTechRef: https://rdap.arin.net/registry/entity/NOG3-ARIN

OrgNOCHandle: NOG3-ARIN
OrgNOCName: Steadfast Networks Network Operations Center
OrgNOCPhone: +1-312-602-2689
OrgNOCEmail: noc@steadfast.net
OrgNOCRef: https://rdap.arin.net/registry/entity/NOG3-ARIN

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

%rwhois V-1.0,V-1.5:00090h:00 manage.steadfast.net (Ubersmith RWhois Server V-3.5.14)
%error 350 Invalid query syntax

HTML Metatags
Title
whos.amung.us - real-time stats!
The title has an optimal length. Search engines typically displays the first 50–70 characters of a title tag. If you keep your titles under 70 characters, our research suggests that you can expect about 90% of your titles to display properly.
Description
Free real-time stats for your website or blog! No account setup required. Customize your widget today and get started!
The description has optimal length. Keep in mind that the "optimal" length will vary depending on the situation, and your primary goal should be to provide value and drive clicks.
Encoding
UTF-8
You should always specify the encoding used for an HTML page. If you don't, you risk that characters in your content are incorrectly interpreted. This is not just an issue of human readability, increasingly machines need to understand your data too.
Language
en English
Identifying the language of your content allows you to automatically do a number of things, from changing the look and behavior of a page, to assisting search engines in extracting information. If part of the page uses text in a different language, you can add a language attribute with a different value to the element that surrounds that content.
Language Region
United States
Images
Attribute ALT
Line 114, ...<img src="//assets.amung.us/img/waulogox-white.png" class="logo-s...
Line 115, ...<img src="//assets.amung.us/img/waulogox.png" class="logo-scroll"...
Line 276, ...<img src="//assets.amung.us/img/codeboxes/wcolor.png">...
Line 279, ...<img src="//assets.amung.us/img/codeboxes/fcolor.png">...
Line 558, ...<img class="vam" src="//assets.amung.us/img/other/adchoices.png" ...
As a general rule, search engines do not interpret the content of image files. The text provided in the <img alt> attribute enables the site owner to provide relevant information to the search engine and to the end user.
H1-H6 Tags Information

For search engines, <H> tags helps understand the structure of the text on a page better. For users, headings are like anchors in a wall of text, navigating them through the page and making it easier to digest. The <h1> tag reinforces the core keyword(s) found in the <title>, <description>, and the <body>. We recommend that the <h1> tag includes keywords that reflect the contents of the page and that it is not longer than 150 characters in length, but don’t overuse the tags and the keywords in them. Keep it readable for users.

H1
The H1 tag is missing
Your H1 introduces the topic your page is all about, just as a title tells a reader what a book is all about. Add a header to the page by using a H1 tag and place it within the BODY of the page source.
H2
1 H2 tag(s).
The H2s are akin to book chapters, describing the main topics you’ll cover in sections of the article.
H3
2 H3 tag(s).
Subsequent headers, H3s to H6s, serve as additional sub-headings within each section, just as a book chapter may be split up by multiple sub-topics.
H4
H5
1 H5 tag(s).
H6
Iframes Information
iFrame
iFrames not found.
Since search engines consider the content in iframes to belong to another website, the best you can hope for is no effect on SEO. Iframes tend to neither help nor hurt your search engine ranking. For this reason, it’s best to refrain from using iframes on main pages that you want to rank high in search engine results. Instead, fill high-priority pages with useful, unique content and save iframes for other pages.
Code To Text Ratio
Code To Text Ratio
5.47 %
A good code to text ratio is anywhere from 25 to 70 percent. This percentage refers to the visible text ratio, as opposed to HTML elements, image tags and other non-visible information. This has become especially apparent since search engines, such as Google, released the Panda update which placed importance on content-driven sites.
Favicons

Favicons are the little piece of graphic that represents your brand on browser tabs, bookmark lists, search history, search ads and even search results. These files are placed in a file called favicon.ico and placed in the root directory of a website. There are no direct SEO effects of having favicons. However, there may be indirect benefits such as increased usability of site and bookmarks. It makes your website look more professional and help a users to remember your site while browsing through multiple URLs. If you want to get mentioned benefits you have to specify icons for different web browsers and sometimes even for different mobiles.

Default Favicon
Line 21, //assets.amung.us/img/favicon.png
Backup icon for most desktop browsers (if no icon of the right size is found). Tag format <link rel="shortcut icon" href="path-to-16x16-icon.ico" type="image/x-icon" />
16x16 Optional Favicon
Standard icon for outdated browsers or small resolution hand held devices. Tag format <link rel="icon" type="image/png" sizes="16x16" href="path-to-16x16.png">
32x32 Optional Favicon
Standard for most desktop browsers. Tag format <link rel="icon" sizes="32x32" href="path-to-32x32.png">
96x96 Optional Favicon
Mostly used as GoogleTV icon. Tag format <link rel="icon" type="image/png" sizes="96x96" href="path-to-96x96.png">
Default Apple Icon
Backup icon for apple devices (if no icon of the right size is found). Preferrable size 60x60. Tag format <link rel="apple-touch-icon" sizes="72x72" href="path-to-small-icon.png">
180x180 Apple Icon
iPhone 6 plus icons. Tag format <link rel="apple-touch-icon" sizes="180x180" href="path-to-180x180.png">
152x152 Apple Icon
iPad, iPad mini icons. Tag format <link rel="apple-touch-icon" sizes="152x152" href="path-to-icon-152x152.png">
167x167 Apple Icon
iPad Pro icon. Tag format <link rel="apple-touch-icon" sizes="167x167" href="path-to-167x167.png">
Robots.txt Information

Robots.txt is a text file that website owners can create to tell search engine bots how to crawl and index pages on their site.

Robots File
Robots File Loaded successfully (robots.txt)
You can have multiple lines of instructions to allow or disallow specific URLs and add multiple sitemaps. If you do not disallow a URL, then search engine bots assume that they are allowed to crawl it.
Disallow
Not found
Other User-Agent
Not found
Default User-Agent
1 record(s)
Sitemap

A sitemap is an XML file where is provided information about each URL: when it was last updated, how often it changes, and how important it is in relation to other URLs in the site. Search engines crawling bots read this file to more efficiently and intelligently crawl your site and to find URLs that may be isolated from rest of the site's content.

Default Sitemap
Sitemap File Loaded successfully (sitemap.xml)
Using a sitemap doesn't guarantee that all the items in your sitemap will be crawled and indexed, however, your site will benefit from having a sitemap.
WHOIS

Domain Name: amung.us
Registry Domain ID: D12150970-US
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: whois.godaddy.com
Updated Date: 2017-02-03T17:04:12Z
Creation Date: 2007-03-18T04:55:43Z
Registry Expiry Date: 2022-03-17T23:59:59Z
Registrar: GoDaddy.com, Inc.
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: C23426832-US
Registrant Name: Bart Bobrowski
Registrant Organization: whos.amung.us Inc
Registrant Street: 139 Cranleigh Manor SE
Registrant Street:
Registrant Street:
Registrant City: Calgary
Registrant State/Province: Alberta
Registrant Postal Code: T3M1J3
Registrant Country: ca
Registrant Phone: +1.8883046941
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: whos@amung.us
Registrant Application Purpose: P3
Registrant Nexus Category: C11
Registry Admin ID: C23426834-US
Admin Name: Bart Bobrowski
Admin Organization: whos.amung.us Inc
Admin Street: 139 Cranleigh Manor SE
Admin Street:
Admin Street:
Admin City: Calgary
Admin State/Province: Alberta
Admin Postal Code: T3M1J3
Admin Country: ca
Admin Phone: +1.8883046941
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: whos@amung.us
Admin Application Purpose: P3
Admin Nexus Category: C11
Registry Tech ID: C23426833-US
Tech Name: Bart Bobrowski
Tech Organization: whos.amung.us Inc
Tech Street: 139 Cranleigh Manor SE
Tech Street:
Tech Street:
Tech City: Calgary
Tech State/Province: Alberta
Tech Postal Code: T3M1J3
Tech Country: ca
Tech Phone: +1.8883046941
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: whos@amung.us
Tech Application Purpose: P3
Tech Nexus Category: C11
Name Server: ns2.amung.us
Name Server: ns6.amung.us
Name Server: ns4.amung.us
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2018-11-08T12:56:19Z

DNS Records
HostA RecordTTL
amung.us67.202.94.94300
amung.us67.202.94.86300
amung.us67.202.94.93300
HostMX RecordPriorityTTL
amung.usALT1.ASPMX.L.GOOGLE.COM20300
amung.usASPMX3.GOOGLEMAIL.COM30300
amung.usASPMX2.GOOGLEMAIL.COM30300
amung.usASPMX5.GOOGLEMAIL.COM30300
amung.usASPMX.L.GOOGLE.COM10300
amung.usALT2.ASPMX.L.GOOGLE.COM20300
amung.usASPMX4.GOOGLEMAIL.COM30300
HostNS RecordTTL
amung.usNS6.amung.us300
amung.usNS2.amung.us300
amung.usNS4.amung.us300
HostTXT RecordTTL

NS2.amung.us
TTL: 300
Email address: info.amung.us
Serial: 2019060301
Refresh: 10800
Retry: 3600
Expire: 604800
Minimum: 300

Errors
Line: 104 Column: 18 - 65
"... <span id="sel_lang_txt" class="tx" rel="uruwtm">Change..."
Line: 193 Column: 5 - 34
"..."dn"> <span class="tx" rel="my2j17"> ..."
Line: 229 Column: 18 - 47
"... <span class="tx" rel="y4hbxs">Copyri..."
Line: 229 Column: 93 - 122
"...us Inc. - <span class="tx" rel="k7na6a">All Ri..."
Line: 104 Column: 95 - 187
"...e:</span> <img id="active_lang_flag" class="vam" src="http://assets.amung.us/images/flags/16/us.png" /> ..."
Line: 130 Column: 59 - 121
"...="ius4jl"><img src="http://assets.amung.us/images/header/prologin.png" /></a> ..."
Line: 135 Column: 14 - 78
"... <img src="http://assets.amung.us/images/header/headerlogo.png" /> ..."
Line: 154 Column: 9 - 99
"...> <img src="http://assets.amung.us/images/home/splashpreview.png" class="splashpreviewpos" /> <..."
Line: 176 Column: 17 - 50
"... <img src="/widget/dzsg93pq.png" /> ..."
Line: 200 Column: 9 - 95
"...> <img class="vam" src="http://assets.amung.us/images/other/adchoices.png" height="12" /> <..."
Line: 108 Column: 14 - 45
"... <a rel="ar:sa:rtl:,." href="#">عربي</..."
Line: 109 Column: 17 - 51
"... <a rel="zh-CN:cn:ltr:,." href="#">简体</a>..."
Line: 110 Column: 17 - 51
"... <a rel="zh-TW:cn:ltr:,." href="#">繁體</a>..."
Line: 111 Column: 5 - 37
"...8226; <a rel="en:us:ltr:,." href="#">Englis..."
Line: 112 Column: 5 - 37
"...8226; <a rel="es:es:ltr: ," href="#">Españo..."
Line: 113 Column: 17 - 49
"... <a rel="fr:fr:ltr: ," href="#">França..."
Line: 114 Column: 17 - 49
"... <a rel="de:de:ltr: ," href="#">Deutsc..."
Line: 115 Column: 17 - 49
"... <a rel="el:gr:ltr: ," href="#">Ελληνι..."
Line: 116 Column: 5 - 36
"...8226; <a rel="id:id:ltr: ," href="#">Indone..."
Line: 117 Column: 17 - 49
"... <a rel="it:it:ltr: ," href="#">Italia..."
Line: 118 Column: 5 - 37
"...8226; <a rel="ja:jp:ltr:,." href="#">日本語</a..."
Line: 119 Column: 17 - 49
"... <a rel="ko:kr:ltr:,." href="#">한국어</a..."
Line: 120 Column: 5 - 37
"...8226; <a rel="nl:nl:ltr: ," href="#">Nederl..."
Line: 121 Column: 17 - 49
"... <a rel="pl:pl:ltr: ," href="#">Polski..."
Line: 122 Column: 17 - 48
"... <a rel="pt:br:ltr: ," href="#">Portug..."
Line: 123 Column: 17 - 49
"... <a rel="ru:ru:ltr: ," href="#">Русски..."
Line: 124 Column: 17 - 49
"... <a rel="tr:tr:ltr: ," href="#">Türkçe..."
Line: 125 Column: 5 - 36
"...8226; <a rel="vi:vn:ltr:,." href="#">tiếng ..."
Line: 127 Column: 4 - 79
"...</div> <div class="tx" id="lang_bar_text_lang" style="display: none;" rel="uruwtm">Change..."
Line: 157 Column: 1 - 90
"...a> </div> <div class="ptext tx" style="float:left; width:600px; margin:50px 0 0 25px;" rel="01uqus"> If yo..."
Line: 166 Column: 1 - 35
"...ed.</h1> <div class="ptext tx" rel="duzo8a"> Insta..."
Line: 188 Column: 1 - 35
"...ore?</h1> <div class="ptext tx" rel="htuygt"> Get m..."
Line: 206 Column: 5 - 48
"..."dn"> <div id="tiptitles" class="tx" rel="1b2lqk">Click ..."
Line: 207 Column: 5 - 49
".../div> <div id="wibiya_txt" class="tx" rel="wrhqra">Try us..."
Line: 208 Column: 5 - 51
".../div> <div id="no_flash_txt" class="tx" rel="wj3f4w">DOUBLE..."
Line: 209 Column: 5 - 57
".../div> <div id="codebox_header_txt" class="tx" rel="974fqx">COPY T..."
Line: 210 Column: 5 - 52
".../div> <div id="codebox_p_txt" class="tx" rel="ldwowx">By usi..."
Line: 130 Column: 13 - 58
"... <a class="tx" href="/pro/login/" rel="ius4jl"><img s..."
Line: 131 Column: 13 - 58
"... <a class="tx" href="/pro/login/" rel="8ulh7l">Pro Lo..."
Line: 151 Column: 1 - 28
"...nt"> <h1 class="tx" rel="6phnzx">Free r..."
Line: 164 Column: 1 - 28
"...sp;</div> <h1 class="tx" rel="bxw09t">Gettin..."
Line: 187 Column: 1 - 28
"...sp;</div> <h1 class="tx" rel="5e0tm4">Want e..."
Line: 220 Column: 21 - 62
"... <a href="/about/" class="tx" rel="0n55c5">About<..."
Line: 221 Column: 6 - 46
"...> | <a href="/blog/" class="tx" rel="gbvehm">News</..."
Line: 222 Column: 21 - 64
"... <a href="/contact/" class="tx" rel="742zxn">Contac..."
Line: 223 Column: 21 - 61
"... <a href="/help/" class="tx" rel="hjrlu3">Help</..."
Line: 224 Column: 21 - 62
"... <a href="/legal/" class="tx" rel="pa21rb">Legal/..."
Line: 225 Column: 21 - 70
"... <a href="/legal/privacy/" class="tx" rel="isyoyb">Privac..."
Line: 226 Column: 21 - 65
"... <a href="/showcase/" class="tx" rel="temot3">Get St..."

Last tested: 05/23/2017

Desktop
Desktop Speed
76%
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://s7.addthis.com/js/250/addthis_widget.js (10 minutes)
http://assets.amung.us/images/backgrounds/default.png (24 hours)
http://assets.amung.us/images/backgrounds/footer.png (24 hours)
http://assets.amung.us/images/codeboxes/pixel_darker.png (24 hours)
http://assets.amung.us/images/flags/16/us.png (24 hours)
http://assets.amung.us/images/header/headerback.png (24 hours)
http://assets.amung.us/images/header/headerlogo.png (24 hours)
http://assets.amung.us/images/header/nav_help_off.png (24 hours)
http://assets.amung.us/images/header/nav_home_off.png (24 hours)
http://assets.amung.us/images/header/nav_home_on.png (24 hours)
http://assets.amung.us/images/header/nav_pro_off.png (24 hours)
http://assets.amung.us/images/header/nav_stats_off.png (24 hours)
http://assets.amung.us/images/header/nav_widgets_off.png (24 hours)
http://assets.amung.us/images/header/prologin.png (24 hours)
http://assets.amung.us/images/home/splashpreview.png (24 hours)
http://assets.amung.us/images/other/adchoices.png (24 hours)
http://assets.amung.us/scripts/3rdparty/featherlight.min.js (24 hours)
http://assets.amung.us/scripts/3rdparty/moocore.js (24 hours)
http://assets.amung.us/scripts/3rdparty/moomore.js (24 hours)
http://assets.amung.us/scripts/3rdparty/syntaxhighlighter.js (24 hours)
http://assets.amung.us/scripts/3rdparty/zeroclipboard.js (24 hours)
http://assets.amung.us/scripts/global.js (24 hours)
http://assets.amung.us/scripts/showcase.js (24 hours)
http://assets.amung.us/styles/3rdparty/featherlight.min.css (24 hours)
http://assets.amung.us/styles/3rdparty/syntaxhighlighter.css (24 hours)
http://assets.amung.us/styles/global.css (24 hours)
http://assets.amung.us/styles/showcase.css (24 hours)
http://widgets.amung.us/_blank.gif (24 hours)
http://widgets.amung.us/a_pro.js (24 hours)

Your page has 4 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

http://assets.amung.us/styles/3rdparty/featherlight.min.css
http://assets.amung.us/styles/global.css
http://fonts.googleapis.com/css?family=Ubuntu:300|…cyrillic-ext,latin-ext
http://fonts.googleapis.com/css?family=Ubuntu+Condensed

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 41.3KiB (50% reduction).

Minifying http://code.jquery.com/jquery-latest.js could save 41.3KiB (50% reduction) after compression.

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 8.1KiB (40% reduction).

Compressing http://assets.amung.us/images/header/nav_widgets_off.png could save 1.3KiB (37% reduction).
Compressing http://assets.amung.us/images/header/nav_home_off.png could save 1KiB (42% reduction).
Compressing http://assets.amung.us/images/header/nav_stats_off.png could save 1KiB (40% reduction).
Compressing http://assets.amung.us/images/header/nav_help_off.png could save 981B (42% reduction).
Compressing http://assets.amung.us/images/header/nav_pro_off.png could save 899B (42% reduction).
Compressing http://assets.amung.us/images/header/prologin.png could save 884B (64% reduction).
Compressing http://assets.amung.us/images/codeboxes/pixel_darker.png could save 852B (92% reduction).
Compressing http://assets.amung.us/images/header/nav_home_on.png could save 717B (24% reduction).
Compressing http://assets.amung.us/images/other/adchoices.png could save 558B (23% reduction).

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 738B (58% reduction).

Compressing http://assets.amung.us/styles/3rdparty/featherlight.min.css could save 738B (58% reduction).

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 556B (15% reduction).

Minifying http://whos.amung.us/ could save 556B (15% reduction) after compression.

Desktop Resource Breakdown
Total Resources44
Number of Hosts10
Static Resources33
JavaScript Resources14
CSS Resources6

Last tested: 05/20/2017

Mobile
Mobile Usability
81%
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.
Configure a viewport for this page.
The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.
The page content is 1,000 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <div id="langbar">عربي •…Site Language:</div> falls outside the viewport.
The element <li id="nav_help"> falls outside the viewport.
The element <div id="headspacer" class="clear"> falls outside the viewport.
The element <h1 class="tx">Free real-time…bsite or blog.</h1> falls outside the viewport.
The element <div class="ptext tx">If you have a…or learn more.</div> falls outside the viewport.
The element <div class="clear"></div> falls outside the viewport.
The element <h1 class="tx">Getting started.</h1> falls outside the viewport.
The element <div class="ptext tx">Installing sta…n our gallery.</div> falls outside the viewport.
The element <div id="dyn_txt_codebox_header_93723" class="codebox_header">COPY THIS CODE TO YOUR SITE:</div> falls outside the viewport.
The element <div class="line number1 index0 alt2">&lt;script id=&quot;_w…k3p&quot;, &quot;ncd&quot;]);</div> falls outside the viewport.
The element <div class="line number2 index1 alt1">(function() {v…s.async=true;</div> falls outside the viewport.
The element <div class="line number3 index2 alt2">s.src=&quot;//widge…s/classic.js&quot;;</div> falls outside the viewport.
The element <div class="line number4 index3 alt1">document.getEl…ppendChild(s);</div> falls outside the viewport.
The element <div class="line number5 index4 alt2">})();&lt;/script&gt;</div> falls outside the viewport.
The element <div id="dyn_text_no_flash_txt_24873" class="fr no_flash_txt">DOUBLE CLICK O…TO SELECT ALL</div> falls outside the viewport.
The element <div class="clear"></div> falls outside the viewport.
The element <div class="clear"></div> falls outside the viewport.
The element <h1 class="tx">Want even more?</h1> falls outside the viewport.
The element <div class="ptext tx">Get more stats…a Pro account.</div> falls outside the viewport.
The element <div class="border">About |…558KShare</div> falls outside the viewport.

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="javascript:void(0)"></a> is close to 1 other tap targets final.
The tap target <a href="/pro/login/" class="tx"></a> is close to 2 other tap targets final.
The tap target <a href="/pro/login/" class="tx">Pro Login</a> is close to 1 other tap targets final.
The tap target <a href="/about/" class="tx">About</a> and 3 others are close to other tap targets final.
The tap target <a href="#" class="addthis_button…erred_2 at300b"></a> and 2 others are close to other tap targets final.

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.

Pro Login renders only 4 pixels tall (11 CSS pixels) final.
DOUBLE CLICK O…TO SELECT ALL and 1 others render only 4 pixels tall (11 CSS pixels) final.
1 and 4 others render only 5 pixels tall (12 CSS pixels) final.
&lt;script id=&quot;_wauncd&quot;&gt; and 1 others render only 5 pixels tall (12 CSS pixels) final.
function and 3 others render only 5 pixels tall (12 CSS pixels) final.
_wau = _wau || []; _wau.push([ and 13 others render only 5 pixels tall (12 CSS pixels) final.
&quot;//widgets.amu…us/classic.js&quot; and 5 others render only 5 pixels tall (12 CSS pixels) final.
Privacy Policy and 6 others render only 6 pixels tall (15 CSS pixels) final.
| and 5 others render only 6 pixels tall (15 CSS pixels) final.
All Rights Reserved. and 1 others render only 5 pixels tall (12 CSS pixels) final.
↓ 3,283.65B ⋅ 2.41M ↑ and 1 others render only 5 pixels tall (12 CSS pixels) final.
558K renders only 6 pixels tall (16 CSS pixels) final.

Mobile Speed
60%
Your page has 4 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

http://assets.amung.us/styles/3rdparty/featherlight.min.css
http://assets.amung.us/styles/global.css
http://fonts.googleapis.com/css?family=Ubuntu:300|…cyrillic-ext,latin-ext
http://fonts.googleapis.com/css?family=Ubuntu+Condensed

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://s7.addthis.com/js/250/addthis_widget.js (10 minutes)
http://assets.amung.us/images/backgrounds/default.png (24 hours)
http://assets.amung.us/images/backgrounds/footer.png (24 hours)
http://assets.amung.us/images/codeboxes/pixel_darker.png (24 hours)
http://assets.amung.us/images/flags/16/us.png (24 hours)
http://assets.amung.us/images/header/headerback.png (24 hours)
http://assets.amung.us/images/header/headerlogo.png (24 hours)
http://assets.amung.us/images/header/nav_help_off.png (24 hours)
http://assets.amung.us/images/header/nav_home_off.png (24 hours)
http://assets.amung.us/images/header/nav_home_on.png (24 hours)
http://assets.amung.us/images/header/nav_pro_off.png (24 hours)
http://assets.amung.us/images/header/nav_stats_off.png (24 hours)
http://assets.amung.us/images/header/nav_widgets_off.png (24 hours)
http://assets.amung.us/images/header/prologin.png (24 hours)
http://assets.amung.us/images/home/splashpreview.png (24 hours)
http://assets.amung.us/images/other/adchoices.png (24 hours)
http://assets.amung.us/scripts/3rdparty/featherlight.min.js (24 hours)
http://assets.amung.us/scripts/3rdparty/moocore.js (24 hours)
http://assets.amung.us/scripts/3rdparty/moomore.js (24 hours)
http://assets.amung.us/scripts/3rdparty/syntaxhighlighter.js (24 hours)
http://assets.amung.us/scripts/3rdparty/zeroclipboard.js (24 hours)
http://assets.amung.us/scripts/global.js (24 hours)
http://assets.amung.us/scripts/showcase.js (24 hours)
http://assets.amung.us/styles/3rdparty/featherlight.min.css (24 hours)
http://assets.amung.us/styles/3rdparty/syntaxhighlighter.css (24 hours)
http://assets.amung.us/styles/global.css (24 hours)
http://assets.amung.us/styles/showcase.css (24 hours)
http://widgets.amung.us/_blank.gif (24 hours)
http://widgets.amung.us/a_pro.js (24 hours)

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 41.3KiB (50% reduction).

Minifying http://code.jquery.com/jquery-latest.js could save 41.3KiB (50% reduction) after compression.

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 8.1KiB (40% reduction).

Compressing http://assets.amung.us/images/header/nav_widgets_off.png could save 1.3KiB (37% reduction).
Compressing http://assets.amung.us/images/header/nav_home_off.png could save 1KiB (42% reduction).
Compressing http://assets.amung.us/images/header/nav_stats_off.png could save 1KiB (40% reduction).
Compressing http://assets.amung.us/images/header/nav_help_off.png could save 981B (42% reduction).
Compressing http://assets.amung.us/images/header/nav_pro_off.png could save 899B (42% reduction).
Compressing http://assets.amung.us/images/header/prologin.png could save 884B (64% reduction).
Compressing http://assets.amung.us/images/codeboxes/pixel_darker.png could save 852B (92% reduction).
Compressing http://assets.amung.us/images/header/nav_home_on.png could save 717B (24% reduction).
Compressing http://assets.amung.us/images/other/adchoices.png could save 558B (23% reduction).

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 738B (58% reduction).

Compressing http://assets.amung.us/styles/3rdparty/featherlight.min.css could save 738B (58% reduction).

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 557B (15% reduction).

Minifying http://whos.amung.us/ could save 557B (15% reduction) after compression.

Mobile Resource Breakdown
Total Resources45
Number of Hosts10
Static Resources34
JavaScript Resources15
CSS Resources6
www.amung.com
www.amung.net
www.amung.org
www.amung.info
www.amung.biz
www.amung.us
www.amung.mobi
www.mung.us
www.amung.us
www.qmung.us
www.aqmung.us
www.qamung.us
www.wmung.us
www.awmung.us
www.wamung.us
www.smung.us
www.asmung.us
www.samung.us
www.zmung.us
www.azmung.us
www.zamung.us
www.aung.us
www.anung.us
www.amnung.us
www.anmung.us
www.ajung.us
www.amjung.us
www.ajmung.us
www.akung.us
www.amkung.us
www.akmung.us
www.amng.us
www.amyng.us
www.amuyng.us
www.amyung.us
www.amhng.us
www.amuhng.us
www.amhung.us
www.amjng.us
www.amujng.us
www.aming.us
www.amuing.us
www.amiung.us
www.amug.us
www.amubg.us
www.amunbg.us
www.amubng.us
www.amuhg.us
www.amunhg.us
www.amujg.us
www.amunjg.us
www.amumg.us
www.amunmg.us
www.amumng.us
www.amun.us
www.amunf.us
www.amungf.us
www.amunfg.us
www.amunv.us
www.amungv.us
www.amunvg.us
www.amunt.us
www.amungt.us
www.amuntg.us
www.amunb.us
www.amungb.us
www.amuny.us
www.amungy.us
www.amunyg.us
www.amunh.us
www.amungh.us