Website review, no card needed
justice.gov website review
Visit site (opens in a new tab)Reviewed 12 October 202645 issues · 86 checks
This review found 45 issues worth fixing on justice.gov, 21 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 411 ms |
| Apr 25, 2026 | 442 ms |
| May 2, 2026 | 501 ms |
| May 9, 2026 | 535 ms |
| May 16, 2026 | 570 ms |
| May 23, 2026 | 600 ms |
| May 30, 2026 | 613 ms |
| Jun 6, 2026 | 652 ms |
| Jun 13, 2026 | 713 ms |
| Jun 20, 2026 | 717 ms |
| Jun 27, 2026 | 716 ms |
| Jul 4, 2026 | 642 ms |
| Jul 11, 2026 | 605 ms |
| Jul 18, 2026 | 609 ms |
| Jul 25, 2026 | 610 ms |
| Aug 1, 2026 | 678 ms |
| Aug 8, 2026 | 698 ms |
| Aug 15, 2026 | 704 ms |
| Aug 22, 2026 | 721 ms |
| Aug 29, 2026 | 739 ms |
| Sep 5, 2026 | 730 ms |
| Sep 12, 2026 | 697 ms |
| Sep 19, 2026 | 654 ms |
| Sep 26, 2026 | 589 ms |
| Oct 3, 2026 | 541 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 95 ms |
| Apr 25, 2026 | 95 ms |
| May 2, 2026 | 95 ms |
| May 9, 2026 | 94 ms |
| May 16, 2026 | 95 ms |
| May 23, 2026 | 95 ms |
| May 30, 2026 | 95 ms |
| Jun 6, 2026 | 95 ms |
| Jun 13, 2026 | 94 ms |
| Jun 20, 2026 | 94 ms |
| Jun 27, 2026 | 95 ms |
| Jul 4, 2026 | 95 ms |
| Jul 11, 2026 | 94 ms |
| Jul 18, 2026 | 94 ms |
| Jul 25, 2026 | 94 ms |
| Aug 1, 2026 | 94 ms |
| Aug 8, 2026 | 94 ms |
| Aug 15, 2026 | 94 ms |
| Aug 22, 2026 | 94 ms |
| Aug 29, 2026 | 93 ms |
| Sep 5, 2026 | 93 ms |
| Sep 12, 2026 | 92 ms |
| Sep 19, 2026 | 92 ms |
| Sep 26, 2026 | 92 ms |
| Oct 3, 2026 | 92 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.4 s
2.7 s
4.1 s
5.4 s
6.8 s
8.1 s
9.5 s
10.8 s
Speed
Reduce unused JavaScript
22.9 s · 8.2 MBAbout 8.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 22.9 s faster on a phone.
Use efficient cache lifetimes
4.3 s · 2.5 MB99 files are served with short cache lifetimes, so returning visitors download them again (2.5 MB).
YouTube adds 3.9 s
3.9 sYouTube costs a phone 3.9 s of main-thread work and 14.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Reduce unused CSS
2.4 s · 230 KiBAbout 230 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Render-blocking requests
1.9 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Main-thread work: 16.4 s
A phone's processor spends 16.4 s on main-thread work while loading, 10.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 25
25/100Your mobile performance score is 25 (desktop: 23). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 14.7 MB and 4.1 s of main-thread time.
Improve image delivery
880 KiB13 images could be 880 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 440 ms. During a long task the page ignores taps.
1,645 HTML elements
The page has 1,645 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
First Contentful Paint: 29.8 s
29.8 sThe first text or image appears after 29.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 36.6 s
36.6 sYour largest element takes 36.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Attorney General Blanche Hosts Roundtable on Violent Crime …”.
Speed Index: 36.8 s
36.8 sVisually, the page fills in at 36.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 112.2 s
112.2 sThe page becomes fully interactive after 112.2 s. Good is under 3.8 s.
Total Blocking Time: 2.6 s
2.6 sScripts block taps and scrolling for 2.6 s in total while the page loads. Good is under 200 ms.
Real-user INP: 203 ms
203 msReal visitors wait 203 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 0.4 s to 0.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 95 ms to 92 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 553 ms
553 msReal visitors wait 553 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.072
0.072The layout barely moves while loading (CLS 0.072, good is under 0.1).
Images and page weight
Page weight: 20.4 MB in 358 requests
20.4 MBYour homepage downloads 20.4 MB in 358 requests on a phone: scripts 15.9 MB (97), images 1.6 MB (52) and stylesheets 1.1 MB (52). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
building_2.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images in older formats
2 images (627 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
1 image far larger than shown
78 KiB1 image is downloaded at several times the size a phone draws it, for example image at 1,123 px wide, shown at 290 px. Resized copies would save about 78 KiB.
4 images below the first screen load straight away
4 images further down the page (265 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.8 g of CO₂ per visit
5.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.79 g of CO₂e: 694.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 49 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Department of Justice | Homepage | United States Department of Justice”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (431 characters)
Your meta description is 431 characters; Google truncates after about 160, so the end of your pitch is cut.
Open Graph partly set
Open Graph is missing og:title, so shared links fall back to guesses.
75 internal links, 23 external
The homepage links to 75 pages on justice.gov and 23 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.justice.gov/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.justice.gov/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.justice.gov/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,167 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without a title
https://www.justice.gov/news, https://www.justice.gov/news/press-releases, https://www.justice.gov/news/speeches, https://www.justice.gov/news/videos and https://www.justice.gov/news/photo-galleries have no <title>, so Google invents the link text in results.
2 pages share a title
https://www.justice.gov/agencies/chart/grid and https://www.justice.gov/agencies/chart/map all use the title “Department of Justice | Grid/Map View | United States Department of J…”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://www.justice.gov/agencies/chart/grid, https://www.justice.gov/action-center/find-help-and-information-crime-victims, https://www.justice.gov/contact-us, https://www.justice.gov/about, https://www.justice.gov/ag and https://www.justice.gov/agencies/chart/map and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.justice.gov/news, https://www.justice.gov/news/press-releases, https://www.justice.gov/news/speeches, https://www.justice.gov/news/videos and https://www.justice.gov/news/photo-galleries have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 58 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
5 broken images
5 images failed to load on a phone, for example https://www.fbi.gov/wanted/topten/samuel-ramirez-jr/@@images/image.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught Error: YouTube player element ID required.”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
2 checks passed
Tap targets are thumb-sized
33 of 35 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,327 words of copy
The homepage carries about 1,327 words of visible text.
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Contact Us”, “Contact DOJ” and “Contact the Department”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
8 cookies set on arrival
8Opening the homepage sets 8 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
18 other companies contacted
Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at justice.gov, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on justice.gov, including 20 speed issues, 4 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.