Gov - Gov.com

Overview

Snoop Summary for gov.com

This is a free and comprehensive report about gov.com. Gov.com has the potential to be earning an estimated $2 USD per day from advertising revenue. If gov.com was to be sold it would possibly be worth $1,149 USD (based on the daily revenue potential of the website over a 24 month period). Gov.com is somewhat popular with an estimated 548 daily unique visitors. This report was last updated 26th August, 2021.

About gov.com

Site Preview:
Title:	GOV
Description:	The leading independent online resource for authoritative government affairs and constituent information, providing direct links to every publicly accessible government data source available through official channels.
Keywords and Tags:	public information
Related Terms:	concur gov, donotcall gov, hemayat mcls gov ir, kingdomofdixit gov best, mymedicare gov account, mymedicare gov log in, nv.gov, studentloans gov, studentloans gov login, www ptt gov
Fav Icon:
Age:	Over 28 years old
Domain Created:	18th March, 1996
Domain Updated:	4th May, 2020
Domain Expires:	19th March, 2025

Review

Snoop Score

2/5

Valuation

$1,149 USD

Note: All valuation figures are estimates.

Popularity

Low

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	1,045,305
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority:	0
Moz Page Authority:	0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors:	548
Monthly Visitors:	16,668
Yearly Visitors:	199,888

Note: All visitors figures are estimates.

Visitors By Country

Revenue

Daily Revenue:	$2 USD
Monthly Revenue:	$48 USD
Yearly Revenue:	$570 USD

Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top Ranking Keywords (US)

Domain Analysis

	Value	Length
Domain:	gov.com	7
Domain Name:	gov	3
Extension (TLD):	com	3

Expiry Check:

Page Speed Analysis

Average Load Time:	1.13 seconds
Load Time Comparison:	Faster than 73% of sites

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: http://www.gov.com/

Updated: 28th December, 2020

2.72 seconds

First Contentful Paint (FCP)

20%

60%

20%

0.00 seconds

First Input Delay (FID)

98%

1%

Simulate loading on desktop

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for gov.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Speed Index — 1.0 s
The time taken for the page contents to be visibly populated.

Largest Contentful Paint — 1.1 s
The timing of the largest text or image that is painted.

Time to Interactive — 1.0 s
The time taken for the page to become fully interactive.

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Cumulative Layout Shift — 0.006
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.0 s
The time taken for the page's main thread to be quiet enough to handle input.

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive gov.com as laggy when the latency is higher than 0.05 seconds.

Network Requests
Below is a list of network requests that were made during page load.

URL	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://gov.com/	0	248.33899969235	267	0	301	text/html
http://www.gov.com/	248.75500006601	518.99100001901	30605	30318	200	text/html	Document
https://www.googletagmanager.com/gtag/js?id=UA-138241245-1	533.14600000158	568.39199969545	39705	98729	200	application/javascript	Script
http://www.gov.com/gov.css	533.32499973476	733.75999974087	12667	12381	200	text/css	Stylesheet
http://www.gov.com/graphics/GOV_130x85.gif	535.82499967888	735.52099987864	1531	1246	200	image/gif	Image
http://www.gov.com/graphics/GOV_ban1.gif	536.0619998537	736.13799968734	3040	2755	200	image/gif	Image
http://www.gov.com/graphics/GOV_ban2.gif	536.22599970549	796.61499988288	4455	4169	200	image/gif	Image
http://www.gov.com/graphics/GOV_ban3.gif	536.60599980503	735.94299983233	4281	3996	200	image/gif	Image
http://www.gov.com/graphics/nav25_home.gif	536.86100011691	794.55599980429	2581	2296	200	image/gif	Image
http://www.gov.com/graphics/1x1_white.gif	537.01899992302	796.01199971512	325	43	200	image/gif	Image
http://www.gov.com/graphics/taxuser2.jpg	537.17199992388	857.68699971959	32502	32214	200	image/jpeg	Image
http://www.gov.com/graphics/1x1_EEEEEE.gif	537.40100003779	792.16599976644	325	43	200	image/gif	Image
http://www.gov.com/graphics/taxbutton.gif	537.71999990568	662.47399989516	2554	2269	200	image/gif	Image
https://www.google-analytics.com/analytics.js	594.1519998014	598.08499971405	19452	47051	200	text/javascript	Script
http://www.gov.com/graphics/2x25.gif	607.63899981976	731.4419997856	426	143	200	image/gif	Image
https://www.google-analytics.com/j/collect?v=1&_v=j87&a=849325732&t=pageview&_s=1&dl=http%3A%2F%2Fwww.gov.com%2F&ul=en-us&de=windows-1252&dt=Making%20Government%20User-friendly%20-%20Government%20Information&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUABAAAAAC~&jid=1970567012&gjid=790910673&cid=357257910.1609145090&tid=UA-138241245-1&_gid=1971912566.1609145090&_r=1&gtm=2oubu0&z=1214157009	623.08100005612	626.89499976113	618	1	200	text/plain	XHR

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
548.98	8.139
559.559	5.205
603.45	8.858
612.89	8.403
629.185	21.454
762.031	8.812
770.857	17.015
789.944	7.449

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 0 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Gov.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

URL	Transfer Size (Bytes)	Potential Savings (Ms)
http://www.gov.com/gov.css	12667	70

Show Details

Properly size images
Images can slow down the page's load time. Gov.com should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Gov.com should consider lazy-loading offscreen and hidden images.

Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Gov.com should consider minifying CSS files.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
http://www.gov.com/gov.css	12667	2593

Show Details

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Gov.com should consider minifying JS files.

Remove unused CSS — Potential savings of 10 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Gov.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
http://www.gov.com/gov.css	12667	10513

Show Details

Remove unused JavaScript — Potential savings of 21 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
https://www.googletagmanager.com/gtag/js?id=UA-138241245-1	39705	21671

Show Details

Efficiently encode images — Potential savings of 25 KiB
Unoptimized images can consume more cellular data than what is necessary.

URL	Resource Size (Bytes)	Potential Savings (Bytes)
http://www.gov.com/graphics/taxuser2.jpg	32214	25845

Show Details

Serve images in next-gen formats — Potential savings of 27 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.

URL	Resource Size (Bytes)	Potential Savings (Bytes)
http://www.gov.com/graphics/taxuser2.jpg	32214	27772

Show Details

Enable text compression — Potential savings of 35 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
http://www.gov.com/	30318	24714
http://www.gov.com/gov.css	12381	11520

Show Details

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Initial server response time was short — Root document took 270 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.

URL	Time Spent (Ms)
http://www.gov.com/	271.234

Show Details

Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Gov.com should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
http://gov.com/	190
http://www.gov.com/	0

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Gov.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.

Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

Diagnostics

Avoids enormous network payloads — Total size was 152 KiB
Large network payloads can cost users money and are linked to long load times.

URL	Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=UA-138241245-1	39705
http://www.gov.com/graphics/taxuser2.jpg	32502
http://www.gov.com/	30605
https://www.google-analytics.com/analytics.js	19452
http://www.gov.com/gov.css	12667
http://www.gov.com/graphics/GOV_ban2.gif	4455
http://www.gov.com/graphics/GOV_ban3.gif	4281
http://www.gov.com/graphics/GOV_ban1.gif	3040
http://www.gov.com/graphics/nav25_home.gif	2581
http://www.gov.com/graphics/taxbutton.gif	2554

Show Details

Avoids an excessive DOM size — 515 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.

Statistic	Element	Value
Total DOM Elements		515
Maximum DOM Depth	SHOW DETAILS	20
Maximum Child Elements	SHOW DETAILS	36

Show Details

Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Gov.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

URL	Total CPU Time (Ms)	Script Evaluation (Ms)	Script Parse (Ms)
http://www.gov.com/	51.924	2.842	1.401

Show Details

Minimizes main-thread work — 0.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

Category	Time Spent (Ms)
Script Evaluation	36.827
Other	22.517
Style & Layout	19.915
Rendering	15.931
Parse HTML & CSS	8.378
Script Parsing & Compilation	4.72

Show Details

All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.

Keep request counts low and transfer sizes small — 16 requests • 152 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.

Resource Type	Requests	Transfer Size (Bytes)
Total	16	155334
Script	2	59157
Image	10	52020
Document	1	30605
Stylesheet	1	12667
Other	2	885
Media	0	0
Font	0	0
Third-party	4	60042

Show Details

Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Third-Party	Transfer Size (Bytes)	Main-Thread Blocking Time (Ms)
SHOW DETAILS	39705	0
SHOW DETAILS	20070	0

Show Details

Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.

Element
Consular Information Sheets are available for every country of the world. They …

Show Details

Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.

Element	CLS Contribution
• simple and accurate • more deductions & tax credits • the fastest refund …	0.002468545338801
Simply and accurately prepare and e-file your taxes online with GOV for a speed…	0.0020461706610594
Now compatible with your mobile devices!	0.00060071065278807
Prepare & e-file taxes online with GOV	0.00060071065278807
click here now	0.0004129885737918

Show Details

Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 1.0 s
The time taken for the first image or text on the page to be rendered.

Other

First Meaningful Paint — 1.0 s
The time taken for the primary content of the page to be rendered.

Diagnostics

Serve static assets with an efficient cache policy — 12 resources found
Gov.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.

URL	Cache TTL (Ms)	Transfer Size (Bytes)
http://www.gov.com/graphics/taxuser2.jpg	0	32502
http://www.gov.com/gov.css	0	12667
http://www.gov.com/graphics/GOV_ban2.gif	0	4455
http://www.gov.com/graphics/GOV_ban3.gif	0	4281
http://www.gov.com/graphics/GOV_ban1.gif	0	3040
http://www.gov.com/graphics/nav25_home.gif	0	2581
http://www.gov.com/graphics/taxbutton.gif	0	2554
http://www.gov.com/graphics/GOV_130x85.gif	0	1531
http://www.gov.com/graphics/2x25.gif	0	426
http://www.gov.com/graphics/1x1_EEEEEE.gif	0	325
http://www.gov.com/graphics/1x1_white.gif	0	325
https://www.google-analytics.com/analytics.js	7200000	19452

Show Details

Diagnostics

Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.

URL	Location
http://www.gov.com/	line: 93

Show Details

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of gov.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.

The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.

Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.

`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.

ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.

`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.

`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.

`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.

ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.

`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.

`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.

`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.

`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.

Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.

`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.

Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.

Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.

`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Gov.com may provide assistance to deaf or hearing-impaired users with captions on videos.

`<video>` elements contain a `<track>` element with `[kind="description"]`
Gov.com may provide relevant information that dialogue cannot, by using audio descriptions.

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.

Failing Elements
html

Show Details

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img

Show Details

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Failing Elements
a
a
a

Show Details

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.

Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.

Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.

The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.

User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.

Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.

Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.

Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.

Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.

HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that gov.com should incorporate. This includes practices such as protecting pages with HTTPS.

Passing (14)
Failing (3)

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.

Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Avoids Application Cache
Application cache is deprecated and is no longer recommended.

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.

Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 13 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.

Insecure URL
http://gov.com/
http://www.gov.com/
http://www.gov.com/gov.css
http://www.gov.com/graphics/GOV_130x85.gif
http://www.gov.com/graphics/GOV_ban1.gif
http://www.gov.com/graphics/GOV_ban2.gif
http://www.gov.com/graphics/GOV_ban3.gif
http://www.gov.com/graphics/nav25_home.gif
http://www.gov.com/graphics/1x1_white.gif
http://www.gov.com/graphics/taxuser2.jpg
http://www.gov.com/graphics/1x1_EEEEEE.gif
http://www.gov.com/graphics/taxbutton.gif
http://www.gov.com/graphics/2x25.gif

Show Details

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

URL	Displayed size	Actual size	Expected size
http://www.gov.com/graphics/1x1_white.gif	350 x 40	1 x 1	350 x 40
http://www.gov.com/graphics/1x1_EEEEEE.gif	160 x 18	1 x 1	160 x 18

Show Details

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for gov.com. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.

Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.

Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.

Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.

Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of gov.com on mobile screens.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img

Show Details

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of gov.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.

`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 13 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.

Insecure URL
http://gov.com/
http://www.gov.com/
http://www.gov.com/gov.css
http://www.gov.com/graphics/GOV_130x85.gif
http://www.gov.com/graphics/GOV_ban1.gif
http://www.gov.com/graphics/GOV_ban2.gif
http://www.gov.com/graphics/GOV_ban3.gif
http://www.gov.com/graphics/nav25_home.gif
http://www.gov.com/graphics/1x1_white.gif
http://www.gov.com/graphics/taxuser2.jpg
http://www.gov.com/graphics/1x1_EEEEEE.gif
http://www.gov.com/graphics/taxbutton.gif
http://www.gov.com/graphics/2x25.gif

Show Details

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.

Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of gov.com on mobile screens.

Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.

Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.

Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: http://www.gov.com/

Updated: 28th December, 2020

3.13 seconds

First Contentful Paint (FCP)

21%

53%

26%

0.26 seconds

First Input Delay (FID)

7%

85%

8%

Simulate loading on mobile

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for gov.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 3.5 s
The time taken for the page to become fully interactive.

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Cumulative Layout Shift — 0.002
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 3.5 s
The time taken for the page's main thread to be quiet enough to handle input.

Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive gov.com as laggy when the latency is higher than 0.05 seconds.

Network Requests
Below is a list of network requests that were made during page load.

URL	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://gov.com/	0	123.30900016241	267	0	301	text/html
http://www.gov.com/	123.71800001711	309.86800021492	30605	30318	200	text/html	Document
https://www.googletagmanager.com/gtag/js?id=UA-138241245-1	321.19800010696	337.36200002022	39705	98729	200	application/javascript	Script
http://www.gov.com/gov.css	321.35800016113	444.36400011182	12667	12381	200	text/css	Stylesheet
http://www.gov.com/graphics/GOV_130x85.gif	323.6100000795	447.1790001262	1531	1246	200	image/gif	Image
http://www.gov.com/graphics/GOV_ban1.gif	323.76500009559	448.27000005171	3040	2755	200	image/gif	Image
http://www.gov.com/graphics/GOV_ban2.gif	323.86700017378	509.39500005916	4455	4169	200	image/gif	Image
http://www.gov.com/graphics/GOV_ban3.gif	324.2390002124	448.04300018586	4281	3996	200	image/gif	Image
http://www.gov.com/graphics/nav25_home.gif	324.38500015996	508.12800019048	2581	2296	200	image/gif	Image
http://www.gov.com/graphics/1x1_white.gif	324.56500013359	504.13100002334	325	43	200	image/gif	Image
http://www.gov.com/graphics/taxuser2.jpg	324.69200016931	569.98600019142	32502	32214	200	image/jpeg	Image
http://www.gov.com/graphics/1x1_EEEEEE.gif	324.91500000469	508.37900000624	325	43	200	image/gif	Image
http://www.gov.com/graphics/taxbutton.gif	325.08300011978	447.72500009276	2554	2269	200	image/gif	Image
https://www.google-analytics.com/analytics.js	360.39400007576	365.14700017869	19452	47051	200	text/javascript	Script
http://www.gov.com/graphics/2x25.gif	374.08900004812	564.87900018692	426	143	200	image/gif	Image
https://www.google-analytics.com/j/collect?v=1&_v=j87&a=1209190058&t=pageview&_s=1&dl=http%3A%2F%2Fwww.gov.com%2F&ul=en-us&de=windows-1252&dt=Making%20Government%20User-friendly%20-%20Government%20Information&sd=24-bit&sr=360x640&vp=980x1742&je=0&_u=IEBAAUABAAAAAC~&jid=1719335654&gjid=1541376747&cid=1313113567.1609145099&tid=UA-138241245-1&_gid=1395653355.1609145099&_r=1&gtm=2oubu0&z=234497573	388.41800019145	391.51000021957	618	1	200	text/plain	XHR

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
336.014	6.488
369.116	7.548
377.423	7.041
392.741	20.155
469.989	9.357
479.361	16.789

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Gov.com should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Gov.com should consider lazy-loading offscreen and hidden images.

Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Gov.com should consider minifying CSS files.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
http://www.gov.com/gov.css	12667	2593

Show Details

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Gov.com should consider minifying JS files.

Remove unused CSS — Potential savings of 10 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Gov.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
http://www.gov.com/gov.css	12667	10513

Show Details

Remove unused JavaScript — Potential savings of 21 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
https://www.googletagmanager.com/gtag/js?id=UA-138241245-1	39705	21671

Show Details

Efficiently encode images — Potential savings of 25 KiB
Unoptimized images can consume more cellular data than what is necessary.

URL	Resource Size (Bytes)	Potential Savings (Bytes)
http://www.gov.com/graphics/taxuser2.jpg	32214	25845

Show Details

Serve images in next-gen formats — Potential savings of 27 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.

URL	Resource Size (Bytes)	Potential Savings (Bytes)
http://www.gov.com/graphics/taxuser2.jpg	32214	27772

Show Details

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Initial server response time was short — Root document took 190 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.

URL	Time Spent (Ms)
http://www.gov.com/	187.149

Show Details

Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Gov.com should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
http://gov.com/	630
http://www.gov.com/	0

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Gov.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.

Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

Diagnostics

Avoids enormous network payloads — Total size was 152 KiB
Large network payloads can cost users money and are linked to long load times.

URL	Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=UA-138241245-1	39705
http://www.gov.com/graphics/taxuser2.jpg	32502
http://www.gov.com/	30605
https://www.google-analytics.com/analytics.js	19452
http://www.gov.com/gov.css	12667
http://www.gov.com/graphics/GOV_ban2.gif	4455
http://www.gov.com/graphics/GOV_ban3.gif	4281
http://www.gov.com/graphics/GOV_ban1.gif	3040
http://www.gov.com/graphics/nav25_home.gif	2581
http://www.gov.com/graphics/taxbutton.gif	2554

Show Details

Avoids an excessive DOM size — 515 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.

Statistic	Element	Value
Total DOM Elements		515
Maximum DOM Depth	SHOW DETAILS	20
Maximum Child Elements	SHOW DETAILS	36

Show Details

Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Gov.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

URL	Total CPU Time (Ms)	Script Evaluation (Ms)	Script Parse (Ms)
http://www.gov.com/	195.388	10.528	4.876
https://www.google-analytics.com/analytics.js	84.752	62.968	4.004
https://www.googletagmanager.com/gtag/js?id=UA-138241245-1	67.156	54.232	7.804
Unattributable	55.004	3.724	0.468

Show Details

Minimizes main-thread work — 0.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

Category	Time Spent (Ms)
Script Evaluation	131.452
Other	87.808
Style & Layout	82.836
Rendering	54.324
Parse HTML & CSS	32.328
Script Parsing & Compilation	17.152

Show Details

All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.

Keep request counts low and transfer sizes small — 16 requests • 152 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.

Resource Type	Requests	Transfer Size (Bytes)
Total	16	155334
Script	2	59157
Image	10	52020
Document	1	30605
Stylesheet	1	12667
Other	2	885
Media	0	0
Font	0	0
Third-party	4	60042

Show Details

Minimize third-party usage — Third-party code blocked the main thread for 10 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Third-Party	Transfer Size (Bytes)	Main-Thread Blocking Time (Ms)
SHOW DETAILS	20070	9.928
SHOW DETAILS	39705	0

Show Details

Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.

Element
Consular Information Sheets are available for every country of the world. They …

Show Details

Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.

Element	CLS Contribution
• simple and accurate • more deductions & tax credits • the fastest refund …	0.00065166233641728
Simply and accurately prepare and e-file your taxes online with GOV for a speed…	0.00053355309345124
Now compatible with your mobile devices!	0.00013545500265038
Prepare & e-file taxes online with GOV	0.00013545500265038
click here now	9.3125314322133E-5

Show Details

Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 3.5 s
The time taken for the first image or text on the page to be rendered.

Speed Index — 3.5 s
The time taken for the page contents to be visibly populated.

Largest Contentful Paint — 3.8 s
The timing of the largest text or image that is painted.

Other

First Meaningful Paint — 3.5 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 150 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Gov.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

URL	Transfer Size (Bytes)	Potential Savings (Ms)
http://www.gov.com/gov.css	12667	330

Show Details

Enable text compression — Potential savings of 35 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
http://www.gov.com/	30318	24714
http://www.gov.com/gov.css	12381	11520

Show Details

Diagnostics

Serve static assets with an efficient cache policy — 12 resources found
Gov.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.

URL	Cache TTL (Ms)	Transfer Size (Bytes)
http://www.gov.com/graphics/taxuser2.jpg	0	32502
http://www.gov.com/gov.css	0	12667
http://www.gov.com/graphics/GOV_ban2.gif	0	4455
http://www.gov.com/graphics/GOV_ban3.gif	0	4281
http://www.gov.com/graphics/GOV_ban1.gif	0	3040
http://www.gov.com/graphics/nav25_home.gif	0	2581
http://www.gov.com/graphics/taxbutton.gif	0	2554
http://www.gov.com/graphics/GOV_130x85.gif	0	1531
http://www.gov.com/graphics/2x25.gif	0	426
http://www.gov.com/graphics/1x1_EEEEEE.gif	0	325
http://www.gov.com/graphics/1x1_white.gif	0	325
https://www.google-analytics.com/analytics.js	7200000	19452

Show Details

Diagnostics

Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.

URL	Location
http://www.gov.com/	line: 93

Show Details

Other

First Contentful Paint (3G) — 6760 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.