centenary.edu website information.
centenary.edu domain name is registered by .EDU top-level domain registry. See the other sites registred in .EDU domain zone.
Following name servers are specified for centenary.edu domain:
- ns3.p16.dynect.net
- ns2.p16.dynect.net
- ns4.p16.dynect.net
- ns1.p16.dynect.net
and probably website centenary.edu is hosted by CNNIC-TENCENT-NET-AP Shenzhen Tencent Computer Systems Company Limited, CN web hosting company. Check the complete list of other most popular websites hosted by CNNIC-TENCENT-NET-AP Shenzhen Tencent Computer Systems Company Limited, CN hosting company.
According to Alexa traffic rank the highest website centenary.edu position was 68079 (in the world). The lowest Alexa rank position was 999095. Now website centenary.edu ranked in Alexa database as number 71931 (in the world).
Website centenary.edu Desktop speed measurement score (57/100) is better than the results of 31.79% of other sites shows that the page desktop performance can be improved.
centenary.edu Mobile usability score (96/100) is better than the results of 46.59% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of centenary.edu (53/100) is better than the results of 39.51% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
| Date | Rank | Change |
|---|---|---|
| Nov-20-2024 | 71,931 | 252 |
| Nov-19-2024 | 72,183 | 94 |
| Nov-18-2024 | 72,277 | -120 |
| Nov-17-2024 | 72,157 | -502 |
| Nov-16-2024 | 71,655 | -1,453 |
| Nov-15-2024 | 70,202 | 1,325 |
| Nov-14-2024 | 71,527 | -693 |
Advertisement
centenary.edu Rank History
Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.
centenary.edu whois
WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.
This Registry database contains ONLY .EDU domains.
The data in the EDUCAUSE Whois database is provided
by EDUCAUSE for information purposes in order to
assist in the process of obtaining information about
or related to .edu domain registration records.
The EDUCAUSE Whois database is authoritative for the
.EDU domain.
A Web interface for the .EDU EDUCAUSE Whois Server is
available at: http://whois.educause.edu
By submitting a Whois query, you agree that this information
will not be used to allow, enable, or otherwise support
the transmission of unsolicited commercial advertising or
solicitations via e-mail. The use of electronic processes to
harvest information from this server is generally prohibited
except as reasonably necessary to register or modify .edu
domain names.
-------------------------------------------------------------
Domain Name: CENTENARY.EDU
Registrant:
Centenary College
2911 Centenary Blvd.
Shreveport, LA 71104
USA
Administrative Contact:
Scott Merritt
Centenary College of Louisiana
PO Box 41188
Shreveport, LA 71134
USA
+1.3188695721
smerritt@centenary.edu
Technical Contact:
Chris Derrick
Centenary College of Louisiana
2911 Centenary Blvd.
Shreveport, LA 71104
USA
+1.3188695721
cderrick@centenary.edu
Name Servers:
NS4.P201.DNS.ORACLECLOUD.NET
NS3.P201.DNS.ORACLECLOUD.NET
NS1.P201.DNS.ORACLECLOUD.NET
NS2.P201.DNS.ORACLECLOUD.NET
Domain record activated: 01-Jul-1993
Domain record last updated: 09-Aug-2023
Domain expires: 31-Jul-2025
centenary.edu server information
centenary.edu desktop page speed rank
Last tested: 2019-01-08
centenary.edu Desktop Speed Test Quick Summary
priority - 63 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 613.3KiB (33% reduction).
Compressing https://www.centenary.edu/files/pages/wide-lrg-06-2.jpg could save 78.2KiB (23% reduction).
Compressing https://www.centenary.edu/files/facts-statistics/wide-lrg-05.jpg could save 47.6KiB (19% reduction).
Compressing https://www.centenary.edu/files/home-features/ultr…entenary-2018-4480.jpg could save 47.3KiB (19% reduction).
Compressing https://www.centenary.edu/files/news/wide-xsml-dreamweek19.png could save 44.9KiB (34% reduction).
Compressing https://www.centenary.edu/files/facts-statistics/wide-lrg-04-3.jpg could save 34.2KiB (18% reduction).
Compressing https://www.centenary.edu/files/facts-statistics/wide-lrg-01.jpg could save 27.3KiB (16% reduction).
Compressing https://www.centenary.edu/files/facts-statistics/wide-lrg-03-3.jpg could save 22.1KiB (17% reduction).
Compressing https://d5j4p04e8cw00.cloudfront.net/images/admin_…10060-thumb?1543245214 could save 1.9KiB (41% reduction).
Compressing https://www.centenary.edu/images/triangle-footer-red.jpg could save 815B (44% reduction).
Compressing https://www.centenary.edu/images/triangle-footer-blue.jpg could save 508B (42% reduction).
priority - 10 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 blocking script resources and 2 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.
Remove render-blocking JavaScript:
https://www.centenary.edu/js/site.js?2019-01-03
Optimize CSS Delivery of the following:
https://www.centenary.edu/css/site.css?2019-01-03
priority - 4 Leverage 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://cdn.heapanalytics.com/js/heap-1307114016.js (2 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-KQMWZN (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/138020…0525?v=2.8.35&r=stable (20 minutes)
https://connect.facebook.net/signals/config/212197…8615?v=2.8.35&r=stable (20 minutes)
https://maps.googleapis.com/maps/api/js?key=AIzaSy…nPafs&libraries=places (30 minutes)
https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 2 Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 0 Minify 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.5KiB (18% reduction).
priority - 0 Minify 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 743B (22% reduction).
Minifying https://mobi.visitdays.com/assets/snippet/assets/main.bundle.css could save 254B (26% reduction) after compression.
centenary.edu Desktop Resources
| Total Resources | 53 |
| Number of Hosts | 17 |
| Static Resources | 27 |
| JavaScript Resources | 15 |
| CSS Resources | 7 |
centenary.edu Desktop Resource Breakdown
centenary.edu mobile page speed rank
Last tested: 2019-01-08
centenary.edu Mobile Speed Test Quick Summary
priority - 42 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 408.6KiB (53% reduction).
Compressing https://www.centenary.edu/files/news/classic-xsml-dreamweek19.png could save 52.2KiB (34% reduction).
Compressing https://www.centenary.edu/files/home-features/port…enary-2017-04-3341.jpg could save 22.1KiB (20% reduction).
Compressing https://www.centenary.edu/files/pages/wide-xxsml-06-2.jpg could save 6.4KiB (23% reduction).
Compressing https://www.centenary.edu/files/facts-statistics/wide-xxsml-01.jpg could save 4.8KiB (22% reduction).
Compressing https://www.centenary.edu/files/facts-statistics/wide-xxsml-05.jpg could save 4.3KiB (21% reduction).
Compressing https://www.centenary.edu/files/facts-statistics/wide-xxsml-04-3.jpg could save 4.1KiB (21% reduction).
Compressing https://www.centenary.edu/files/facts-statistics/wide-xxsml-03-3.jpg could save 3.1KiB (20% reduction).
Compressing https://d5j4p04e8cw00.cloudfront.net/images/admin_…10060-thumb?1543245214 could save 1.9KiB (41% reduction).
Compressing https://www.centenary.edu/images/triangle-footer-red.jpg could save 815B (44% reduction).
Compressing https://www.centenary.edu/images/triangle-footer-blue.jpg could save 508B (42% reduction).
priority - 40 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 blocking script resources and 2 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.
Remove render-blocking JavaScript:
https://www.centenary.edu/js/site.js?2019-01-03
Optimize CSS Delivery of the following:
https://www.centenary.edu/css/site.css?2019-01-03
priority - 8 Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 6 Leverage 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://cdn.heapanalytics.com/js/heap-1307114016.js (2 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-KQMWZN (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/138020…0525?v=2.8.35&r=stable (20 minutes)
https://connect.facebook.net/signals/config/212197…8615?v=2.8.35&r=stable (20 minutes)
https://maps.googleapis.com/maps/api/js?key=AIzaSy…nPafs&libraries=places (30 minutes)
https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 0 Minify 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.5KiB (18% reduction).
priority - 0 Minify 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 743B (22% reduction).
Minifying https://mobi.visitdays.com/assets/snippet/assets/main.bundle.css could save 254B (26% reduction) after compression.
centenary.edu Mobile Resources
| Total Resources | 53 |
| Number of Hosts | 17 |
| Static Resources | 27 |
| JavaScript Resources | 15 |
| CSS Resources | 7 |
centenary.edu Mobile Resource Breakdown
centenary.edu mobile page usability
Last tested: 2019-01-08
centenary.edu Mobile Usability Test Quick Summary
priority - 3 Size 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.
<article class="recent_events_…usel-item_next">Jan 15…p Team Meeting</article> is close to 1 other tap targets.The tap target
<button type="button" class="fs-carousel-pa…arousel-active">1</button> and 2 others are close to other tap targets.The tap target
<button type="button" class="fs-carousel-page">2</button> and 8 others are close to other tap targets.The tap target
<article class="recent_news_ar…usel-item_next">January 3, 201…Louisiana tour</article> is close to 1 other tap targets.The tap target
<button type="button" class="fs-carousel-page">2</button> and 2 others are close to other tap targets.The tap target
<button type="submit" class="site_search_button">submit</button> is close to 1 other tap targets.The tap target
<button class="js-swap main_n…s-swap-enabled">Expand Navigation</button> and 4 others are close to other tap targets.centenary.edu similar domains
www.centenary.net
www.centenary.org
www.centenary.info
www.centenary.biz
www.centenary.us
www.centenary.mobi
www.entenary.edu
www.centenary.edu
www.xentenary.edu
www.cxentenary.edu
www.xcentenary.edu
www.dentenary.edu
www.cdentenary.edu
www.dcentenary.edu
www.fentenary.edu
www.cfentenary.edu
www.fcentenary.edu
www.ventenary.edu
www.cventenary.edu
www.vcentenary.edu
www.cntenary.edu
www.cwntenary.edu
www.cewntenary.edu
www.cwentenary.edu
www.csntenary.edu
www.cesntenary.edu
www.csentenary.edu
www.cdntenary.edu
www.cedntenary.edu
www.crntenary.edu
www.cerntenary.edu
www.crentenary.edu
www.cetenary.edu
www.cebtenary.edu
www.cenbtenary.edu
www.cebntenary.edu
www.cehtenary.edu
www.cenhtenary.edu
www.cehntenary.edu
www.cejtenary.edu
www.cenjtenary.edu
www.cejntenary.edu
www.cemtenary.edu
www.cenmtenary.edu
www.cemntenary.edu
www.cenenary.edu
www.cenrenary.edu
www.centrenary.edu
www.cenrtenary.edu
www.cenfenary.edu
www.centfenary.edu
www.cenftenary.edu
www.cengenary.edu
www.centgenary.edu
www.cengtenary.edu
www.cenyenary.edu
www.centyenary.edu
www.cenytenary.edu
www.centnary.edu
www.centwnary.edu
www.centewnary.edu
www.centwenary.edu
www.centsnary.edu
www.centesnary.edu
www.centsenary.edu
www.centdnary.edu
www.centednary.edu
www.centdenary.edu
www.centrnary.edu
www.centernary.edu
www.centeary.edu
www.centebary.edu
www.centenbary.edu
www.centebnary.edu
www.centehary.edu
www.centenhary.edu
www.centehnary.edu
www.centejary.edu
www.centenjary.edu
www.centejnary.edu
www.centemary.edu
www.centenmary.edu
www.centemnary.edu
www.centenry.edu
www.centenqry.edu
www.centenaqry.edu
www.centenqary.edu
www.centenwry.edu
www.centenawry.edu
www.centenwary.edu
www.centensry.edu
www.centenasry.edu
www.centensary.edu
www.centenzry.edu
www.centenazry.edu
www.centenzary.edu
www.centenay.edu
www.centenaey.edu
www.centenarey.edu
www.centenaery.edu
www.centenady.edu
www.centenardy.edu
www.centenadry.edu
www.centenafy.edu
www.centenarfy.edu
www.centenafry.edu
www.centenaty.edu
www.centenarty.edu
www.centenatry.edu
www.centenar.edu
www.centenart.edu
www.centenaryt.edu
www.centenarg.edu
www.centenaryg.edu
www.centenargy.edu
www.centenarh.edu
www.centenaryh.edu
www.centenarhy.edu
www.centenaru.edu
www.centenaryu.edu
www.centenaruy.edu
centenary.edu Ping
Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.
centenary.edu TRACEROUTE
Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.