huntington.edu Website Information

Daily Unique Visits: 12,630

Daily Page Views: 63,150

Income Per Day: $158

Estimated Value: $94,800

This website is located in United States and is using following IP address 199.8.89.57. See the complete list of popular websites hosted in United States.

huntington.edu is registered under .EDU top-level domain. Please check other sites in .EDU zone.

Website huntington.edu is using the following name servers:

dns2.huntington.edu
washington.ind.net
dns1.huntington.edu

and is probably hosted by ILIGHT-NET - Indiana Higher Education Telecommunication System, US. See the full list of other websites hosted by ILIGHT-NET - Indiana Higher Education Telecommunication System, US.

The highest website huntington.edu position in Alexa rank database was 74823 and the lowest rank position was 994788. Current position of huntington.edu in Alexa rank database is 107880.

Desktop speed score of huntington.edu (78/100) is better than the results of 65.98% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of huntington.edu (76/100) is better than the results of 23.99% of other sites and means that the page is not mobile-friendly.

Mobile speed score of huntington.edu (56/100) is better than the results of 45.93% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

huntington.edu 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.

huntington.edu 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.

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: HUNTINGTON.EDU

Registrant:
Huntington University
2303 College Ave
Huntington, IN 46750
USA

Administrative Contact:
Adam Skiles
Huntington University
2303 College Ave
Huntington, IN 46750
USA
+1.2603594130
askiles@huntington.edu

Technical Contact:
Bob Landon
Huntington University
2303 College Ave
Huntington, IN 46750
USA
+1.2603594274
blandon@huntington.edu

Name Servers:
DNS2.HUNTINGTON.EDU
WASHINGTON.IND.NET
DNS1.HUNTINGTON.EDU

Domain record activated: 04-Apr-1997
Domain record last updated: 03-Jun-2024
Domain expires: 31-Jul-2027

huntington.edu server information

Servers Location

huntington.edu desktop page speed rank

Last tested: 2019-01-20

Desktop Speed Medium

78/100

huntington.edu Desktop Speed Test Quick Summary

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

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

Remove render-blocking JavaScript:

https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
https://ajax.googleapis.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js
https://www.huntington.edu/assets/_js/owl.carousel.min.js
https://www.huntington.edu/assets/_js/jquery.fastLiveFilter.js
https://www.huntington.edu/assets/_js/twitter-min.js
https://www.huntington.edu/assets/_js/jquery.fancybox.pack.js
https://www.huntington.edu/assets/_js/jquery.fancybox-media.js
https://www.huntington.edu/assets/_js/jquery.bxslider.min.js
https://www.huntington.edu/assets/_js/main.js
https://www.huntington.edu/assets/_js/slidebars.min.js
https://www.huntington.edu/assets/_js/featherlight.min.js
https://www.huntington.edu/assets/_js/featherlight.gallery.min.js

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Open+Sans:400,700,300
https://fonts.googleapis.com/css?family=Marcellus+SC
https://code.jquery.com/ui/1.11.4/themes/smoothness/jquery-ui.css
https://www.huntington.edu/assets/_css/site.css
https://www.huntington.edu/assets/_css/slidebars.min.css
https://www.huntington.edu/assets/_css/owl.carousel.css
https://www.huntington.edu/assets/_css/owl.theme.css
https://www.huntington.edu/assets/_css/fancybox.css
https://www.huntington.edu/assets/_css/jquery.bxslider.min.css
https://www.huntington.edu/assets/_css/featherlight.min.css
https://www.huntington.edu/assets/_css/featherlight.gallery.min.css

priority - 7Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://huntington.edu/
http://www.huntington.edu/
https://www.huntington.edu/

priority - 4Optimize images

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

Optimize the following images to reduce their size by 40.8KiB (35% reduction).

Compressing and resizing https://www.huntington.edu/images/site/logo-reverse.png could save 20.1KiB (57% reduction).
Compressing and resizing https://www.huntington.edu/images/site/logo-ub.png could save 6.4KiB (61% reduction).
Compressing https://www.huntington.edu/images/site/logo-mcc.png could save 4.8KiB (28% reduction).
Compressing https://www.huntington.edu/uploads/callouts/MajorsPrograms-3.jpg could save 2.3KiB (18% reduction).
Compressing https://www.huntington.edu/uploads/callouts/FinancialAid-3.jpg could save 1.9KiB (16% reduction).
Compressing https://www.huntington.edu/uploads/callouts/ScheduleVisit-3.jpg could save 1.8KiB (16% reduction).
Compressing https://www.huntington.edu/images/icons/icon-watch.png could save 1.6KiB (50% reduction).
Compressing https://www.huntington.edu/uploads/callouts/RequestInfo-3.jpg could save 1.2KiB (14% reduction).
Compressing https://www.huntington.edu/images/site/social/instagram.jpg could save 233B (14% reduction).
Compressing https://www.huntington.edu/images/site/social/youtube.jpg could save 213B (14% reduction).
Compressing https://www.huntington.edu/images/site/social/twitter.jpg could save 150B (13% reduction).

priority - 2Prioritize 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.

Only about 5% of the final above-the-fold content could be rendered with the full HTML response.

Click to see the screenshot with only the HTML response:

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 5.5KiB (17% reduction).

Minifying https://www.huntington.edu/assets/_css/site.css could save 2.8KiB (16% reduction) after compression.
Minifying https://code.jquery.com/ui/1.11.4/themes/smoothness/jquery-ui.css could save 1.3KiB (17% reduction) after compression.
Minifying https://www.huntington.edu/assets/_css/fancybox.css could save 262B (19% reduction) after compression.
Minifying https://www.huntington.edu/assets/_css/owl.theme.css could save 194B (31% reduction) after compression.
Minifying https://www.huntington.edu/assets/_css/smartphone.css could save 165B (14% reduction) after compression.
Minifying https://www.huntington.edu/assets/_css/tablet.css could save 163B (17% reduction) after compression.
Minifying https://www.huntington.edu/assets/_css/featherlight.gallery.min.css could save 159B (27% reduction) after compression.
Minifying https://www.huntington.edu/assets/_css/featherlight.min.css could save 154B (22% reduction) after compression.
Minifying https://www.huntington.edu/assets/_css/jquery.bxslider.min.css could save 139B (15% reduction) after compression.
Minifying https://www.huntington.edu/assets/_css/owl.carousel.css could save 114B (22% reduction) after compression.

priority - 0Leverage 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://www.google-analytics.com/analytics.js (2 hours)

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 2KiB (37% reduction).

Minifying https://www.huntington.edu/assets/_js/jquery.fancybox-media.js could save 859B (44% reduction) after compression.
Minifying https://www.huntington.edu/assets/_js/jquery.fastLiveFilter.js could save 505B (52% reduction) after compression.
Minifying https://www.huntington.edu/assets/_js/main.js could save 500B (32% reduction) after compression.
Minifying https://www.huntington.edu/assets/_js/featherlight.gallery.min.js could save 146B (16% reduction) after compression.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 1.1KiB (12% reduction).

Minifying https://www.huntington.edu/ could save 1.1KiB (12% reduction) after compression.

huntington.edu Desktop Resource Breakdown

Total Resources	74
Number of Hosts	10
Static Resources	64
JavaScript Resources	14
CSS Resources	14

huntington.edu mobile page speed rank

Last tested: 2019-01-20

Mobile Speed Bad

56/100

huntington.edu Mobile Speed Test Quick Summary

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Open+Sans:400,700,300
https://fonts.googleapis.com/css?family=Marcellus+SC
https://code.jquery.com/ui/1.11.4/themes/smoothness/jquery-ui.css
https://www.huntington.edu/assets/_css/site.css
https://www.huntington.edu/assets/_css/slidebars.min.css
https://www.huntington.edu/assets/_css/owl.carousel.css
https://www.huntington.edu/assets/_css/owl.theme.css
https://www.huntington.edu/assets/_css/fancybox.css
https://www.huntington.edu/assets/_css/jquery.bxslider.min.css
https://www.huntington.edu/assets/_css/desktop.css
https://www.huntington.edu/assets/_css/tablet.css
https://www.huntington.edu/assets/_css/smartphone.css
https://www.huntington.edu/assets/_css/featherlight.min.css
https://www.huntington.edu/assets/_css/featherlight.gallery.min.css

priority - 26Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://huntington.edu/
http://www.huntington.edu/
https://www.huntington.edu/

priority - 8Prioritize 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.

Only about 10% of the final above-the-fold content could be rendered with the full HTML response.

Click to see the screenshot with only the HTML response:

priority - 1Optimize images

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

Optimize the following images to reduce their size by 14.3KiB (20% reduction).

Compressing https://www.huntington.edu/images/site/logo-mcc.png could save 4.8KiB (28% reduction).
Compressing https://www.huntington.edu/uploads/callouts/MajorsPrograms-3.jpg could save 2.3KiB (18% reduction).
Compressing https://www.huntington.edu/uploads/callouts/FinancialAid-3.jpg could save 1.9KiB (16% reduction).
Compressing https://www.huntington.edu/uploads/callouts/ScheduleVisit-3.jpg could save 1.8KiB (16% reduction).
Compressing https://www.huntington.edu/images/icons/icon-watch.png could save 1.6KiB (50% reduction).
Compressing https://www.huntington.edu/uploads/callouts/RequestInfo-3.jpg could save 1.2KiB (14% reduction).
Compressing https://www.huntington.edu/images/site/social/instagram.jpg could save 233B (14% reduction).
Compressing https://www.huntington.edu/images/site/social/youtube.jpg could save 213B (14% reduction).
Compressing https://www.huntington.edu/images/site/social/twitter.jpg could save 150B (13% reduction).

priority - 1Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.google-analytics.com/analytics.js (2 hours)

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 5.5KiB (17% 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 2KiB (37% 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.1KiB (12% reduction).

Minifying https://www.huntington.edu/ could save 1.1KiB (12% reduction) after compression.

huntington.edu Mobile Resource Breakdown

Total Resources	74
Number of Hosts	10
Static Resources	64
JavaScript Resources	14
CSS Resources	14

huntington.edu mobile page usability

Last tested: 2019-01-20

Mobile Usability Medium

76/100

huntington.edu Mobile Usability Test Quick Summary

priority - 29Size content to viewport

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 3,296 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

The element <h1>Faith. Family. Farming.</h1> falls outside the viewport.
The element <p>Study agricult…er difference.</p> falls outside the viewport.
The element <h1>Occupational T…Improve Lives</h1> falls outside the viewport.
The element <p>Do you want to…to learn more!</p> falls outside the viewport.
The element <h1>What is your next step?</h1> falls outside the viewport.
The element <p>Earn your degr…or psychology!</p> falls outside the viewport.

priority - 0Size 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 <div id="sb-site">Apply S…Accessibility</div> and 1 others are close to other tap targets.

The tap target <div id="sb-site">Apply S…Accessibility</div> and 1 others are close to other tap targets.
The tap target <div id="sb-site">Apply S…Accessibility</div> and 1 others are close to other tap targets.
The tap target <div id="sb-site">Apply S…Accessibility</div> and 1 others are close to other tap targets.

The tap target <div id="owl-banner" class="owl-carousel owl-theme">Join Us for Ou…<></div> is close to 1 other tap targets.

The tap target <a href="http://twitter…ormTheForester">@NormTheForester</a> and 1 others are close to other tap targets.

huntington.edu HTML validation

Warnings

The “language” attribute on the “script” element is obsolete. You can safely omit it.

Line: 33 Column: 5 - 34
"...ipt> <script language="javascript"> ..."

The “type” attribute is unnecessary for JavaScript resources.

Line: 71 Column: 6 - 36
"... <script type="text/javascript"> ..." Line: 342 Column: 5 - 35
".../div> <script type="text/javascript"> ..." Line: 363 Column: 5 - 35
".../div> <script type="text/javascript"> ..." Line: 384 Column: 5 - 35
".../div> <script type="text/javascript"> ..." Line: 405 Column: 5 - 35
".../div> <script type="text/javascript"> ..." Line: 1033 Column: 2 - 32
".../script> <script type="text/javascript"> $(d..."

The first occurrence of ID “iam” was here.

Line: 332 Column: 9 - 39
"...> <div class="owl-text" id="iam"> ..." Line: 332 Column: 9 - 39
"...> <div class="owl-text" id="iam"> ..." Line: 332 Column: 9 - 39
"...> <div class="owl-text" id="iam"> ..."

Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.

Line: 420 Column: 4 - 37
"... <section class="features wrapper"> ..." Line: 498 Column: 4 - 28
"...n> <section class="collage"> ..." Line: 753 Column: 3 - 32
"...> <section id="social" class=""> ..."

Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

Line: 450 Column: 8 - 11
"..."> <h1>Upcomi..." Line: 639 Column: 12 - 73
"... <h1 style="border-bottom: 1px solid #0c7a57;padding: .7em 0;">News <..." Line: 741 Column: 27 - 30
"...="column"><h1>Get Co..."

Article lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all articles.

Line: 416 Column: 2 - 26
"...ader> <article class="content"> ..."

Errors

Duplicate attribute “class”.

Line: 327 Column: - 147
"...me.jpg')" class="owl-slider he..." Line: 348 Column: - 142
"...me.jpg')" class="owl-slider he..." Line: 369 Column: - 142
"...me.jpg')" class="owl-slider he..." Line: 390 Column: - 140
"...me.jpg')" class="owl-slider he..."

Duplicate ID “iam”.

Line: 353 Column: 9 - 39
"...> <div class="owl-text" id="iam"> ..." Line: 374 Column: 9 - 39
"...> <div class="owl-text" id="iam"> ..." Line: 395 Column: 9 - 39
"...> <div class="owl-text" id="iam"> ..."

Bad value “/events/{calnedar:url_title}” for attribute “href” on element “a”: Illegal character in path segment: “{” is not allowed.

Line: 464 Column: 10 - 48
"... <a href="/events/{calnedar:url_title}">Read M..." Line: 477 Column: 10 - 48
"... <a href="/events/{calnedar:url_title}">Read M..." Line: 490 Column: 10 - 48
"... <a href="/events/{calnedar:url_title}">Read M..."

Bad value “fancybox” for attribute “rel” on element “a”: The string “fancybox” is not a registered keyword.

Line: 508 Column: - 185
"......" Line: 538 Column: 9 - 169
"...> <a href='https://www.youtube.com/watch?v=jjjaJ_S2jvE&list=PLVi3Ko6YXKTeUU0wewBljrGcSx6sIRDou' class='fancybox-media' data-fancybox-type='iframe' rel='fancybox'> ..." Line: 563 Column: - 186
"......" Line: 588 Column: - 185
"......" Line: 613 Column: 9 - 128
"...> <a href='https://www.youtube.com/watch?v=iOhE9Yf4zyE' class='fancybox-media' data-fancybox-type='iframe' rel='fancybox'> ..." Line: 844 Column: - 182
"......" Line: 866 Column: 7 - 126
"...2"> <a href='https://www.youtube.com/watch?v=iKTRhDph8pw' class='fancybox-media' data-fancybox-type='iframe' rel='fancybox'> ..."

The element “button” must not appear as a descendant of the “a” element.

Line: 515 Column: 11 - 18
"... <button> ..." Line: 545 Column: 10 - 17
"... <button> ..." Line: 570 Column: 10 - 17
"... <button> ..." Line: 595 Column: 10 - 17
"... <button> ..." Line: 620 Column: 10 - 17
"... <button> ..." Line: 852 Column: 9 - 16
"... <button> ..." Line: 874 Column: 9 - 16
"... <button> ..."

No “p” element in scope but a “p” end tag seen.

Line: 655 Column: 125 - 128
"...ellip;</p></p> ..."

huntington.edu similar domains

Similar domains:

www.huntington.com
www.huntington.net
www.huntington.org
www.huntington.info
www.huntington.biz
www.huntington.us
www.huntington.mobi
www.untington.edu
www.huntington.edu
www.buntington.edu
www.hbuntington.edu
www.bhuntington.edu
www.guntington.edu
www.hguntington.edu
www.ghuntington.edu
www.yuntington.edu
www.hyuntington.edu
www.yhuntington.edu
www.uuntington.edu
www.huuntington.edu
www.uhuntington.edu
www.juntington.edu
www.hjuntington.edu
www.jhuntington.edu
www.nuntington.edu
www.hnuntington.edu
www.nhuntington.edu
www.hntington.edu
www.hyntington.edu
www.huyntington.edu
www.hhntington.edu
www.huhntington.edu
www.hhuntington.edu
www.hjntington.edu
www.hujntington.edu
www.hintington.edu
www.huintington.edu
www.hiuntington.edu
www.hutington.edu
www.hubtington.edu
www.hunbtington.edu
www.hubntington.edu
www.huhtington.edu
www.hunhtington.edu
www.hujtington.edu
www.hunjtington.edu
www.humtington.edu
www.hunmtington.edu
www.humntington.edu
www.hunington.edu
www.hunrington.edu
www.huntrington.edu
www.hunrtington.edu
www.hunfington.edu
www.huntfington.edu
www.hunftington.edu
www.hungington.edu
www.huntgington.edu
www.hungtington.edu
www.hunyington.edu
www.huntyington.edu
www.hunytington.edu
www.huntngton.edu
www.huntungton.edu
www.huntiungton.edu
www.huntuington.edu
www.huntjngton.edu
www.huntijngton.edu
www.huntjington.edu
www.huntkngton.edu
www.huntikngton.edu
www.huntkington.edu
www.huntongton.edu
www.huntiongton.edu
www.huntoington.edu
www.huntigton.edu
www.huntibgton.edu
www.huntinbgton.edu
www.huntibngton.edu
www.huntihgton.edu
www.huntinhgton.edu
www.huntihngton.edu
www.huntijgton.edu
www.huntinjgton.edu
www.huntimgton.edu
www.huntinmgton.edu
www.huntimngton.edu
www.huntinton.edu
www.huntinfton.edu
www.huntingfton.edu
www.huntinfgton.edu
www.huntinvton.edu
www.huntingvton.edu
www.huntinvgton.edu
www.huntintton.edu
www.huntingtton.edu
www.huntintgton.edu
www.huntinbton.edu
www.huntingbton.edu
www.huntinyton.edu
www.huntingyton.edu
www.huntinygton.edu
www.huntinhton.edu
www.huntinghton.edu
www.huntingon.edu
www.huntingron.edu
www.huntingtron.edu
www.huntingrton.edu
www.huntingfon.edu
www.huntingtfon.edu
www.huntinggon.edu
www.huntingtgon.edu
www.huntinggton.edu
www.huntingyon.edu
www.huntingtyon.edu
www.huntingtn.edu
www.huntingtin.edu
www.huntingtoin.edu
www.huntingtion.edu
www.huntingtkn.edu
www.huntingtokn.edu
www.huntingtkon.edu
www.huntingtln.edu
www.huntingtoln.edu
www.huntingtlon.edu
www.huntingtpn.edu
www.huntingtopn.edu
www.huntingtpon.edu
www.huntingto.edu
www.huntingtob.edu
www.huntingtonb.edu
www.huntingtobn.edu
www.huntingtoh.edu
www.huntingtonh.edu
www.huntingtohn.edu
www.huntingtoj.edu
www.huntingtonj.edu
www.huntingtojn.edu
www.huntingtom.edu
www.huntingtonm.edu
www.huntingtomn.edu

huntington.edu 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.

huntington.edu 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.

HUNTINGTON.EDU Huntington University | Top-Rated Christian University in Indiana

huntington.edu Website Information

Advertisement

huntington.edu Alexa Rank

huntington.edu whois

huntington.edu server information

Servers Location

huntington.edu desktop page speed rank

huntington.edu Desktop Speed Test Quick Summary

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 7Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

priority - 4Optimize images

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

Optimize the following images to reduce their size by 40.8KiB (35% reduction).

priority - 2Prioritize 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.

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 5.5KiB (17% reduction).

priority - 0Leverage 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:

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 2KiB (37% 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.1KiB (12% reduction).

huntington.edu Desktop Resource Breakdown

huntington.edu mobile page speed rank

huntington.edu Mobile Speed Test Quick Summary

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 26Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

priority - 8Prioritize 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.

priority - 1Optimize images

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

Optimize the following images to reduce their size by 14.3KiB (20% reduction).

priority - 1Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

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 5.5KiB (17% 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 2KiB (37% 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.1KiB (12% reduction).

huntington.edu Mobile Resource Breakdown

huntington.edu mobile page usability

huntington.edu Mobile Usability Test Quick Summary

priority - 29Size content to viewport

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 3,296 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

priority - 0Size 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.

huntington.edu HTML validation

Warnings

The “language” attribute on the “script” element is obsolete. You can safely omit it.

The “type” attribute is unnecessary for JavaScript resources.

The first occurrence of ID “iam” was here.

Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.

Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

Article lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all articles.

Errors

Duplicate attribute “class”.

Duplicate ID “iam”.