Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
ticksy.com/wp-content/themes/ticksy/css/images/window.png	14400.0 s	137.9 KiB
ticksy.com/wp-content/themes/ticksy/css/images/desk.jpg	14400.0 s	49.1 KiB
cdn.mxpnl.com/libs/mixpanel-2-latest.min.js	600.0 s	31.7 KiB
ticksy.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	14400.0 s	33.6 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
ticksy.com/wp-includes/css/dist/block-library/style.min.css?ver=6.5.8	14400.0 s	18.2 KiB
/wp-content/plugins/gdpr-cookie-compliance/dist/scripts/m...	14400.0 s	17.8 KiB
/wp-content/plugins/gdpr-cookie-compliance/dist/styles/gd...	14400.0 s	11.3 KiB
/ticksy-wp-media/wp/wp-content/uploads/2015/03/31191158/c...	0.0 ms	6.4 KiB
ticksy.com/wp-content/themes/ticksy/style.css?ver=6.5.8	14400.0 s	8.7 KiB
ticksy.com/wp-content/themes/ticksy/css/images/logo.png	14400.0 s	7.1 KiB
/ticksy-wp-media/wp/wp-content/uploads/2015/03/31182103/t...	0.0 ms	4.6 KiB
ticksy.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	14400.0 s	5.2 KiB
widget.intercom.io/widget/x7mv1bds	300.0 s	3.6 KiB
ticksy.com/wp-content/themes/ticksy/js/ticksy_custom.js	14400.0 s	2.8 KiB
ticksy.disqus.com/count.js	300.0 s	1.5 KiB
ticksy.com/wp-content/themes/ticksy/css/responsive.css?ver=6.5.8	14400.0 s	1.2 KiB
/wp-content/plugins/disqus-comment-system/public/js/comme...	14400.0 s	870 B
/wp-content/plugins/disqus-comment-system/public/js/comme...	14400.0 s	529 B
ticksy.com/wp-content/themes/ticksy/js/ticksy_mixpanel.js	14400.0 s	331 B
/wp-content/plugins/sola-testimonials//includes/gutenberg...	14400.0 s	144 B
/wp-content/plugins/sola-testimonials//includes/gutenberg...	14400.0 s	106 B

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
fonts.gstatic.com/s/rubik/v31/iJWKBXyIfDnIV7nBrXyw023e.woff2	30 ms

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: div#content > div#intro-area > div.intro-content > img.visible

path: 1,HTML,1,BODY,1,DIV,0,DIV,0,DIV,1,IMG

selector: div#content > div#intro-area > div.intro-content > img.visible

snippet: <img src="https://ticksy.com/wp-content/themes/ticksy/css/images/window.png" class="visible">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
use.fortawesome.com/dc1c57f5.js	0 B	230 ms
fonts.googleapis.com/css?family=Rubik%3A300%2C400%2C500%2C700&ver=6.5.8	1.3 KiB	268 ms
ticksy.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.2 KiB
/wp-content/plugins/gdpr-cookie-compliance/dist/styles/gd...	11.3 KiB
ticksy.com/wp-content/themes/ticksy/css/responsive.css?ver=6.5.8	1.2 KiB
ticksy.com/wp-content/themes/ticksy/style.css?ver=6.5.8	8.7 KiB	57 ms
ticksy.com/wp-includes/css/dist/block-library/style.min.css?ver=6.5.8	18.2 KiB	57 ms
/wp-content/plugins/sola-testimonials//includes/gutenberg...	106 B
/wp-content/plugins/sola-testimonials//includes/gutenberg...	144 B
ticksy.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	33.6 KiB	113 ms

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.

	URL	Resource Size	Est Savings
div#content > div#intro-area > div.intro-content > img.visible `div#content > div#intro-area > div.intro-content > img.visible`	ticksy.com/wp-content/themes/ticksy/css/images/window.png	139.0 KiB	103.4 KiB
div.shell > ul.cf > li > img `div.shell > ul.cf > li > img`	/ticksy-wp-media/wp/wp-content/uploads/2015/03/31191158/c...	6.0 KiB	5.4 KiB

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

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 490 ms 591.3 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	241.8 KiB
js.intercomcdn.com/frame-modern.7a9f78bc.js	192.7 KiB	133.9 KiB
js.intercomcdn.com/vendor-modern.80eace52.js	143.3 KiB	90.3 KiB
www.googletagmanager.com/gtag/js?id=G-X2W3123QHE&cx=c&gtm=4e64k0h1	143.7 KiB	63.1 KiB
www.googletagmanager.com/gtag/js?id=UA-140333453-1	124.9 KiB	62.1 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 29.0 KiB

URL	Transfer Size	Est Savings
ticksy.com/wp-includes/css/dist/block-library/style.min.css?ver=6.5.8	18.2 KiB	18.1 KiB
/wp-content/plugins/gdpr-cookie-compliance/dist/styles/gd...	11.3 KiB	10.8 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
div#content > div#intro-area > div.intro-content > img.visible `div#content > div#intro-area > div.intro-content > img.visible`	ticksy.com/wp-content/themes/ticksy/css/images/window.png
div.shell > ul.cf > li > img `div.shell > ul.cf > li > img`	/ticksy-wp-media/wp/wp-content/uploads/2015/03/31182103/t...
div.shell > ul.cf > li > img `div.shell > ul.cf > li > img`	/ticksy-wp-media/wp/wp-content/uploads/2015/03/31191158/c...

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

●Max Potential First Input Delay 110 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,400 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.6 s

●Avoid long main-thread tasks 1 long task found

●Avoid non-composited animations 3 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 30 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 30 ms

●Avoid large layout shifts 9 layout shifts found

○INP breakdown

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ACCOUNT `div.menu-main-navigation-container > ul#menu-main-navigation > li#menu-item-801 > a`
UPDATES `div.menu-main-navigation-container > ul#menu-main-navigation > li#menu-item-728 > a`
NEED HELP? `div.menu-main-navigation-container > ul#menu-main-navigation > li#menu-item-344 > a`
PRICING & SIGNUP `div.menu-main-navigation-container > ul#menu-main-navigation > li#menu-item-886 > a`
CONTACT `div.menu-main-navigation-container > ul#menu-main-navigation > li#menu-item-850 > a`
Private tickets are just between you and your customers, but Public tickets are… `ul.cf > li > div.content > p`
(public tickets are optional) `li > div.content > p > small`
Connect your Envato Market account to provide your customers with a one-click s… `ul.cf > li > div.content > p`
Envato Market `div.content > p > strong > a`
one-click solution `li > div.content > p > em`
Easy Digital Downloads `div.content > p > strong > a`
Themely Marketplace `div.content > p > strong > a`
Freemius `div.content > p > strong > a`
Create an unlimited number of articles and assigned them to one or more categor… `ul.cf > li > div.content > p`
Branding is important, which is why with Ticksy you can choose a custom subdoma… `ul.cf > li > div.content > p`
Stay in the loop. Email notifications are sent out for each new ticket & reply.… `ul.cf > li > div.content > p`
(you can enable and disable specific notifications) `li > div.content > p > small`
Speed is extremely important when it comes to support, which is why Ticksy boas… `ul.cf > li > div.content > p`
You can display your system in several different languages. Your support agents… `ul.cf > li > div.content > p`
English (US & UK), Spanish, French, Italian, Norwegian, Estonian, Dutch, & Chin… `li > div.content > p > small`
Every comment can be "liked" by both the support agents and your customers, pro… `ul.cf > li > div.content > p`
You can define a list of email addresses that your customers can use in order t… `ul.cf > li > div.content > p`
this article `li > div.content > p > a`
If you'd like to ask your customers for multiple details when they submit a tic… `ul.cf > li > div.content > p`
GET STARTED `div.shell > div > a.get-started > span`
Support: https://support.ticksy.com `li > div.content > p > small`
https://support.ticksy.com `div.content > p > small > a`
Phone Number: +1-208-481-8061 `li > div.content > p > small`
Got It! `div.moove-gdpr-info-bar-container > div.moove-gdpr-info-bar-content > div.moove-gdpr-button-holder > button.mgbutton`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#content > div#intro-area > div.intro-content > img.visible `div#content > div#intro-area > div.intro-content > img.visible`
li > div.content > p > img.ticksy-emoticon `li > div.content > p > img.ticksy-emoticon`
div.shell > ul.cf > li > img `div.shell > ul.cf > li > img`
div.shell > ul.cf > li > img `div.shell > ul.cf > li > img`

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.no-js `html.no-js`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.features-row > ul.cf > li > iframe `div.features-row > ul.cf > li > iframe`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#header > div.shell > h1#logo > a `div#header > div.shell > h1#logo > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ACCOUNT UPDATES NEED HELP? PRICING & SIGNUP CONTACT `body.home > div#header > div.shell > ul#main-navigation`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.no-js `html.no-js`

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>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●All heading elements contain content.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

○`[role]`s have all required `[aria-*]` attributes

○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

○`[role]` values are valid

○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

○`<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

○Form elements have associated labels

○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>`.

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

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.

Source	Description
ticksy.com/	`Access to manifest at 'https://ticksy-favicons.s3.amazonaws.com/manifest.json?v=wAAmQ5QG4Y' from origin 'https://ticksy.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
ticksy.com/	`Access to manifest at 'https://ticksy-favicons.s3.amazonaws.com/manifest.json?v=wAAmQ5QG4Y' from origin 'https://ticksy.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
/wp-content/plugins/disqus-comment-system/public/js/comme... line 37, col 16	`Could not find 'disqus_thread' container to load DISQUS. This is usually the result of a WordPress theme conflicting with the DISQUS plugin. Try switching your site to a Classic Theme, or contact DISQUS support for help.`
ticksy-favicons.s3.amazonaws.com/manifest.json?v=wAAmQ5QG4Y	`Failed to load resource: net::ERR_FAILED`
ticksy-favicons.s3.amazonaws.com/manifest.json?v=wAAmQ5QG4Y	`Failed to load resource: net::ERR_FAILED`
api-iam.intercom.io/messenger/web/ping	`Failed to load resource: the server responded with a status of 403 ()`
api-iam.intercom.io/messenger/web/launcher_settings	`Failed to load resource: the server responded with a status of 403 ()`

●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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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.

Content Best Practices

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.no-js `html.no-js`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#content > div#intro-area > div.intro-content > img.visible `div#content > div#intro-area > div.intro-content > img.visible`
li > div.content > p > img.ticksy-emoticon `li > div.content > p > img.ticksy-emoticon`
div.shell > ul.cf > li > img `div.shell > ul.cf > li > img`
div.shell > ul.cf > li > img `div.shell > ul.cf > li > img`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`