nsep.gov Website Information

Daily Unique Visits: 807

Daily Page Views: 1,614

Income Per Day: $5

Estimated Value: $1,200

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

nsep.gov is registered under .GOV top-level domain. Please check other sites in .GOV zone.

Website nsep.gov is using the following name servers:

mns01.domaincontrol.com
mns02.domaincontrol.com

and is probably hosted by Amazon Data Services Ireland Ltd. See the full list of other websites hosted by Amazon Data Services Ireland Ltd.

The highest website nsep.gov position in Alexa rank database was 43452 and the lowest rank position was 993391. Current position of nsep.gov in Alexa rank database is 889104.

Desktop speed score of nsep.gov (57/100) is better than the results of 31.79% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of nsep.gov (61/100) is better than the results of 5.47% of other sites and means that the page is not mobile-friendly.

Mobile speed score of nsep.gov (46/100) is better than the results of 27.13% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

nsep.gov 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.

nsep.gov 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.

% DOTGOV WHOIS Server ready
Domain Name: NSEP.GOV
Status: ACTIVE
Security Contact Email: nsep@nsep.gov

>>> Last update of whois database: 2022-11-19T12:48:04Z

nsep.gov server information

Servers Location

nsep.gov desktop page speed rank

Last tested: 2017-06-02

Desktop Speed Bad

57/100

nsep.gov Desktop Speed Test Quick Summary

priority - 47Optimize images

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

Optimize the following images to reduce their size by 457.3KiB (73% reduction).

Compressing https://nsep.gov/sites/all/themes/business/images/studentpic.jpg could save 173.9KiB (76% reduction).
Compressing https://nsep.gov/sites/all/themes/business/images/results.jpg could save 154.1KiB (74% reduction).
Compressing https://nsep.gov/sites/all/themes/business/images/federal.jpg could save 64.4KiB (57% reduction).
Compressing https://nsep.gov/images/logo-front.jpg could save 59.5KiB (87% reduction).
Compressing https://nsep.gov/sites/all/themes/business/images/…e-nav-button-hover.png could save 2.7KiB (95% reduction).
Compressing https://nsep.gov/images/bar.png could save 2.7KiB (87% reduction).

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

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

Remove render-blocking JavaScript:

https://nsep.gov/misc/jquery.js?v=1.4.4
https://nsep.gov/misc/jquery.once.js?v=1.2
https://nsep.gov/misc/drupal.js?o8tjwo
https://nsep.gov/sites/all/libraries/shadowbox-3.0.3/shadowbox.js?v=3.0.3
https://nsep.gov/sites/all/modules/shadowbox/shadowbox_auto.js?v=3.0.3
https://nsep.gov/sites/all/themes/business/js/sliding_effect.js?o8tjwo
https://nsep.gov/sites/all/themes/business/js/superfish.js?o8tjwo
https://nsep.gov/sites/all/themes/business/js/supersubs.js?o8tjwo
https://nsep.gov/sites/all/themes/business/js/sfmenu.js?o8tjwo

Optimize CSS Delivery of the following:

https://nsep.gov/modules/system/system.base.css?o8tjwo
https://nsep.gov/modules/system/system.menus.css?o8tjwo
https://nsep.gov/modules/system/system.messages.css?o8tjwo
https://nsep.gov/modules/system/system.theme.css?o8tjwo
https://nsep.gov/sites/all/libraries/shadowbox-3.0.3/shadowbox.css?o8tjwo
https://nsep.gov/modules/comment/comment.css?o8tjwo
https://nsep.gov/modules/field/theme/field.css?o8tjwo
https://nsep.gov/modules/node/node.css?o8tjwo
https://nsep.gov/modules/search/search.css?o8tjwo
https://nsep.gov/modules/user/user.css?o8tjwo
https://nsep.gov/sites/all/themes/business/style.css?o8tjwo
https://nsep.gov/sites/default/files/color/busines…3a07/colors.css?o8tjwo
https://fonts.googleapis.com/css?family=Droid+Sans:regular,bold

priority - 14Enable 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 131.7KiB (66% reduction).

Compressing https://nsep.gov/misc/jquery.js?v=1.4.4 could save 50.3KiB (65% reduction).
Compressing https://nsep.gov/sites/all/libraries/shadowbox-3.0.3/shadowbox.js?v=3.0.3 could save 23.5KiB (64% reduction).
Compressing https://nsep.gov/sites/all/themes/business/style.css?o8tjwo could save 18.6KiB (75% reduction).
Compressing https://nsep.gov/ could save 11.5KiB (71% reduction).
Compressing https://nsep.gov/misc/drupal.js?o8tjwo could save 10.8KiB (65% reduction).
Compressing https://nsep.gov/modules/system/system.base.css?o8tjwo could save 3.5KiB (65% reduction).
Compressing https://nsep.gov/modules/system/system.theme.css?o8tjwo could save 2.4KiB (67% reduction).
Compressing https://nsep.gov/sites/all/themes/business/js/superfish.js?o8tjwo could save 2.1KiB (59% reduction).
Compressing https://nsep.gov/misc/jquery.once.js?v=1.2 could save 1.9KiB (64% reduction).
Compressing https://nsep.gov/sites/all/themes/business/js/supersubs.js?o8tjwo could save 1.7KiB (53% reduction).
Compressing https://nsep.gov/modules/system/system.menus.css?o8tjwo could save 1.3KiB (67% reduction).
Compressing https://nsep.gov/sites/all/libraries/shadowbox-3.0.3/shadowbox.css?o8tjwo could save 1.3KiB (64% reduction).
Compressing https://nsep.gov/sites/all/themes/business/js/sliding_effect.js?o8tjwo could save 1.1KiB (56% reduction).
Compressing https://nsep.gov/modules/user/user.css?o8tjwo could save 1.1KiB (61% reduction).
Compressing https://nsep.gov/modules/system/system.messages.css?o8tjwo could save 579B (60% reduction).

priority - 2Minify 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 17.6KiB (62% reduction).

Minifying https://nsep.gov/misc/drupal.js?o8tjwo could save 11KiB (67% reduction).
Minifying https://nsep.gov/misc/jquery.once.js?v=1.2 could save 2.5KiB (84% reduction).
Minifying https://nsep.gov/sites/all/themes/business/js/supersubs.js?o8tjwo could save 2.2KiB (66% reduction).
Minifying https://nsep.gov/sites/all/themes/business/js/sliding_effect.js?o8tjwo could save 1.1KiB (54% reduction).
Minifying https://nsep.gov/sites/all/themes/business/js/superfish.js?o8tjwo could save 946B (26% reduction).

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 11.2KiB (31% reduction).

Minifying https://nsep.gov/sites/all/themes/business/style.css?o8tjwo could save 6.7KiB (28% reduction).
Minifying https://nsep.gov/modules/system/system.base.css?o8tjwo could save 2.3KiB (44% reduction).
Minifying https://nsep.gov/modules/system/system.theme.css?o8tjwo could save 1.2KiB (33% reduction).
Minifying https://nsep.gov/modules/system/system.menus.css?o8tjwo could save 588B (29% reduction).
Minifying https://nsep.gov/modules/user/user.css?o8tjwo could save 517B (29% 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:

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

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

Minifying https://nsep.gov/ could save 1.7KiB (11% reduction).

nsep.gov Desktop Resource Breakdown

Total Resources	38
Number of Hosts	5
Static Resources	32
JavaScript Resources	11
CSS Resources	13

nsep.gov mobile page speed rank

Last tested: 2017-05-30

Mobile Speed Bad

46/100

nsep.gov Mobile Speed Test Quick Summary

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 47Optimize images

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

Optimize the following images to reduce their size by 457.3KiB (73% reduction).

priority - 14Enable 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 131.7KiB (66% reduction).

priority - 2Minify 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 17.6KiB (62% reduction).

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 11.2KiB (31% 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 - 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.7KiB (11% reduction).

Minifying https://nsep.gov/ could save 1.7KiB (11% reduction).

nsep.gov Mobile Resource Breakdown

Total Resources	38
Number of Hosts	5
Static Resources	32
JavaScript Resources	11
CSS Resources	13

nsep.gov mobile page usability

Last tested: 2017-05-30

Mobile Usability Bad

61/100

nsep.gov Mobile Usability Test Quick Summary

priority - 34Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Home renders only 5 pixels tall (14 CSS pixels).

Federal Employers and 3 others render only 5 pixels tall (14 CSS pixels).

Contact renders only 5 pixels tall (14 CSS pixels).

National Security and 1 others render only 7 pixels tall (17 CSS pixels).

Strengthening…ional security and 2 others render only 4 pixels tall (11 CSS pixels).

In 2011, the N…n Act of 1991. and 3 others render only 5 pixels tall (14 CSS pixels).

What people ar…ying about us: renders only 5 pixels tall (14 CSS pixels).

"FEMA has had…t the agency." and 2 others render only 7 pixels tall (17 CSS pixels).

Federal Emerge…nt Agency, DHS and 2 others render only 5 pixels tall (13 CSS pixels).

for building l…ty in the U.S. and 3 others render only 6 pixels tall (15 CSS pixels).

Learn more here. and 1 others render only 5 pixels tall (14 CSS pixels).

Accessibility/Section 508 and 8 others render only 6 pixels tall (15 CSS pixels).

English for He…guage Speakers and 23 others render only 5 pixels tall (12 CSS pixels).

priority - 19Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/" class="active">Home</a> is close to 1 other tap targets.

The tap target <a href="#" class="active">1</a> is close to 1 other tap targets.

The tap target <a href="#">2</a> and 1 others are close to other tap targets.

The tap target <a href="http://www.nsep.gov">Home</a> and 8 others are close to other tap targets.

The tap target <a href="../content/mis…and-objectives">Mission and Objectives</a> and 25 others are close to other tap targets.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 3Size 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 1,040 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <div class="clear"></div> falls outside the viewport.
The element <h1>Welcome to the…cation Program</h1> falls outside the viewport.
The element <p>At NSEP, our p…ent workforce.</p> falls outside the viewport.
The element <div class="home-block">The Language F…arn more here.</div> falls outside the viewport.
The element <div class="clear"></div> falls outside the viewport.
The element <div id="ft">Home Contact…udent Profiles</div> falls outside the viewport.

nsep.gov HTML validation

Errors

Attribute “xmlns:content” not allowed here.

Line: 11 Column: 16 - 48
"...TYPE html> <html lang="en" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <head..."

Attribute “xmlns:dc” not allowed here.

Attribute “xmlns:foaf” not allowed here.

Attribute “xmlns:og” not allowed here.

Attribute “xmlns:rdfs” not allowed here.

Attribute “xmlns:sioc” not allowed here.

Attribute “xmlns:sioct” not allowed here.

Attribute “xmlns:skos” not allowed here.

Attribute “xmlns:xsd” not allowed here.

Element “p” not allowed as child of element “hgroup” in this context. (Suppressing further errors from this subtree.)

Line: 130 Column: 5 - 7
"...</h2> <p></p><!..."

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

Line: 154 Column: 6 - 25
"...ng"> <a rel="1" href="#">1</a> ..."

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

Line: 155 Column: 6 - 25
"...</a> <a rel="2" href="#">2</a> ..."

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

Line: 156 Column: 6 - 25
"...</a> <a rel="3" href="#">3</a> ..."

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

Line: 242 Column: 64 - 68
"...ersary</a></li></p> ..."

Warnings

Attribute with the local name “xmlns:content” is not serializable as XML 1.0.

Attribute with the local name “xmlns:dc” is not serializable as XML 1.0.

Attribute with the local name “xmlns:foaf” is not serializable as XML 1.0.

Attribute with the local name “xmlns:og” is not serializable as XML 1.0.

Attribute with the local name “xmlns:rdfs” is not serializable as XML 1.0.

Attribute with the local name “xmlns:sioc” is not serializable as XML 1.0.

Attribute with the local name “xmlns:sioct” is not serializable as XML 1.0.

Attribute with the local name “xmlns:skos” is not serializable as XML 1.0.

Attribute with the local name “xmlns:xsd” is not serializable as XML 1.0.

The “type” attribute for the “style” element is not needed and should be omitted.

Line: 18 Column: 1 - 35
"...v</title> <style type="text/css" media="all"> @impo..." Line: 24 Column: 1 - 38
"... </style> <style type="text/css" media="screen"> @impo..." Line: 27 Column: 1 - 37
"... </style> <style type="text/css" media="print"> <!--/..." Line: 33 Column: 1 - 35
"... </style> <style type="text/css" media="all"> @impo..." Line: 40 Column: 1 - 35
"... </style> <style type="text/css" media="all"> @impo..."

The “type” attribute is unnecessary for JavaScript resources.

Line: 44 Column: 1 - 77
"... </style> <script type="text/javascript" src="https://nsep.gov/misc/jquery.js?v=1.4.4"></scri..." Line: 45 Column: 1 - 80
"...</script> <script type="text/javascript" src="https://nsep.gov/misc/jquery.once.js?v=1.2"></scri..." Line: 46 Column: 1 - 76
"...</script> <script type="text/javascript" src="https://nsep.gov/misc/drupal.js?p6cz3l"></scri..." Line: 47 Column: 1 - 111
"...</script> <script type="text/javascript" src="https://nsep.gov/sites/all/libraries/shadowbox-3.0.3/shadowbox.js?v=3.0.3"></scri..." Line: 48 Column: 1 - 108
"...</script> <script type="text/javascript" src="https://nsep.gov/sites/all/modules/shadowbox/shadowbox_auto.js?v=3.0.3"></scri..." Line: 49 Column: 1 - 108
"...</script> <script type="text/javascript" src="https://nsep.gov/sites/all/themes/business/js/sliding_effect.js?p6cz3l"></scri..." Line: 50 Column: 1 - 103
"...</script> <script type="text/javascript" src="https://nsep.gov/sites/all/themes/business/js/superfish.js?p6cz3l"></scri..." Line: 51 Column: 1 - 103
"...</script> <script type="text/javascript" src="https://nsep.gov/sites/all/themes/business/js/supersubs.js?p6cz3l"></scri..." Line: 52 Column: 1 - 100
"...</script> <script type="text/javascript" src="https://nsep.gov/sites/all/themes/business/js/sfmenu.js?p6cz3l"></scri..." Line: 53 Column: 1 - 31
"...</script> <script type="text/javascript">  <script async type="text/javascript" src="https://dap.digitalgov.gov/Universal-Federated-Analytics-Min.js?agency=DOD&subagency=DLNSEO" id="_fed_an_ua_tag"></scrip..." Line: 68 Column: 1 - 63
"...</script> <script src="//static.getclicky.com/js" type="text/javascript"></scri..." Line: 69 Column: 1 - 31
"...</script> <script type="text/javascript">try{ c..."

The “banner” role is unnecessary for element “header”.

Line: 75 Column: 3 - 53
"...auto;"> <header id="header" class="clearfix" role="banner"> ..."

The “navigation” role is unnecessary for element “nav”.

Line: 78 Column: 5 - 60
"... <nav id="navigation" class="clearfix" role="navigation"> ..."

Empty heading.

Line: 129 Column: 5 - 8
"...ame"> <h2><a hre..."

nsep.gov similar domains

Similar domains:

www.nsep.com
www.nsep.net
www.nsep.org
www.nsep.info
www.nsep.biz
www.nsep.us
www.nsep.mobi
www.sep.gov
www.nsep.gov
www.bsep.gov
www.nbsep.gov
www.bnsep.gov
www.hsep.gov
www.nhsep.gov
www.hnsep.gov
www.jsep.gov
www.njsep.gov
www.jnsep.gov
www.msep.gov
www.nmsep.gov
www.mnsep.gov
www.nep.gov
www.nwep.gov
www.nswep.gov
www.nwsep.gov
www.neep.gov
www.nseep.gov
www.nesep.gov
www.ndep.gov
www.nsdep.gov
www.ndsep.gov
www.nzep.gov
www.nszep.gov
www.nzsep.gov
www.nxep.gov
www.nsxep.gov
www.nxsep.gov
www.naep.gov
www.nsaep.gov
www.nasep.gov
www.nsp.gov
www.nswp.gov
www.nsewp.gov
www.nssp.gov
www.nsesp.gov
www.nssep.gov
www.nsdp.gov
www.nsedp.gov
www.nsrp.gov
www.nserp.gov
www.nsrep.gov
www.nse.gov
www.nseo.gov
www.nsepo.gov
www.nseop.gov
www.nsel.gov
www.nsepl.gov
www.nselp.gov

nsep.gov 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.

nsep.gov 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.

NSEP.GOV Home | nsepgov

nsep.gov Website Information

Advertisement

nsep.gov Alexa Rank

nsep.gov whois

nsep.gov server information

Servers Location

nsep.gov desktop page speed rank

nsep.gov Desktop Speed Test Quick Summary

priority - 47Optimize images

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

Optimize the following images to reduce their size by 457.3KiB (73% reduction).

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 14Enable 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 131.7KiB (66% reduction).

priority - 2Minify 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 17.6KiB (62% reduction).

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 11.2KiB (31% 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 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.7KiB (11% reduction).

nsep.gov Desktop Resource Breakdown

nsep.gov mobile page speed rank

nsep.gov Mobile Speed Test Quick Summary

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

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

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 47Optimize images

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

Optimize the following images to reduce their size by 457.3KiB (73% reduction).

priority - 14Enable 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 131.7KiB (66% reduction).

priority - 2Minify 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 17.6KiB (62% reduction).

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 11.2KiB (31% 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 - 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.7KiB (11% reduction).

nsep.gov Mobile Resource Breakdown

nsep.gov mobile page usability

nsep.gov Mobile Usability Test Quick Summary

priority - 34Use 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.

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

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.

priority - 3Size 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 1,040 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

nsep.gov HTML validation

Errors

Attribute “xmlns:content” not allowed here.

Attribute “xmlns:dc” not allowed here.

Attribute “xmlns:foaf” not allowed here.

Attribute “xmlns:og” not allowed here.

Attribute “xmlns:rdfs” not allowed here.

Attribute “xmlns:sioc” not allowed here.

Attribute “xmlns:sioct” not allowed here.

Attribute “xmlns:skos” not allowed here.