Website review, no card needed

leg.state.nv.us logo

leg.state.nv.us website review

Visit site (opens in a new tab)Reviewed 1 November 202632 issues · 76 checks

This review found 32 issues worth fixing on leg.state.nv.us, 7 of them high impact, across 76 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
951 ms787 msMay 9Oct 24861 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026817 ms
May 16, 2026826 ms
May 23, 2026850 ms
May 30, 2026893 ms
Jun 6, 2026915 ms
Jun 13, 2026919 ms
Jun 20, 2026907 ms
Jun 27, 2026879 ms
Jul 4, 2026928 ms
Jul 11, 2026925 ms
Jul 18, 2026932 ms
Jul 25, 2026927 ms
Aug 1, 2026868 ms
Aug 8, 2026849 ms
Aug 15, 2026852 ms
Aug 22, 2026872 ms
Aug 29, 2026885 ms
Sep 5, 2026897 ms
Sep 12, 2026887 ms
Sep 19, 2026867 ms
Sep 26, 2026839 ms
Oct 3, 2026833 ms
Oct 10, 2026806 ms
Oct 17, 2026838 ms
Oct 24, 2026861 ms
Real-visitor tap response (INP)75th percentile, phones
292 ms266 msMay 9Oct 24288 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026286 ms
May 16, 2026286 ms
May 23, 2026284 ms
May 30, 2026285 ms
Jun 6, 2026284 ms
Jun 13, 2026283 ms
Jun 20, 2026283 ms
Jun 27, 2026284 ms
Jul 4, 2026270 ms
Jul 11, 2026269 ms
Jul 18, 2026270 ms
Jul 25, 2026270 ms
Aug 1, 2026284 ms
Aug 8, 2026288 ms
Aug 15, 2026289 ms
Aug 22, 2026287 ms
Aug 29, 2026287 ms
Sep 5, 2026286 ms
Sep 12, 2026282 ms
Sep 19, 2026282 ms
Sep 26, 2026280 ms
Oct 3, 2026280 ms
Oct 10, 2026286 ms
Oct 17, 2026284 ms
Oct 24, 2026288 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

Full-page screenshot of leg.state.nv.us (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. leg.state.nv.us at 0.4 s0.4 s
  2. leg.state.nv.us at 0.8 s0.8 s
  3. leg.state.nv.us at 1.1 s1.1 s
  4. leg.state.nv.us at 1.5 s1.5 s
  5. leg.state.nv.us at 1.9 s1.9 s
  6. leg.state.nv.us at 2.3 s2.3 s
  7. leg.state.nv.us at 2.6 s2.6 s
  8. leg.state.nv.us at 3.0 s3.0 s

Speed

4 to fix93
  • Render-blocking requests

    1.5 s

    13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.

  • Use efficient cache lifetimes

    50 ms · 1.4 MB

    18 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

  • Improve image delivery

    1.3 MB

    2 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google Tag Manager adds 236 ms

    236 ms

    Google Tag Manager costs a phone 236 ms of main-thread work and 307 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Feedbackify and FontAwesome CDN and others), adding 456 KiB and 297 ms of main-thread time.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 177 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    138 KiB

    About 138 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    59 KiB

    About 59 KiB of CSS is downloaded but never applied on this page.

  • 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.

3 checks passed
  • Mobile performance score: 93

    93/100

    Your mobile performance score is 93. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 286 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Time to Interactive: 5.9 s

    5.9 s

    The page becomes fully interactive after 5.9 s. Good is under 3.8 s.

  • First Contentful Paint: 2.3 s

    2.3 s

    The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

  • Speed Index: 4.2 s

    4.2 s

    Visually, the page fills in at 4.2 s (Speed Index). Good is under 3.4 s.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 286 ms to 288 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 79 ms

    79 ms

    Real visitors wait 79 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 314 ms

    314 ms

    Real visitors wait 314 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 2.3 s

    2.3 s

    Your largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “BDR (bill draft request) forms for the 84th (2027) Session …”.

  • Total Blocking Time: 85 ms

    85 ms

    Scripts block the page for only 85 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix50
  • 1 image over 500 KB

    LegislativeBuildingNew.png weighs 1.1 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 2.0 MB in 36 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 36 requests on a phone: images 1.5 MB (6), scripts 392 KiB (10) and fonts 57 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (1.4 MB) 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

    399 KiB

    1 image is downloaded at several times the size a phone draws it, for example lcb-logo-without-tagline-lg.png at 6,994 px wide, shown at 205 px. Resized copies would save about 399 KiB.

  • About 0.6 g of CO₂ per visit

    0.57 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

2 to fixGoogle 9696
  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • 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 6 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 10066
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (18 characters)

    Your title is only 18 characters: “Nevada Legislature”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (191 characters)

    Your meta description is 191 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No XML sitemap

    No XML sitemap at https://www.leg.state.nv.us/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 146 internal links, 7 external

    The homepage links to 146 pages on leg.state.nv.us and 7 external pages.

2 checks passed
  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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.leg.state.nv.us/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 (585 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix67
  • 1 page without a title

    https://www.leg.state.nv.us/Session/75th2009 has no <title>, so Google invents the link text in results.

  • 3 pages share a title

    https://www.leg.state.nv.us/App/NELIS/REL, https://www.leg.state.nv.us/Session/36th2025Special and https://www.leg.state.nv.us/Session/83rd2025 all use the title “NELIS Home”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://www.leg.state.nv.us/Session, https://www.leg.state.nv.us/Session/35th2023Special, https://www.leg.state.nv.us/Session/34th2023Special, https://www.leg.state.nv.us/Session/82nd2023, https://www.leg.state.nv.us/Session/81st2021 and https://www.leg.state.nv.us/Session/80th2019 and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.leg.state.nv.us/App/NELIS/REL, https://www.leg.state.nv.us/Session/36th2025Special and https://www.leg.state.nv.us/Session/83rd2025 use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.leg.state.nv.us/Session/75th2009 has 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 112 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

1 to fixGoogle 8197
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    31 of 36 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 240 words

    The homepage has only about 240 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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.

2 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Nevada Register”, “Contact CSU” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (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.

  • 10 other companies contacted

    Loading the homepage contacts 10 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 leg.state.nv.us, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Founded
1864
Headquarters
Nevada State Legislative Building

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on leg.state.nv.us, including 8 speed issues, 6 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25