Skip to content
https://tobaccoseedshop.com

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

99

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div#seed-carousel > a.carousel-slide > picture > img div#seed-carousel > a.carousel-slide > picture > img
tobaccoseedshop.com/Images/Seeds/Turkish_Basma.thumb.webp?v=178456099360.1 KiB50.9 KiB
div#seed-carousel > a.carousel-slide > picture > img div#seed-carousel > a.carousel-slide > picture > img
tobaccoseedshop.com/Images/Seeds/Burley_TN92.thumb.webp?v=178456097741.9 KiB32.7 KiB
div#seed-carousel > a.carousel-slide > picture > img div#seed-carousel > a.carousel-slide > picture > img
tobaccoseedshop.com/Images/Seeds/Black_Mammoth.thumb.webp?v=178456097638.4 KiB29.2 KiB
div#seed-carousel > a.carousel-slide > picture > img div#seed-carousel > a.carousel-slide > picture > img
tobaccoseedshop.com/Images/Seeds/Yellow_Twist_Bud.thumb.webp?v=178456099636.6 KiB27.6 KiB
div#seed-carousel > a.carousel-slide > picture > img div#seed-carousel > a.carousel-slide > picture > img
tobaccoseedshop.com/Images/Seeds/Banana_Leaf.thumb.webp?v=178456097535.6 KiB26.9 KiB
div#seed-carousel > a.carousel-slide > picture > img div#seed-carousel > a.carousel-slide > picture > img
tobaccoseedshop.com/Images/Seeds/NC_95.thumb.webp?v=178456098730.6 KiB23.1 KiB
div#seed-carousel > a.carousel-slide > picture > img div#seed-carousel > a.carousel-slide > picture > img
tobaccoseedshop.com/Images/Seeds/Shirey.thumb.webp?v=178456099226.6 KiB20.1 KiB
div#seed-carousel > a.carousel-slide > picture > img div#seed-carousel > a.carousel-slide > picture > img
tobaccoseedshop.com/Images/Seeds/Pelleted_Turkish_Basma.thumb.webp?v=178456098931.3 KiB19.0 KiB
div#seed-carousel > a.carousel-slide > picture > img div#seed-carousel > a.carousel-slide > picture > img
tobaccoseedshop.com/Images/Seeds/Oxford_207.thumb.webp?v=178456098722.8 KiB17.2 KiB
div#seed-carousel > a.carousel-slide > picture > img div#seed-carousel > a.carousel-slide > picture > img
tobaccoseedshop.com/Images/Seeds/Paris_Wrapper.thumb.webp?v=178456098822.8 KiB17.2 KiB
Tobacco Seed Shop Est. 1999 div.logo > a > picture > img.site-logo-img
tobaccoseedshop.com/Images/branding/logo.webp?v=178456097424.4 KiB11.4 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.5 KiB
URLTransfer SizeEst Savings
/** * Site-wide theme — parchment beige & warm brown (matches logo). */ :root { --font-family: …9.2 KiB2.5 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Use efficient cache lifetimes
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Network dependency tree
●Render blocking requests
●Optimize viewport for mobile
●Time to Interactive 0.8 s
●Max Potential First Input Delay 20 ms
●Minify JavaScript
●Reduce unused CSS
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 436 KiB
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.2 s
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 0 ms
●Server Backend Latencies 470 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 400 ms
○INP breakdown
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid non-composited animations
○Avoid large layout shifts
96

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
HOME div.site-footer-grid > div.site-footer-col > h3.site-footer-col-title > a
Browse seeds div.site-footer-col > ul.site-footer-links > li > a
Growing guides div.site-footer-col > ul.site-footer-links > li > a
TOBACCO SEEDS div.site-footer-grid > div.site-footer-col > h3.site-footer-col-title > a
Rustica div.site-footer-col > ul.site-footer-links > li > a
GROWING TOBACCO div.site-footer-grid > div.site-footer-col > h3.site-footer-col-title > a
All articles div.site-footer-col > ul.site-footer-links > li > a
Starting Seeds div.site-footer-col > ul.site-footer-links > li > a
LEGAL div.site-footer-grid > div.site-footer-col > h3.site-footer-col-title > a
Disclaimer & Limitation of Liability div.site-footer-col > ul.site-footer-links > li > a
Privacy & Personal Data div.site-footer-col > ul.site-footer-links > li > a
ABOUT US div.site-footer-grid > div.site-footer-col > h3.site-footer-col-title > a
Quality & Plant Health div.site-footer-col > ul.site-footer-links > li > a
About Our Seeds div.site-footer-col > ul.site-footer-links > li > a

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
tobaccoseedshop.com/favicon.png
Failed to load resource: the server responded with a status of 404 ()
●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback