lexic.us Website Information
Daily Unique Visits: 1,359
Daily Page Views: 2,718
Income Per Day: $8
Estimated Value: $1,920
This website is located in United States and is using following IP address 64.50.164.160. See the complete list of popular websites hosted in United States.
lexic.us is registered under .US top-level domain. Please check other sites in .US zone.
Website lexic.us is using the following name servers:
- pdns06.domaincontrol.com
- pdns05.domaincontrol.com
and is probably hosted by PRIVATESYSTEMS - PrivateSystems Networks, US. See the full list of other websites hosted by PRIVATESYSTEMS - PrivateSystems Networks, US.
The highest website lexic.us position in Alexa rank database was 114115 and the lowest rank position was 998511. Current position of lexic.us in Alexa rank database is 527572.
Desktop speed score of lexic.us (83/100) is better than the results of 76.15% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of lexic.us (62/100) is better than the results of 7.29% of other sites and means that the page is not mobile-friendly.
Mobile speed score of lexic.us (66/100) is better than the results of 68.49% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
lexic.us 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.
lexic.us 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.
Registry Domain ID: D12048632-US
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: whois.godaddy.com
Updated Date: 2024-03-07T16:45:30Z
Creation Date: 2007-03-02T05:12:55Z
Registry Expiry Date: 2025-03-01T23:59:59Z
Registrar: GoDaddy.com, LLC
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: C40806670-US
Registrant Name: Stephen Ryder
Registrant Organization:
Registrant Street: PO Box 950429
Registrant Street:
Registrant Street:
Registrant City: Lake Mary
Registrant State/Province: Florida
Registrant Postal Code: 32795
Registrant Country: US
Registrant Phone: +1.3213480708
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: admin@puzzlebaron.com
Registrant Application Purpose: P3
Registrant Nexus Category: C11
Registry Admin ID: C40806674-US
Admin Name: Stephen Ryder
Admin Organization:
Admin Street: PO Box 950429
Admin Street:
Admin Street:
Admin City: Lake Mary
Admin State/Province: Florida
Admin Postal Code: 32795
Admin Country: US
Admin Phone: +1.3213480708
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: admin@puzzlebaron.com
Admin Application Purpose: P3
Admin Nexus Category: C11
Registry Tech ID: C40806672-US
Tech Name: Stephen Ryder
Tech Organization:
Tech Street: PO Box 950429
Tech Street:
Tech Street:
Tech City: Lake Mary
Tech State/Province: Florida
Tech Postal Code: 32795
Tech Country: US
Tech Phone: +1.3213480708
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: admin@puzzlebaron.com
Tech Application Purpose: P3
Tech Nexus Category: C11
Name Server: pdns05.domaincontrol.com
Name Server: pdns06.domaincontrol.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2024-10-22T11:18:45Z
lexic.us server information
Servers Location
lexic.us desktop page speed rank
Last tested: 2019-01-10
lexic.us Desktop Speed Test Quick Summary
priority - 10Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
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:
https://dmx.districtm.io/s/10007/AAACIhGqURkf-gNvB…em61WpYWI6nGfBL9mBvO1R (expiration not specified)
https://dmx.districtm.io/s/10009/e8514c01-4546-417d-b812-4b77d6f8dec4 (expiration not specified)
https://dmx.districtm.io/s/10016/XDaPBwAAAMmpaBZD&_test=XDaPBwAAAMmpaBZD (expiration not specified)
https://dmx.districtm.io/s/10023/959337090207245790 (expiration not specified)
https://dmx.districtm.io/s/v1/buyers (expiration not specified)
https://static.adsafeprotected.com/skeleton.js (expiration not specified)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://www.googletagservices.com/activeview/js/cu…osd.js?cb=%2Fr20100101 (50 minutes)
https://www.googletagservices.com/activeview/js/cu…ner.js?cache=r20110914 (50 minutes)
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://tags.expo9.exponential.com/tags/Cryptogramsorg/lexicus/tags.js (60 minutes)
https://secure-assets.rubiconproject.com/utils/xapi/multi-sync.js (3.1 hours)
https://cdn.districtm.ca/merge/merge.v4.2.111810.js (4 hours)
https://cdn.districtm.io/ids/idsync.9a20a03c.js (4 hours)
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 5.3KiB (23% reduction).
Minifying https://www.google-analytics.com/urchin.js could save 975B (15% reduction) after compression.
Minifying https://cdnx.tribalfusion.com/media/8238626/Main.js could save 291B (14% reduction) after compression.
Minifying https://cdnx.tribalfusion.com/media/common/adChoice/tf_adChoice11.js could save 177B (18% reduction) after compression.
priority - 0Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 1.8KiB (30% reduction).
Compressing https://tpc.googlesyndication.com/daca_images/simg…3916589033?w=195&h=102 could save 764B (18% reduction).
Compressing https://cdnx.tribalfusion.com/media/common//adChoi…on/ad_choices_i_UR.png could save 247B (49% reduction).
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 1.4KiB (60% reduction).
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.3KiB (17% reduction).
Minifying https://cdnx.tribalfusion.com/media/8238626/Main.h…p%3A//1x1pixelurl.com/ could save 496B (31% reduction) after compression.
lexic.us Desktop Resource Breakdown
Total Resources | 242 |
Number of Hosts | 81 |
Static Resources | 49 |
JavaScript Resources | 47 |
CSS Resources | 2 |
lexic.us mobile page speed rank
Last tested: 2019-01-10
lexic.us Mobile Speed Test Quick Summary
priority - 40Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
priority - 11Leverage 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:
https://dmx.districtm.io/s/10007/AAACKSynmpc3PwNh3…LsOuSRs0hzFp5J9aBShQ03 (expiration not specified)
https://dmx.districtm.io/s/10009/dc858bd7-06db-4667-b31a-2b9e5826843b (expiration not specified)
https://dmx.districtm.io/s/10022/432240058549 (expiration not specified)
https://dmx.districtm.io/s/10023/968062829366200412 (expiration not specified)
https://dmx.districtm.io/s/v1/buyers (expiration not specified)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://www.googletagservices.com/activeview/js/cu…dar.js?cache=r20110914 (50 minutes)
https://www.googletagservices.com/activeview/js/cu…osd.js?cb=%2Fr20100101 (50 minutes)
https://www.googletagservices.com/activeview/js/cu…ner.js?cache=r20110914 (50 minutes)
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://tags.expo9.exponential.com/tags/Cryptogramsorg/lexicus/tags.js (60 minutes)
https://www.googletagservices.com/dcm/dcmads.js (60 minutes)
https://secure-assets.rubiconproject.com/utils/xapi/multi-sync.js (3.8 hours)
https://cdn.districtm.ca/merge/merge.v4.2.111810.js (4 hours)
https://cdn.districtm.io/ids/idsync.9a20a03c.js (4 hours)
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 5.4KiB (24% reduction).
Minifying https://www.google-analytics.com/urchin.js could save 975B (15% reduction) after compression.
Minifying https://p.cpx.to/p/11724/px.js could save 392B (27% reduction).
Minifying https://cdnx.tribalfusion.com/media/common/adChoice/tf_adChoice11.js could save 177B (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 2.5KiB (56% reduction).
Compressing https://p.cpx.to/p/11724/px.js could save 848B (56% reduction).
Compressing https://tag.apxlv.com/tag/partner/213?id=39e63b921cd450a27b2f3ac0 could save 267B (44% reduction).
priority - 0Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 1KiB (11% reduction).
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 858B (14% reduction).
lexic.us Mobile Resource Breakdown
Total Resources | 240 |
Number of Hosts | 87 |
Static Resources | 54 |
JavaScript Resources | 61 |
CSS Resources | 1 |
lexic.us mobile page usability
Last tested: 2019-01-10
lexic.us Mobile Usability Test Quick Summary
priority - 31Use 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.
Welcome to Lexicus
renders only 8 pixels tall (20 CSS pixels).Lexicus is an…h information.
and 53 others render only 5 pixels tall (12 CSS pixels).The MCAT is Ju…US and Canada.
renders only 5 pixels tall (12 CSS pixels).go.auamed.org
renders only 5 pixels tall (12 CSS pixels).OPEN
renders only 5 pixels tall (13 CSS pixels).Words people a…ing for today:
renders only 5 pixels tall (12 CSS pixels).glycine_hydrox…hyltransferase
and 52 others render only 5 pixels tall (12 CSS pixels).Search
renders only 5 pixels tall (14 CSS pixels).priority - 24Size 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.
<div id="abgc" class="abgc"></div>
is close to 1 other tap targets.<div id="abgc" class="abgc"></div>
is close to 1 other tap targets.<a href="/definition-of…fty-cent_piece">fifty-cent_piece</a>
and 52 others are close to other tap targets.<input type="submit" name="Submit" class="submitbox">
is close to 1 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.
lexic.us HTML validation
Errors
Start tag seen without seeing a doctype first. Expected “<!DOCTYPE html>”.
"...<html> <head..."
The “align” attribute on the “div” element is obsolete. Use CSS instead.
"...d> <body> <div id="leaderboard" align="right"><div i..." Line: 872 Column: 5 - 72
"...box"> <div class="sidebar" align="center" style="padding:0px !important;"> <!-- ..."
The “cellspacing” attribute on the “table” element is obsolete. Use CSS instead.
"...1"></a> <table border="0" cellspacing="0" cellpadding="0" align="right" width="305" style="margin-top: 25px; margin-left: 15px; margin-bottom: 15px"> <tr><..."
The “cellpadding” attribute on the “table” element is obsolete. Use CSS instead.
"...1"></a> <table border="0" cellspacing="0" cellpadding="0" align="right" width="305" style="margin-top: 25px; margin-left: 15px; margin-bottom: 15px"> <tr><..."
The “align” attribute on the “table” element is obsolete. Use CSS instead.
"...1"></a> <table border="0" cellspacing="0" cellpadding="0" align="right" width="305" style="margin-top: 25px; margin-left: 15px; margin-bottom: 15px"> <tr><..."
The “width” attribute on the “table” element is obsolete. Use CSS instead.
"...1"></a> <table border="0" cellspacing="0" cellpadding="0" align="right" width="305" style="margin-top: 25px; margin-left: 15px; margin-bottom: 15px"> <tr><..."
The “border” attribute on the “table” element is obsolete. Use CSS instead.
"...1"></a> <table border="0" cellspacing="0" cellpadding="0" align="right" width="305" style="margin-top: 25px; margin-left: 15px; margin-bottom: 15px"> <tr><..."
The “size” attribute on the “hr” element is obsolete. Use CSS instead.
"...a> <p> <hr size=1 color=silver> <p><..."
The “color” attribute on the “hr” element is obsolete. Use CSS instead.
"...a> <p> <hr size=1 color=silver> <p><..."
Stray end tag “div”.
"... </div> </div> <scr..."
Warnings
The “name” attribute is obsolete. Consider putting an “id” attribute on the nearest container instead.
"...Content"> <a name="1"></a> ..."
lexic.us similar domains
www.lexic.net
www.lexic.org
www.lexic.info
www.lexic.biz
www.lexic.us
www.lexic.mobi
www.exic.us
www.lexic.us
www.pexic.us
www.lpexic.us
www.plexic.us
www.oexic.us
www.loexic.us
www.olexic.us
www.kexic.us
www.lkexic.us
www.klexic.us
www.lxic.us
www.lwxic.us
www.lewxic.us
www.lwexic.us
www.lsxic.us
www.lesxic.us
www.ldxic.us
www.ledxic.us
www.ldexic.us
www.lrxic.us
www.lerxic.us
www.lrexic.us
www.leic.us
www.lezic.us
www.lexzic.us
www.lezxic.us
www.lesic.us
www.lexsic.us
www.ledic.us
www.lexdic.us
www.lecic.us
www.lexcic.us
www.lecxic.us
www.lexc.us
www.lexuc.us
www.lexiuc.us
www.lexuic.us
www.lexjc.us
www.lexijc.us
www.lexjic.us
www.lexkc.us
www.lexikc.us
www.lexkic.us
www.lexoc.us
www.lexioc.us
www.lexoic.us
www.lexi.us
www.lexix.us
www.lexicx.us
www.lexixc.us
www.lexid.us
www.lexicd.us
www.lexidc.us
www.lexif.us
www.lexicf.us
www.lexifc.us
www.lexiv.us
www.lexicv.us
www.lexivc.us
lexic.us 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.
lexic.us 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.