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
jigsy.com/images/outside/no-installation_pencils.jpg	0.0 ms	770.5 KiB
jigsy.com/images/outside/support_people.jpg	0.0 ms	457.1 KiB
jigsy.com/images/outside/top_desk.jpg	0.0 ms	288.5 KiB
jigsy.com/images/home/2.png	0.0 ms	222.6 KiB
jigsy.com/images/outside/create-website_girl.jpg	0.0 ms	194.9 KiB
jigsy.com/fonts/fontawesome-webfont.woff2?v=4.3.0	0.0 ms	55.6 KiB
jigsy.com/images/cloudlock2.jpg	0.0 ms	13.4 KiB
jigsy.com/images/jigsy/logo.png	0.0 ms	4.9 KiB
jigsy.com/images/icons/facebook.png	0.0 ms	1.9 KiB
jigsy.com/images/icons/x_formally_known_as_twitter.png	0.0 ms	1.4 KiB
ads.pro-market.net/ads/scripts/site-125361.js	86400.0 s	1.7 KiB

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
jigsy.com/fonts/fontawesome-webfont.woff2?v=4.3.0	185 ms
fonts.gstatic.com/s/catamaran/v28/o-0IIpQoyXQa2RxT7-5r5TRASf6M7Q.woff2	15 ms
/s/opensans/v44/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...	15 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
Picture of a computer, tablet and smart phone `div.container > div.row > div.col-md-6 > img.center_image`	jigsy.com/images/home/2.png	222.3 KiB	194.6 KiB
body#welcome_index > div.parallax-mirror > img.parallax-slider `body#welcome_index > div.parallax-mirror > img.parallax-slider`	jigsy.com/images/outside/top_desk.jpg	288.2 KiB	164.4 KiB

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-1-IMG

nodeLabel: body#welcome_index > div.parallax-mirror > img.parallax-slider

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

selector: body#welcome_index > div.parallax-mirror > img.parallax-slider

snippet: <img class="parallax-slider" src="/images/outside/top_desk.jpg" style="transform: translate3d(0px, 0px, 0px); position: absolute; top: -155px;">

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
jigsy.com/assets/vendor/jquery-3cfe00e2ecb0d8e1640d0b2c9223d1dc.js	96.5 KiB	449 ms
jigsy.com/assets/vendor/swfobject-efc45c928360ca646916d74c578f2b30.js	9.2 KiB
jigsy.com/assets/jigsy-fdc4946dc54563e13a32082fbf07cab8.js	23.1 KiB
/assets/vendor/jquery_plugins/jquery.json-37e05a819459912...	2.0 KiB
jigsy.com/assets/responsive/jigsy.ajaxForms-b02294cb797aa3c7d5e870687ce759c8.js	797 B
jigsy.com/assets/responsive/jigsy.modal-0f89705f8d1433770ce4e4b34512867f.js	10.9 KiB
jigsy.com/assets/responsive/jigsy.countdown-eb7237748346a9b56ca02c5ca99d335b.js	580 B
/assets/vendor/jquery_plugins/jquery.cycle.lite-4c3c59b63...	4.6 KiB
/assets/vendor/jquery_plugins/jquery.fancybox-965e4e6de08...	14.4 KiB	225 ms
jigsy.com/assets/vendor/flowplayer-6a74b2f70493aba30d491cae7911f870.js	15.2 KiB
jigsy.com/assets/parallax.min-2dd776f7c4d30d5aaf826de11bb3bb24.js	6.9 KiB
/assets/vendor/swfupload/plugins/swfupload.queue-b9a55265...	2.2 KiB
jigsy.com/assets/vendor/cookies-d5572bd0a695970e3e2fad4af6789eaa.js	2.2 KiB
jigsy.com/assets/jquery_ujs-d25cb65d1f6e0aae3d96b24a729e55bb.js	18.5 KiB
jigsy.com/assets/vendor/swfupload/swfupload-85fcc14dec456f2beaf2cfb97b346fbd.js	20.0 KiB
jigsy.com/assets/responsive/jigsy-e86cc199cbd08623de64a94e1b92f9a4.js	2.2 KiB
jigsy.com/assets/responsive/jigsy.util.html-41517f4e9b3de9a68ba9ebdc6b58072d.js	3.2 KiB
/assets/vendor/jquery_plugins/slides.min.jquery-ed87b713a...	6.2 KiB
jigsy.com/assets/mobile_nav-7ff9402e7a343d1eacca0df07e6690ef.js	923 B
jigsy.com/assets/responsive/jigsy.extensions-dd3b6a9aecc8ca06dd6386af6b3293cf.js	877 B
/assets/vendor/jquery_plugins/jquery.jHelperTip-63c22f09e...	2.6 KiB
/assets/vendor/jquery_plugins/jquery.inview.min-26a54fac2...	1.8 KiB
/assets/vendor/jquery_plugins/jquery.endless-scroll-4c22e...	1.9 KiB
jigsy.com/assets/animation-14175b47868a38b2f676154ad0d88464.css	5.2 KiB
jigsy.com/assets/style-ec75cb9dab2eb2124104290a94480240.css	12.2 KiB
jigsy.com/assets/full_width-e8ddd06fbf3609b15206b97769281b43.css	2.6 KiB
jigsy.com/assets/mobile_nav-58d7d86921bae73cbfef840c3b166a33.css	1.1 KiB
jigsy.com/assets/jigsy-afe12ed47481c63ca72f37d724ef26b0.css	4.5 KiB
jigsy.com/assets/form-elements-303b2abf48bd1379708d241bd459f47e.css	1.4 KiB
jigsy.com/assets/font-awesome.min-b2aa2ea30994b60be6919d99b375358f.css	5.7 KiB	225 ms
jigsy.com/assets/fontello-1386f3e768e18cfeef4f09565c071d56.css	1.3 KiB
jigsy.com/assets/fancybox/jquery.fancybox-72995133e20ba753b90d844c7287af4a.css	1.7 KiB
/css?family=Opens+Sans:300,400\|Droid+Sans\|Catamaran:300,4...	1.0 KiB
fonts.googleapis.com/css?family=Open+Sans:100,400,300,600,700	1.9 KiB	266 ms
use.fontawesome.com/releases/v5.0.6/css/all.css	8.4 KiB	211 ms
cdnjs.cloudflare.com/ajax/libs/Chart.js/2.2.1/Chart.min.js	32.4 KiB	374 ms
cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.3/umd/popper.min.js	6.9 KiB	229 ms
stackpath.bootstrapcdn.com/bootstrap/4.3.1/css/bootstrap.min.css	27.1 KiB	375 ms
stackpath.bootstrapcdn.com/bootstrap/4.3.1/js/bootstrap.min.js	16.1 KiB	359 ms

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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.1 KiB

URL	Transfer Size	Est Savings
jigsy.com/assets/style-ec75cb9dab2eb2124104290a94480240.css	12.2 KiB	2.1 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 24.1 KiB

URL	Transfer Size	Est Savings
jigsy.com/assets/jigsy-fdc4946dc54563e13a32082fbf07cab8.js	22.7 KiB	9.8 KiB
jigsy.com/assets/jquery_ujs-d25cb65d1f6e0aae3d96b24a729e55bb.js	18.0 KiB	8.1 KiB
jigsy.com/assets/responsive/jigsy.modal-0f89705f8d1433770ce4e4b34512867f.js	10.5 KiB	6.3 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 36.7 KiB

URL	Transfer Size	Est Savings
stackpath.bootstrapcdn.com/bootstrap/4.3.1/css/bootstrap.min.css	26.5 KiB	25.8 KiB
jigsy.com/assets/style-ec75cb9dab2eb2124104290a94480240.css	11.8 KiB	11.0 KiB

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: 0.0 ms 138.5 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-H702YKNYSR	156.9 KiB	64.0 KiB
jigsy.com/assets/vendor/jquery-3cfe00e2ecb0d8e1640d0b2c9223d1dc.js	96.0 KiB	48.9 KiB
cdnjs.cloudflare.com/ajax/libs/Chart.js/2.2.1/Chart.min.js	31.8 KiB	25.5 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
Picture of a computer, tablet and smart phone `div.container > div.row > div.col-md-6 > img.center_image`	jigsy.com/images/home/2.png
div.container > div.row > div.col-sm-6 > img.center_image `div.container > div.row > div.col-sm-6 > img.center_image`	jigsy.com/images/cloudlock2.jpg
Jigsy `div.top_navigation > div.container > div#header > img`	jigsy.com/images/jigsy/logo.png

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 40 ms

●Avoids enormous network payloads Total size was 2,639 KiB

●User Timing marks and measures 7 user timings

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.4 s

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 180 ms

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

●Avoid large layout shifts 15 layout shifts found

○INP breakdown

○Avoid long main-thread tasks

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
We use cookies Cookies help us deliver the best experience on our website. By … `body#welcome_index > div#cookie-consent-dialog`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body#welcome_index > div#cookie-consent-dialog > div.container > button.close `body#welcome_index > div#cookie-consent-dialog > div.container > button.close`

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
body#welcome_index > div.parallax-mirror > img.parallax-slider `body#welcome_index > div.parallax-mirror > img.parallax-slider`
div.container > div.row > div.col-sm-6 > img.center_image `div.container > div.row > div.col-sm-6 > img.center_image`

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.container > div#copyright > div.social_links > a.social_twitter `div.container > div#copyright > div.social_links > a.social_twitter`
div.container > div#copyright > div.social_links > a.social_facebook `div.container > div#copyright > div.social_links > a.social_facebook`

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.

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
SIGN UP `div.row > div.col-md-4 > div.package_2428 > a.signup`
SIGN UP `div.row > div.col-md-4 > div.package_2429 > a.signup`
SIGN UP `div.row > div.col-md-4 > div.package_2430 > a.signup`

These are opportunities to improve the legibility of your content.

○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-hidden="true"]` is not present on the document `<body>`

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

●`[role]` values are valid

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●Document has a `<title>` element

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

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

○ARIA attributes are used as specified for the element's role

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted 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

○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

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

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

○The page contains a heading, skip link, or landmark region

○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

○Form elements have associated labels

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

○Elements with visible text labels have matching accessible names.

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

100

Best Practices

●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 browser errors logged to the console

●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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

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
body#welcome_index > div.parallax-mirror > img.parallax-slider `body#welcome_index > div.parallax-mirror > img.parallax-slider`
div.container > div.row > div.col-sm-6 > img.center_image `div.container > div.row > div.col-sm-6 > img.center_image`

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

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