8/14/23, 9:15 AM about:blank

[Link]

88 93 100 83

Performance Accessibility Best SEO PWA

Practices

88

Performance
Values are estimated and may vary. The performance
score is calculated directly from these metrics. See
calculator.

0–49 50–89 90–100

METRICS Expand view

First Contentful Paint Largest Contentful Paint

0.9 s 1.0 s
Total Blocking Time Cumulative Layout Shift
20 ms 0.037
Speed Index
4.6 s
View Treemap View Original Trace

about:blank 1/45
8/14/23, 9:15 AM about:blank

Show audits relevant to: All FCP LCP TBT CLS

OPPORTUNITIES
Opportunity Estimated Savings
Reduce initial server response time 5.98s

Keep the server response time for the main document short because all other requests depend on it. Learn more
about the Time to First Byte metric. FCP LCP
Themes, plugins, and server specifications all contribute to server response time. Consider finding a
more optimized theme, carefully selecting an optimization plugin, and/or upgrading your server.

URL Time Spent

WP Engine Hosting 1st Party 6,080 ms

[Link] 6,080 ms

Serve images in next-gen formats 0.72s

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster
downloads and less data consumption. Learn more about modern image formats.
Consider using the Performance Lab plugin to automatically convert your uploaded JPEG images into
WebP, wherever supported.

Resource Potential
URL
Size Savings

WP Engine Hosting 1,242.5 KiB 897.8 KiB

1st Party

…07/A-Beginners-Guide-to-Jazz-
230.7 KiB 150.5 KiB
[Link] ([Link])

[Link] …05/LEARN- 108.7 KiB 102.5 KiB

mentor JAZ….jpg ([Link])

about:blank 2/45
8/14/23, 9:15 AM about:blank

Resource Potential
URL
Size Savings
-
elemen
[Link]
entor-element-85b8f17.e-
con-full.e-flex.e-con

[Link]
mentor
-
…05/LEARN-
elemen 85.3 KiB 81.1 KiB
JAZ….jpg ([Link])
[Link]
entor-element-8ad7683.e-
con-boxed.e-flex.e-con

[Link]
mento
r- …05/LEARN-
95.3 KiB 70.9 KiB
custo JAZ….jpg ([Link])
m-
embed-image-overlay

…09/maxresdefault-
111.8 KiB 53.5 KiB
[Link] ([Link])

[Link]
mento
r- …05/LEARN-
57.1 KiB 46.1 KiB
custo JAZ….jpg ([Link])
m-
embed-image-overlay

[Link]
mentor
-
…05/LEARN-
elemen 65.5 KiB 42.5 KiB
JAZ….jpg ([Link])
[Link]
entor-element-cde3b58.e-
con-boxed.e-flex.e-con

[Link]
mento
r- …05/LEARN-
49.1 KiB 39.9 KiB
custo JAZ….jpg ([Link])
m-
embed-image-overlay

about:blank 3/45
8/14/23, 9:15 AM about:blank

Resource Potential
URL
Size Savings

[Link]- …08/LEARN-
31.5 KiB 24.0 KiB
[Link]-image-192315 JAZ….jpg ([Link])

[Link]- …08/LEARN-
30.5 KiB 23.5 KiB
[Link]-image-192313 JAZ….jpg ([Link])

[Link]- …05/LEARN-
28.8 KiB 23.3 KiB
[Link]-image-191535 JAZ….jpg ([Link])

[Link]- …05/LEARN-
31.1 KiB 23.1 KiB
[Link]-image-191538 JAZ….jpg ([Link])

[Link]- …08/LEARN-
27.8 KiB 21.9 KiB
[Link]-image-192314 JAZ….jpg ([Link])

[Link]- …08/LEARN-
24.9 KiB 18.8 KiB
[Link]-image-192309 JAZ….jpg ([Link])

[Link]- …08/LEARN-
23.5 KiB 18.3 KiB
[Link]-image-192310 JAZ….jpg ([Link])

[Link]
mento
r-
…05/LEARN-
eleme 19.1 KiB 17.4 KiB
JAZ….jpg ([Link])
[Link]
mentor-element-af0e16f.e-
con-full.e-flex.e-con

[Link]
emen
tor-
elem …05/LEARN-
18.1 KiB 16.6 KiB
ent.e JAZ….jpg ([Link])
lementor-element-
222c007.e-con-full.e-flex.e-
con

[Link]- …05/LEARN-
20.6 KiB 15.9 KiB
[Link]-image-191537 JAZ….jpg ([Link])

[Link]- …08/LEARN-
20.1 KiB 15.4 KiB
[Link]-image-192308 JAZ….jpg ([Link])

about:blank 4/45
8/14/23, 9:15 AM about:blank

Resource Potential
URL
Size Savings

[Link]- …08/LEARN-
20.0 KiB 15.4 KiB
[Link]-image-192312 JAZ….jpg ([Link])

[Link]
mentor
-
…05/LEARN-
elemen 33.7 KiB 14.8 KiB
JAZ….jpg ([Link])
[Link]
entor-element-b000c6d.e-
con-boxed.e-flex.e-con

[Link]- …05/LEARN-
19.4 KiB 14.8 KiB
[Link]-image-191539 JAZ….jpg ([Link])

[Link]- …08/LEARN-
19.2 KiB 14.5 KiB
[Link]-image-192311 JAZ….jpg ([Link])

[Link]- …05/LEARN-
17.9 KiB 13.7 KiB
[Link]-image-191536 JAZ….jpg ([Link])

img.
attac
hme …05/LEARN-
27.0 KiB 10.3 KiB
nt- JAZ….jpg ([Link])
[Link]
[Link]-image-191498

[Link]
mentor
-
…07/LEARN-
elemen 25.7 KiB 9.3 KiB
JAZ….jpg ([Link])
[Link]
entor-element-5076b79.e-
con-boxed.e-flex.e-con

Efficiently encode images 0.32s

Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

Consider using an image optimization WordPress plugin that compresses your images while retaining
quality.

about:blank 5/45
8/14/23, 9:15 AM about:blank

Resource Potential
URL
Size Savings

WP Engine Hosting 1st Party 748.1 KiB 436.9 KiB

[Link]
tor-
[Link] …05/LEARN-
108.7 KiB 90.3 KiB
ementor- JAZ….jpg ([Link])
element-
85b8f17.e-con-full.e-flex.e-con

[Link]
tor-
[Link]
…05/LEARN-
ementor- 85.3 KiB 74.0 KiB
JAZ….jpg ([Link])
element-
8ad7683.e-con-boxed.e-flex.e-
con

[Link]
tor-
custom- …05/LEARN-
95.3 KiB 43.8 KiB
embed- JAZ….jpg ([Link])
image-
overlay

[Link]
tor-
custom- …05/LEARN-
57.1 KiB 29.3 KiB
embed- JAZ….jpg ([Link])
image-
overlay

[Link]
tor-
custom- …05/LEARN-
49.1 KiB 25.3 KiB
embed- JAZ….jpg ([Link])
image-
overlay

[Link]- …05/LEARN-
28.8 KiB 15.9 KiB
[Link]-image-191535 JAZ….jpg ([Link])

[Link]- …08/LEARN-
31.5 KiB 14.3 KiB
[Link]-image-192315 JAZ….jpg ([Link])

about:blank 6/45
8/14/23, 9:15 AM about:blank

Resource Potential
URL
Size Savings

[Link]
tor-
[Link] …05/LEARN-
19.1 KiB 14.3 KiB
ementor- JAZ….jpg ([Link])
element-
af0e16f.e-con-full.e-flex.e-con

[Link]- …08/LEARN-
30.5 KiB 14.2 KiB
[Link]-image-192313 JAZ….jpg ([Link])

[Link]- …08/LEARN-
27.8 KiB 14.0 KiB
[Link]-image-192314 JAZ….jpg ([Link])

[Link]- …05/LEARN-
31.1 KiB 14.0 KiB
[Link]-image-191538 JAZ….jpg ([Link])

[Link]
ntor-
element.
…05/LEARN-
elemento 18.1 KiB 13.7 KiB
JAZ….jpg ([Link])
r-
element-222c007.e-con-full.e-
flex.e-con

[Link]- …08/LEARN-
24.9 KiB 11.2 KiB
[Link]-image-192309 JAZ….jpg ([Link])

[Link]- …08/LEARN-
23.5 KiB 10.4 KiB
[Link]-image-192310 JAZ….jpg ([Link])

[Link]- …05/LEARN-
20.6 KiB 10.1 KiB
[Link]-image-191537 JAZ….jpg ([Link])

[Link]- …05/LEARN-
19.4 KiB 9.0 KiB
[Link]-image-191539 JAZ….jpg ([Link])

[Link]- …08/LEARN-
20.0 KiB 8.7 KiB
[Link]-image-192312 JAZ….jpg ([Link])

[Link]- …08/LEARN-
20.1 KiB 8.6 KiB
[Link]-image-192308 JAZ….jpg ([Link])

[Link]- …05/LEARN- 17.9 KiB 8.1 KiB

[Link]-image-191536
about:blank 7/45
8/14/23, 9:15 AM about:blank

Resource Potential
URL
Size Savings
JAZ….jpg ([Link])

[Link]- …08/LEARN-
19.2 KiB 7.8 KiB
[Link]-image-192311 JAZ….jpg ([Link])

These suggestions can help your page load faster. They don't directly affect the Performance score.

DIAGNOSTICS

Ensure text remains visible during webfont load

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more
about font-display. FCP LCP

Potential
URL
Savings

Google Fonts Cdn 70 ms

…v12/UcC73FwrK….woff2 ([Link]) 60 ms

…v30/KFOmCnqEu….woff2 ([Link]) 10 ms

Does not use passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance.
Learn more about adopting passive event listeners.

Source

WP Engine Hosting 1st Party

[Link]

Avoid an excessive DOM size — 1,564 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows.
Learn how to avoid an excessive DOM size. TBT

about:blank 8/45
8/14/23, 9:15 AM about:blank

Statistic Element Value

Total DOM
1,564
Elements

Maximum
[Link]-grid-caption-text 18
DOM Depth

[Link]-template-
elementor_header_footer.[Link]-
Maximum
[Link]-template-full-
Child 71
[Link]-
Elements
page-24377.e--ua-isTouchDevice.e--ua-blink.e--ua-
chrome.e--ua-webkit

Minimize main-thread work — 2.4 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS
payloads helps with this. Learn how to minimize main-thread work TBT

Category Time Spent

Other 788 ms

Style & Layout 719 ms

Script Evaluation 620 ms

Rendering 129 ms

Parse HTML & CSS 105 ms

Script Parsing & Compilation 21 ms

Garbage Collection 11 ms

Avoid chaining critical requests — 71 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing
the length of chains, reducing the download size of resources, or deferring the download of unnecessary
resources to improve page load. Learn how to avoid chaining critical requests. FCP LCP

Maximum critical path latency: 9,505.656 ms

about:blank 9/45
8/14/23, 9:15 AM about:blank

Initial Navigation
[Link]
…block-library/[Link]?ver=6.2.2 ([Link]) - 281.143 ms, 12.79 KiB
…css/[Link]?ver=6.2.2 ([Link]) - 220.793 ms, 0.41 KiB
…css/[Link]?ver=3.3.1 ([Link]) - 273.713 ms, 0.85 KiB
…css/[Link]?ver=3.0.8 ([Link]) - 281.17 ms, 1.05 KiB
…css/[Link]?ver=6.2.2 ([Link]) - 318.458 ms, 34.65 KiB
…css/[Link]?ver=2.5.14 ([Link]) - 293.146 ms, 6.80 KiB
…hello-elementor/[Link]?ver=2.7.1 ([Link]) - 284.087 ms, 2.02 KiB
…hello-elementor/[Link]?ver=2.7.1 ([Link]) - 288.979 ms, 2.68 KiB
…css/[Link]?ver=5.20.0 ([Link]) - 295.973 ms, 4.00 KiB
…css/[Link]?ver=169… ([Link]) - 302.246 ms, 11.49 KiB
…css/[Link]?ver=5.3.6 ([Link]) - 280.535 ms, 2.57 KiB
…css/[Link]?ver=169… ([Link]) - 286.283 ms, 0.79 KiB
…css/[Link]?ver=169… ([Link]) - 291.962 ms, 1.73 KiB
…min-css/[Link]?ver=1.36.16 ([Link]) - 325.176 ms, 17.71 KiB
…css/[Link]?ver=169… ([Link]) - 329.841 ms, 10.00 KiB
…css/[Link]?ver=169… ([Link]) - 293.013 ms, 2.35 KiB
…css/[Link]?ver=169… ([Link]) - 282.104 ms, 1.97 KiB
…css/[Link]?ver=169… ([Link]) - 275.335 ms, 2.59 KiB
…css/[Link]?ver=169… ([Link]) - 278.026 ms, 2.59 KiB
…css/[Link]?ver=169… ([Link]) - 272.424 ms, 0.98 KiB
…css/[Link]?ver=169… ([Link]) - 276.257 ms, 2.91 KiB
…css/[Link]?ver=169… ([Link]) - 284.506 ms, 1.41 KiB
…hello-theme-child-master/[Link]?ver=2.0.0 ([Link]) - 278.005 ms, 0.57 KiB
/css?family=… ([Link])
…v12/UcC73FwrK….woff2 ([Link]) - 62.863 ms, 37.43 KiB
…v30/KFOmCnqEu….woff2 ([Link]) - 8.254 ms, 10.88 KiB
…css/[Link]?ver=5.15.3 ([Link]) - 332.748 ms, 12.56 KiB
…css/[Link]?ver=5.15.3 ([Link])
…webfonts/fa-solid-900.woff2 ([Link]) - 371.37 ms, 76.65 KiB
…css/[Link]?ver=169… ([Link]) - 320.176 ms, 1.23 KiB
…css/[Link]?ver=0 ([Link]) - 321.816 ms, 3.54 KiB
…css/[Link] ([Link]) - 242.452 ms, 2.51 KiB
…css/[Link] ([Link]) - 252.153 ms, 2.08 KiB
…dist/[Link]?ver=2.7.12 ([Link]) - 259.509 ms, 0.88 KiB
…dist/[Link]?ver=2.7.12 ([Link]) - 246.34 ms, 6.96 KiB
…dist/[Link]?ver=2.7.12 ([Link]) - 376.036 ms, 20.90 K
…dist/[Link]?ver=2.7.12 ([Link]) - 239.933 ms, 0.18 KiB
about:blank 10/45
8/14/23, 9:15 AM about:blank

…dist/[Link]?ver=2.7.12 ([Link]) - 249.751 ms, 7.55 KiB

…dist/[Link]?ver=2.7.12 ([Link]) - 245.537 ms, 0.18 KiB
…dist/[Link]?ver=2.7.12 ([Link]) - 250.747 ms, 0.60 KiB
…dist/[Link]?ver=2.7.12 ([Link]) - 255.055 ms, 5.54 KiB
…jquery/[Link]?ver=3.6.4 ([Link]) - 345.723 ms, 31.54 KiB
…jquery/[Link]?ver=3.4.0 ([Link]) - 306.382 ms, 5.06 KiB
…js/[Link]?ver=3.3.1 ([Link]) - 306.462 ms, 0.19 KiB
…js/[Link]?ver=1.0.0 ([Link]) - 318.471 ms, 1.01 KiB
…js/[Link]?ver=2.5.14 ([Link]) - 353.359 ms, 19.10 KiB
…js/[Link]?ver=2.5.14 ([Link]) - 320.222 ms, 7.15 KiB
…ui/[Link]?ver=1.13.2 ([Link]) - 262.586 ms, 7.34 KiB
…ui/[Link]?ver=1.13.2 ([Link]) - 377.466 ms, 11.26 KiB
…smartmenus/[Link]?ver=1.0.1 ([Link]) - 381.601 ms, 7.59 KiB
…jquery-numerator/[Link]?ver=0.2.1 ([Link]) - 386.886 ms, 0.95 KiB
…isotope/[Link]?ver=1.36.16 ([Link]) - 347.552 ms, 10.68 KiB
…js/[Link]?ver=4.1.4 ([Link]) - 375.808 ms, 2.06 KiB
…slick/[Link]?ver=1.36.16 ([Link]) - 390.305 ms, 11.32 KiB
…jquery-element-resize/jquery_resize.[Link]?ver=1.36.16 ([Link]) - 256.716 ms, 1.53 KiB
…min-js/[Link]?ver=1.36.16 ([Link]) - 354.084 ms, 9.22 KiB
…fancybox/jquery_fancybox.[Link]?ver=1.36.16 ([Link]) - 394.872 ms, 20.15 KiB
…justifiedgallery/[Link]?ver=1.36.16 ([Link]) - 394.771 ms, 5.31 KiB
…vendor/[Link]?ver=3.1.2 ([Link]) - 241.944 ms, 2.69 KiB
…vendor/[Link]?ver=0.13.11 ([Link]) - 350.7 ms, 2.72 KiB
…vendor/[Link]?ver=3.15.0 ([Link]) - 352.673 ms, 6.74 KiB
…dist/[Link]?ver=392bdd4… ([Link]) - 352.651 ms, 0.54 KiB
…dist/[Link]?ver=4169d3c… ([Link]) - 349.182 ms, 1.88 KiB
…dist/[Link]?ver=9e794f3… ([Link]) - 247.062 ms, 4.08 KiB
…dist/[Link]?ver=ecce20f… ([Link]) - 346.665 ms, 1.13 KiB
…js/[Link]?ver=3.13.2 ([Link]) - 393.52 ms, 2.62 KiB
…js/[Link]?ver=3.13.4 ([Link]) - 393.403 ms, 2.40 KiB
…js/[Link]?ver=3.13.4 ([Link]) - 400.565 ms, 14.41 KiB
…js/[Link]?ver=3.13.2 ([Link]) - 401.34 ms, 6.89 KiB
…waypoints/[Link]?ver=4.0.2 ([Link]) - 401.491 ms, 3.34 KiB
…js/[Link]?ver=3.13.4 ([Link]) - 571.279 ms, 12.65 KiB
…js/[Link]?ver=3.13.2 ([Link]) - 571.2 ms, 7.23 KiB
…sticky/[Link]?ver=3.13.2 ([Link]) - 570.355 ms, 1.74 KiB

Keep request counts low and transfer sizes small — 128 requests • 2,614 KiB

about:blank 11/45
8/14/23, 9:15 AM about:blank

To set budgets for the quantity and size of page resources, add a [Link] file. Learn more about
performance budgets.

Resource Type Requests Transfer Size

Total 128.0 2,613.9 KiB

Image 37.0 1,294.2 KiB

Media 3.0 691.9 KiB

Script 46.0 277.3 KiB

Stylesheet 38.0 192.6 KiB

Font 3.0 125.0 KiB

Document 1.0 33.0 KiB

Other 0.0 0.0 KiB

Third-party 128.0 2,613.9 KiB

Largest Contentful Paint element — 1 element found

This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint
element LCP

Element
h1

Phase % of LCP Timing

TTFB 585% 6,090 ms
Load Delay 0% 0 ms

about:blank 12/45
8/14/23, 9:15 AM about:blank

Phase % of LCP Timing

Load Time 0% 0 ms
Render Delay -485% -5,040 ms

Avoid large layout shifts — 5 elements found

These DOM elements contribute most to the CLS of the page. Learn how to improve CLS CLS

CLS
Element
Contribution

[Link]-
first-text
0.012

[Link]-element-
[Link]-widget__width-
[Link]-widget-button 0.009

[Link]-element-5ac9018.e-con-
full.e-flex.e-con
0.006

[Link]-
[Link]-widget-text-editor
0.005

[Link]-button-text

0.003

Avoid long main-thread tasks — 3 long tasks found

about:blank 13/45
8/14/23, 9:15 AM about:blank

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to
avoid long main-thread tasks TBT

Start
URL Duration
Time

WP Engine Hosting 1st Party 296 ms

[Link] 548 ms 126 ms

…js/[Link]?ver=4.1.4 ([Link]) 1,269 ms 97 ms

[Link] 674 ms 73 ms

Avoid non-composited animations — 60 animated elements found

Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited
animations CLS

Element Name

[Link]-widget-container

Unsupported CSS Property: box-shadow box-shadow

[Link]-element-6782505.e-
con-full.e-flex.e-con

Unsupported CSS Property: border-bottom-width border-bottom-width

Unsupported CSS Property: border-bottom-color border-bottom-color
[Link]-item

Unsupported CSS Property: padding-right padding-right

about:blank 14/45
8/14/23, 9:15 AM about:blank

Element Name

[Link]-element-c656995.e-
con-full.e-flex.e-con

Unsupported CSS Property: border-bottom-width border-bottom-width

Unsupported CSS Property: border-bottom-color border-bottom-color
[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-image-191537
Unsupported CSS Property: visibility visibility
[Link]-image-192315

Unsupported CSS Property: visibility visibility

[Link]-image-192308
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-image-191535

Unsupported CSS Property: visibility visibility

[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-image-192312
Unsupported CSS Property: visibility visibility

[Link]-image-192314
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption

about:blank 15/45
8/14/23, 9:15 AM about:blank

Element Name

Unsupported CSS Property: visibility visibility

[Link]-image-192310
Unsupported CSS Property: visibility visibility
[Link]-image-192309

Unsupported CSS Property: visibility visibility

[Link]-grid-img-caption

Unsupported CSS Property: visibility visibility

[Link]-grid-img-caption

Unsupported CSS Property: visibility visibility

[Link]-image-192311
Unsupported CSS Property: visibility visibility
[Link]-image-191538

Unsupported CSS Property: visibility visibility

[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption

Unsupported CSS Property: visibility visibility

[Link]-grid-img-caption
about:blank 16/45
8/14/23, 9:15 AM about:blank

Element Name

Unsupported CSS Property: visibility visibility

[Link]-image-192313

Unsupported CSS Property: visibility visibility

[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-image-191536

Unsupported CSS Property: visibility visibility

[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption

Unsupported CSS Property: visibility visibility

[Link]-image-191539
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-image-191536
Unsupported CSS Property: visibility visibility
[Link]-image-192309

Unsupported CSS Property: visibility visibility

[Link]-grid-img-caption
about:blank 17/45
8/14/23, 9:15 AM about:blank

Element Name

Unsupported CSS Property: visibility visibility

[Link]-image-191537
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption

Unsupported CSS Property: visibility visibility

[Link]-image-192310
Unsupported CSS Property: visibility visibility
[Link]-image-192312
Unsupported CSS Property: visibility visibility
[Link]-image-192314
Unsupported CSS Property: visibility visibility

[Link]-image-192310
Unsupported CSS Property: visibility visibility
[Link]-image-191538
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility

[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
about:blank 18/45
8/14/23, 9:15 AM about:blank

Element Name

[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption

Unsupported CSS Property: visibility visibility

[Link]-image-192308
Unsupported CSS Property: visibility visibility

[Link]-image-192315
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-image-191539
Unsupported CSS Property: visibility visibility

[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-grid-img-caption
Unsupported CSS Property: visibility visibility
[Link]-image-192313
Unsupported CSS Property: visibility visibility
[Link]-image-192309

Unsupported CSS Property: visibility visibility

[Link]-image-192311
Unsupported CSS Property: visibility visibility

about:blank 19/45
8/14/23, 9:15 AM about:blank

Element Name

[Link]-image-191535
Unsupported CSS Property: visibility visibility

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

PASSED AUDITS (27) Hide

Eliminate render-blocking resources — Potential savings of 110 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all
non-critical JS/styles. Learn how to eliminate render-blocking resources. FCP LCP
There are a number of WordPress plugins that can help you inline critical assets or defer less important
resources. Beware that optimizations provided by these plugins may break features of your theme or
plugins, so you will likely need to make code changes.
Show 3rd-party resources (1)

Transfer Potential
URL
Size Savings

WP Engine Hosting 1st Party 34.7 KiB 80 ms

…css/[Link]?ver=6.2.2 ([Link]) 34.7 KiB 80 ms

Google Fonts Cdn 2.4 KiB 240 ms

/css?family=… ([Link]) 2.4 KiB 240 ms

Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Upload images directly through the media library to ensure that the required image sizes are available,
and then insert them from the media library or use the image widget to ensure the optimal image sizes
are used (including those for the responsive breakpoints). Avoid using Full Size images unless the
dimensions are adequate for their usage. Learn More.

Defer offscreen images

about:blank 20/45
8/14/23, 9:15 AM about:blank

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower
time to interactive. Learn how to defer offscreen images.
Install a lazy-load WordPress plugin that provides the ability to defer any offscreen images, or switch to a
theme that provides that functionality. Also consider using the AMP plugin.

Minify CSS

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS. FCP LCP
A number of WordPress plugins can speed up your site by concatenating, minifying, and compressing
your styles. You may also want to use a build process to do this minification up-front if possible.

Minify JavaScript

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

A number of WordPress plugins can speed up your site by concatenating, minifying, and compressing
your scripts. You may also want to use a build process to do this minification up front if possible.

Reduce unused CSS — Potential savings of 108 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. FCP LCP
Consider reducing, or switching, the number of WordPress plugins loading unused CSS in your page. To
identify plugins that are adding extraneous CSS, try running code coverage in Chrome DevTools. You can
identify the theme/plugin responsible from the URL of the stylesheet. Look out for plugins that have
many stylesheets in the list which have a lot of red in code coverage. A plugin should only enqueue a
stylesheet if it is actually used on the page.

Transfer Potential
URL
Size Savings

WP Engine Hosting 1st Party 110.1 KiB 108.3 KiB

…css/[Link]?ver=6.2.2 ([Link]) 34.7 KiB 34.7 KiB

…dist/[Link]?
20.9 KiB 20.9 KiB
ver=2.7.12 ([Link])

…min-css/[Link]?ver=1.36.16 ([Link]) 17.7 KiB 17.2 KiB

…block-library/[Link]?ver=6.2.2 ([Link]) 12.8 KiB 12.7 KiB

about:blank 21/45
8/14/23, 9:15 AM about:blank

Transfer Potential
URL
Size Savings

…css/[Link]?ver=5.15.3 ([Link]) 12.6 KiB 12.5 KiB

…css/[Link]?ver=169… ([Link]) 11.5 KiB 10.3 KiB

Reduce unused JavaScript

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by
network activity. Learn how to reduce unused JavaScript. LCP
Consider reducing, or switching, the number of WordPress plugins loading unused JavaScript in your
page. To identify plugins that are adding extraneous JS, try running code coverage in Chrome DevTools.
You can identify the theme/plugin responsible from the URL of the script. Look out for plugins that have
many scripts in the list which have a lot of red in code coverage. A plugin should only enqueue a script if
it is actually used on the page.

Enable text compression

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network
bytes. Learn more about text compression. FCP LCP

You can enable text compression in your web server configuration.

Preconnect to required origins

Warnings: A `<link rel=preconnect>` was found for "[Link] but was not used by the
browser. Check that you are using the `crossorigin` attribute properly.

Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-
party origins. Learn how to preconnect to required origins. FCP LCP

Avoid multiple page redirects

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects. FCP
LCP

Preload key requests

Consider using <link rel=preload> to prioritize fetching resources that are currently requested later in page
load. Learn how to preload key requests. FCP LCP

about:blank 22/45
8/14/23, 9:15 AM about:blank

Use HTTP/2

HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more about
HTTP/2.

Use video formats for animated content

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations
and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formats
LCP

Consider uploading your GIF to a service which will make it available to embed as an HTML5 video.

Remove duplicate modules in JavaScript bundles

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

Avoid serving legacy JavaScript to modern browsers — Potential savings of 8 KiB

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary
for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using
module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining
support for legacy browsers. Learn how to use modern JavaScript TBT

Potential
URL
Savings

WP Engine Hosting 1st Party 7.5 KiB

…js/[Link]?
7.5 KiB
ver=2.5.14 ([Link])
[Link] [Link]

…vendor/[Link]?
0.1 KiB
ver=3.1.2 ([Link])
@babel/plugin-transform-
[Link]
classes

Preload Largest Contentful Paint image

If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP.
Learn more about preloading LCP elements. LCP

about:blank 23/45
8/14/23, 9:15 AM about:blank

Avoids enormous network payloads — Total size was 2,614 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to
reduce payload sizes. LCP
Consider showing excerpts in your post lists (e.g. via the more tag), reducing the number of posts shown
on a given page, breaking your long posts into multiple pages, or using a plugin to lazy-load comments.

Transfer
URL
Size

WP Engine Hosting 1st Party 1,467.8 KiB

…08/Glen-Testimonial.mp4 ([Link]) 285.3 KiB

…07/[Link] ([Link]) 231.2 KiB

…08/Sue-Bradley.mp4 ([Link]) 215.8 KiB

…08/David-Leaper.mp4 ([Link]) 190.7 KiB

…09/[Link] ([Link]) 112.1 KiB

…05/LEARN-JAZ….jpg ([Link]) 109.1 KiB

…05/LEARN-JAZ….jpg ([Link]) 95.6 KiB

…05/LEARN-JAZ….jpg ([Link]) 85.6 KiB

…webfonts/fa-solid-900.woff2 ([Link]) 76.7 KiB

…05/LEARN-JAZ….jpg ([Link]) 65.7 KiB

Uses efficient cache policy on static assets — 0 resources found

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

Read about Browser Caching in WordPress.

User Timing marks and measures

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during
key user experiences. Learn more about User Timing marks.

about:blank 24/45
8/14/23, 9:15 AM about:blank

JavaScript execution time — 0.5 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS
payloads helps with this. Learn how to reduce Javascript execution time. TBT

Total CPU Script Script

URL
Time Evaluation Parse

WP Engine Hosting 1st Party 1,882 ms 515 ms 6 ms

[Link] 1,036 ms 106 ms 4 ms

…jquery/[Link]?ver=3.6.4 ([Link]) 495 ms 263 ms 1 ms

…js/[Link]?ver=4.1.4 ([Link]) 206 ms 97 ms 0 ms

…jquery-element-resize/jquery_resize.[Link]?
145 ms 50 ms 0 ms
ver=1.36.16 ([Link])

Unattributable 336 ms 16 ms 0 ms

Unattributable 336 ms 16 ms 0 ms

Minimize third-party usage — Third-party code blocked the main thread for 0 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party
providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize
third-party impact. TBT

Third-Party Transfer Size Main-Thread Blocking Time

Google Fonts Cdn 51 KiB 0 ms

…v12/UcC73FwrK….woff2 ([Link]) 37 KiB 0 ms

…v30/KFOmCnqEu….woff2 ([Link]) 11 KiB 0 ms

Lazy load third-party resources with facades

Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required.
Learn how to defer third-parties with a facade. TBT

Largest Contentful Paint image was not lazily loaded

about:blank 25/45
8/14/23, 9:15 AM about:blank

Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest
contentful paint. Learn more about optimal lazy loading. LCP

Avoids [Link]()

For users on slow connections, external scripts dynamically injected via [Link]() can delay page load
by tens of seconds. Learn how to avoid [Link]().

Image elements have explicit width and height

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

Has a <meta name="viewport"> tag with width or initial-scale

A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300
millisecond delay to user input. Learn more about using the viewport meta tag. TBT

Page didn't prevent back/forward cache restoration

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache
(bfcache) can speed up these return navigations. Learn more about the bfcache

93

Accessibility
These checks highlight opportunities to improve the accessibility of
your web app. Only a subset of accessibility issues can be
automatically detected so manual testing is also encouraged.

CONTRAST

Background and foreground colors do not have a sufficient contrast ratio.

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

Failing Elements

[Link]-button-text
about:blank 26/45
8/14/23, 9:15 AM about:blank

Failing Elements

[Link]-size-sm

[Link]-button-text

[Link]-size-sm

[Link]-image-box-title

[Link]-element-6782505.e-con-full.e-flex.e-con

[Link]-image-box-title

[Link]-element-0e11617.e-con-full.e-flex.e-con

[Link]-button-text

about:blank 27/45
8/14/23, 9:15 AM about:blank

Failing Elements
[Link]-size-sm

[Link]-testimonial-name

[Link]-widget-container

[Link]-testimonial-name

[Link]-widget-container

[Link]-testimonial-name

[Link]-widget-container

[Link]-button-text

[Link]-size-sm

about:blank 28/45
8/14/23, 9:15 AM about:blank

Failing Elements

[Link]-button-text

[Link]-size-sm

[Link]-post__read-more

[Link]-
[Link]-blog

[Link]-post__read-more

[Link]-
[Link]-ear-
training.post_format-post-format-video

[Link]-post__read-more

[Link]-
[Link]-jazz-theory

about:blank 29/45
8/14/23, 9:15 AM about:blank

Failing Elements

[Link]-button-text

[Link]-size-sm

[Link]-button-text

[Link]-size-sm

These are opportunities to improve the legibility of your content.

NAMES AND LABELS

Links do not have a discernible name

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.

Failing Elements

about:blank 30/45
8/14/23, 9:15 AM about:blank

Failing Elements

[Link]-
repeater-item-7523e50

[Link]-
repeater-item-b870818

[Link]-
repeater-item-158bc2e

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.

NAVIGATION

Heading elements are not in a sequentially-descending order

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to
navigate and understand when using assistive technologies. Learn more about heading order.

Failing Elements

[Link]-grid-caption-text

These are opportunities to improve keyboard navigation in your application.

AUDIO AND VIDEO

<video> elements contain a <track> element with [kind="captions"]

about:blank 31/45
8/14/23, 9:15 AM about:blank

When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn
more about video captions.

Failing Elements

[Link]-video

These are opportunities to provide alternative content for audio and video. This may improve the experience for users
with hearing or vision impairments.
ADDITIONAL ITEMS TO MANUALLY CHECK (10) Hide

The page has a logical tab order

Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more
about logical tab ordering.

Interactive controls are keyboard focusable

Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom
controls focusable.

Interactive elements indicate their purpose and state

Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-
interactive elements. Learn how to decorate interactive elements with affordance hints.

The user's focus is directed to new content added to the page

If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus
to new content.

User focus is not accidentally trapped in a region

A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid
focus traps.

Custom controls have associated labels

about:blank 32/45
8/14/23, 9:15 AM about:blank

Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about
custom controls and labels.

Custom controls have ARIA roles

Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.

Visual order on the page follows DOM order

DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and
visual ordering.

Offscreen content is hidden from assistive technology

Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen
content.

HTML5 landmark elements are used to improve navigation

Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive
technology. Learn more about landmark elements.

These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an
accessibility review.

PASSED AUDITS (17) Hide

[aria-*] attributes match their roles

Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-*
attributes. Learn how to match ARIA attributes to their roles.

[aria-hidden="true"] is not present on the document <body>

Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the
document <body>. Learn how aria-hidden affects the document body.

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

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more
about roles and required attributes.

about:blank 33/45
8/14/23, 9:15 AM about:blank

[role] values are valid

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about
valid ARIA roles.

[aria-*] attributes have valid values

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about
valid values for ARIA attributes.

[aria-*] attributes are valid and not misspelled

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about
valid ARIA attributes.

ARIA IDs are unique

The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive
technologies. Learn how to fix duplicate ARIA IDs.

Image elements have [alt] attributes

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.

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

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.

,
button link , and menuitem elements have accessible names

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it
unusable for users who rely on screen readers. Learn how to make command elements more accessible.

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

Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being
available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable
elements.

Document has a <title> element

about:blank 34/45
8/14/23, 9:15 AM about:blank

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.

<html> element has a [lang] attribute

If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that
the user chose when setting up the screen reader. If the page isn't actually in the default language, then the
screen reader might not announce the page's text correctly. Learn more about the lang attribute.

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

Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang
attribute.

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

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

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

Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced
properly. Learn more about proper list structure.

No element has a [tabindex] value greater than 0

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates
frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.

NOT APPLICABLE (23) Hide

[accesskey] values are unique

Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique.
Learn more about access keys.

ARIA input fields have accessible names

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it
unusable for users who rely on screen readers. Learn more about input field labels.

ARIA meter elements have accessible names

about:blank 35/45
8/14/23, 9:15 AM about:blank

When a meter element doesn't have an accessible name, screen readers announce it with a generic name,
making it unusable for users who rely on screen readers. Learn how to name meter elements.

ARIA progressbar elements have accessible names

When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name,
making it unusable for users who rely on screen readers. Learn how to label progressbar elements.

Elements with an ARIA [role] that require children to contain a specific [role] have all required children.

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn
more about roles and required children elements.

[role] s are contained by their required parent element

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility
functions. Learn more about ARIA roles and required parent element.

ARIA toggle fields have accessible names

When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it
unusable for users who rely on screen readers. Learn more about toggle fields.

ARIA tooltip elements have accessible names

When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name,
making it unusable for users who rely on screen readers. Learn how to name tooltip elements.

ARIA treeitem elements have accessible names

When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name,
making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.

Buttons have an accessible name

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.

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

Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more
about bypass blocks.

about:blank 36/45
8/14/23, 9:15 AM about:blank

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

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output.
Learn how to structure definition lists correctly.

Definition list items are wrapped in <dl> elements

Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can
properly announce them. Learn how to structure definition lists correctly.

[id] attributes on active, focusable elements are unique

All focusable elements must have a unique id to ensure that they're visible to assistive technologies. Learn how
to fix duplicate ids.

No form fields have multiple labels

Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers
which use either the first, the last, or all of the labels. Learn how to use form labels.

<frame> or <iframe> elements have a title

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

<input type="image"> elements have [alt] text

When an image is being used as an <input> button, providing alternative text can help screen reader users
understand the purpose of the button. Learn about input image alt text.

Form elements have associated labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn
more about form element labels.

The document does not use <meta http-equiv="refresh">

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page.
This may create a frustrating or confusing experience. Learn more about the refresh meta tag.

<object> elements have alternate text

Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen
readers convey meaning to users. Learn more about alt text for object elements.

about:blank 37/45
8/14/23, 9:15 AM about:blank

Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.

Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute
only refer to other cells in the same table may improve the experience for screen reader users. Learn more about
the headers attribute.

<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.

Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set
of cells may improve the experience for screen reader users. Learn more about table headers.

[lang] attributes have a valid value

Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen
reader. Learn how to use the lang attribute.

100

Best Practices
TRUST AND SAFETY

Ensure CSP is effective against XSS attacks

A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn
how to use a CSP to prevent XSS

Description Directive Severity

No CSP found in enforcement mode High

GENERAL

Detected JavaScript libraries

All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection
diagnostic audit.

about:blank 38/45
8/14/23, 9:15 AM about:blank

Name Version

jQuery 3.6.4

jQuery UI 1.13.2

Isotope

WordPress

core-js core-js-global@3.19.1; core-js-global@3.30.1; core-js-global@3.30.1

PASSED AUDITS (13) Hide

Uses HTTPS

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding
mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS.
HTTPS prevents intruders from tampering with or passively listening in on the communications between your
app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about
HTTPS.

Avoids requesting the geolocation permission on page load

Users are mistrustful of or confused by sites that request their location without context. Consider tying the
request to a user action instead. Learn more about the geolocation permission.

Avoids requesting the notification permission on page load

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying
the request to user gestures instead. Learn more about responsibly getting permission for notifications.

Allows users to paste into input fields

Preventing input pasting is a bad practice for the UX, and weakens security by blocking password
[Link] more about user-friendly input fields.

Displays images with correct aspect ratio

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Serves images with appropriate resolution

about:blank 39/45
8/14/23, 9:15 AM about:blank

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image
clarity. Learn how to provide responsive images.

Page has the HTML doctype

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype
declaration.

Properly defines charset

A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the
HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.

Avoids unload event listeners

The unload event does not fire reliably and listening for it can prevent browser optimizations like the Back-
Forward Cache. Use pagehide or visibilitychange events instead. Learn more about unload event listeners

Avoids deprecated APIs

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

No browser errors logged to the console

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

No issues in the Issues panel in Chrome Devtools

Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from
network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in
Chrome DevTools for more details on each issue.

Page has valid source maps

Source maps translate minified code to the original source code. This helps developers debug in production. In
addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of
these benefits. Learn more about source maps.

NOT APPLICABLE (1) Hide

Fonts with font-display: optional are preloaded

about:blank 40/45
8/14/23, 9:15 AM about:blank

Preload optional fonts so first-time visitors may use them. Learn more about preloading fonts

83

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

Document does not have a meta description

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the
meta description.

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

CRAWLING AND INDEXING

Page is blocked from indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them.
Learn more about crawler directives.

Blocking Directive Source

meta

/[Link]

To appear in search results, crawlers need access to your app.

ADDITIONAL ITEMS TO MANUALLY CHECK (1) Hide

Structured data is valid

about:blank 41/45
8/14/23, 9:15 AM about:blank

Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more
about Structured Data.

Run these additional validators on your site to check additional SEO best practices.

PASSED AUDITS (10) Hide

Has a <meta name="viewport"> tag with width or initial-scale

A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300
millisecond delay to user input. Learn more about using the viewport meta tag. TBT

Document has a <title> element

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.

Page has successful HTTP status code

Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.

Links have descriptive text

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Links are crawlable

Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor
elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make
links crawlable

[Link] is valid

If your [Link] file is malformed, crawlers may not be able to understand how you want your website to be
crawled or indexed. Learn more about [Link].

Image elements have [alt] attributes

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.

Document has a valid hreflang

about:blank 42/45
8/14/23, 9:15 AM about:blank

hreflang links tell search engines what version of a page they should list in search results for a given language
or region. Learn more about hreflang.

Document has a valid rel=canonical

Canonical links suggest which URL to show in search results. Learn more about canonical links.

Document avoids plugins

Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more
about avoiding plugins.

NOT APPLICABLE (2) Hide

Document uses legible font sizes

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to
read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.

Tap targets are sized appropriately

Interactive elements like buttons and links should be large enough (48x48px), or have enough space around
them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.

PWA
These checks validate the aspects of a Progressive Web App. Learn
what makes a good Progressive Web App.

INSTALLABLE

Web app manifest or service worker do not meet the installability requirements — 1 reason

Service worker is the technology that enables your app to use many Progressive Web App features, such as
offline, add to homescreen, and push notifications. With proper service worker and manifest implementations,
browsers can proactively prompt users to add your app to their homescreen, which can lead to higher
engagement. Learn more about manifest installability requirements.

about:blank 43/45
8/14/23, 9:15 AM about:blank

Failure reason

Page has no manifest <link> URL

PWA OPTIMIZED

Does not register a service worker that controls page and start_url

The service worker is the technology that enables your app to use many Progressive Web App features, such as
offline, add to homescreen, and push notifications. Learn more about Service Workers.

Is not configured for a custom splash screen Failures: No manifest was fetched.

A themed splash screen ensures a high-quality experience when users launch your app from their homescreens.
Learn more about splash screens.

Does not set a theme color for the address bar.

Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.

The browser address bar can be themed to match your site. Learn more about theming the address bar.

Content is sized correctly for the viewport

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for
mobile screens. Learn how to size content for the viewport.

Has a <meta name="viewport"> tag with width or initial-scale

A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300
millisecond delay to user input. Learn more about using the viewport meta tag. TBT

Manifest doesn't have a maskable icon No manifest was fetched

A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app
on a device. Learn about maskable manifest icons.

ADDITIONAL ITEMS TO MANUALLY CHECK (3) Hide

Site works cross-browser

To reach the most number of users, sites should work across every major browser. Learn about cross-browser

about:blank 44/45
8/14/23, 9:15 AM about:blank

compatibility.

Page transitions don't feel like they block on the network

Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's
perception of performance. Learn more about page transitions.

Each page has a URL

Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on
social media. Learn more about providing deep links.

These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not
affect your score but it's important that you verify them manually.

Captured at Aug 14, 2023, Emulated Desktop with Single page load
9:13 AM GMT+8 Lighthouse 10.2.0
Initial page load Custom throttling Using Chromium [Link]
with devtools

Generated by Lighthouse 10.2.0 | File an issue

about:blank 45/45