10up Homepage Lighthouse

Download as pdf or txt
Download as pdf or txt
You are on page 1of 42

23/12/2023, 08:56 about:blank

https://10up.com/careers/

86 96 82 83

Performance Accessibility Best SEO PWA


Practices

There were issues affecting this run of Lighthouse:

Chrome extensions negatively affected this page's load performance. Try auditing the page in
incognito mode or from a Chrome profile without extensions.

There may be stored data affecting loading performance in this location: IndexedDB. Audit this
page in an incognito window to prevent those resources from affecting your scores.

The page loaded too slowly to finish within the time limit. Results may be incomplete.

86

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.4 s 0.9 s

Total Blocking Time Cumulative Layout Shift

150 ms 0

Speed Index

6.3 s

View Treemap

about:blank 1/42
23/12/2023, 08:56 about:blank

Show audits relevant to: All FCP LCP TBT CLS

DIAGNOSTICS

Reduce initial server response time — Root document took 1,860 ms

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

10up.com 1st Party 1,860 ms

/careers/ (10up.com) 1,860 ms

Serve images in next-gen formats — Potential savings of 122 KiB

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.

Show 3rd-party resources (1)

Resource Potential
URL
Size Savings

10up.com 1st Party 171.1 KiB 70.8 KiB

div.video-
marketing_
…img/careers-hero-large-
_backgroun 85.6 KiB 35.5 KiB
fallback.jpg (10up.com)
d-video

…img/careers-hero-large-
85.5 KiB 35.4 KiB
fallback.jpg (10up.com)

Cloudinary Content 210.7 KiB 50.8 KiB

about:blank 2/42
23/12/2023, 08:56 about:blank

Resource Potential
URL
Size Savings

img.
alt-
story …11/pod-group-
210.7 KiB 50.8 KiB
- photo@2x.jpg (res.cloudinary.com)
imag
e

Reduce unused CSS — Potential savings of 98 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.

Show 3rd-party resources (1)

Transfer Potential
URL
Size Savings

Unattributable 45.4 KiB 43.1 KiB

:root { font-size: 100%; } … 24.1 KiB 24.1 KiB

#inner-shadow-companion { font-size: 100%; } … 21.3 KiB 19.0 KiB

10up.com 1st Party 38.3 KiB 33.8 KiB

…css/frontend-style.css?ver=bed770e… (10up.com) 23.5 KiB 19.1 KiB

…block-library/style.min.css?ver=6.4.2 (10up.com) 14.8 KiB 14.7 KiB

Torrent Scanner Chrome Extension 21.3 KiB 21.3 KiB

chrome-extension://aegnopegbbhjeeiganiajffnalhlkkjb/css/custom.css 21.3 KiB 21.3 KiB

Reduce unused JavaScript — Potential savings of 455 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. LCP

about:blank 3/42
23/12/2023, 08:56 about:blank

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.

Show 3rd-party resources (5)

Transfer Potential
URL
Size Savings

RocketReach Chrome Extension Chrome Extension 607.2 KiB 367.5 KiB

chrome-extension://oiecklaabeielolbliiddlbokpfnmhba/chunks/Company-
289.0 KiB 200.2 KiB
12559e48.js

chrome-extension://oiecklaabeielolbliiddlbokpfnmhba/chunks/logging-
262.7 KiB 116.8 KiB
df72f020.js

chrome-extension://oiecklaabeielolbliiddlbokpfnmhba/ui/content-
55.6 KiB 50.6 KiB
script/index.js

Google Tag Manager Tag-Manager 162.1 KiB 63.9 KiB

/gtm.js?id=GTM-5KQZN66 (www.googletagmanager.com) 77.9 KiB 32.9 KiB

/gtag/js?id=G-C7B7GMVE23&l=dataLayer&cx=c (www.googletagmanager.com) 84.2 KiB 31.0 KiB

10up.com 1st Party 31.0 KiB 23.5 KiB

…jquery/jquery.min.js?ver=3.7.1 (10up.com) 31.0 KiB 23.5 KiB

Minify CSS — Potential savings of 2 KiB

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.

Transfer Potential
URL
Size Savings

:root { font-size: 100%; } … 24.1 KiB 2.4 KiB

Minify JavaScript — Potential savings of 299 KiB

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

about:blank 4/42
23/12/2023, 08:56 about:blank

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.

Show 3rd-party resources (2)

Transfer Potential
URL
Size Savings

Unattributable 306.2 KiB 220.4 KiB

chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext-
101.7 KiB 83.8 KiB
sdk/content.js

chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext-
101.7 KiB 83.8 KiB
sdk/content.js

chrome-
19.8 KiB 10.5 KiB
extension://majdfhpaihoncoakbjgbdhglocklcgno/ublock/js/contentscript.js

chrome-
19.8 KiB 10.5 KiB
extension://majdfhpaihoncoakbjgbdhglocklcgno/ublock/js/contentscript.js

chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/polyfill.js 14.0 KiB 8.9 KiB

chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/polyfill.js 14.0 KiB 8.9 KiB

chrome-extension://chklaanhfefbnpoihckbnefhakgolnmc/js/content.js 15.5 KiB 5.4 KiB

chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/adblock-functions.js 6.8 KiB 3.1 KiB

chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/adblock-functions.js 6.8 KiB 3.1 KiB

chrome-extension://hgmhmanijnjhaffoampdlllchpolkdnj/js/shared.js 6.1 KiB 2.3 KiB

RocketReach Chrome Extension Chrome Extension 289.0 KiB 72.2 KiB

chrome-extension://oiecklaabeielolbliiddlbokpfnmhba/chunks/Company-
289.0 KiB 72.2 KiB
12559e48.js

Torrent Scanner Chrome Extension 23.1 KiB 6.6 KiB

chrome-extension://aegnopegbbhjeeiganiajffnalhlkkjb/js/popup.js 23.1 KiB 6.6 KiB

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 5/42
23/12/2023, 08:56 about:blank

URL Potential Savings

10up.com 1st Party 0 ms

div.video-
marketing__bac
kground-video …img/careers-hero-large-fallback.jpg (10up.com) 0 ms

Serve static assets with an efficient cache policy — 26 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.

Show 3rd-party resources (4)

Cache Transfer
URL
TTL Size

10up.com 1st Party 314 KiB

…img/careers-hero-large-fallback.jpg (10up.com) 30d 86 KiB

…img/careers-hero-large-fallback.jpg (10up.com) 30d 86 KiB

…vendor/wp-polyfill.min.js?ver=3.15.0 (10up.com) 30d 36 KiB

…jquery/jquery.min.js?ver=3.7.1 (10up.com) 30d 31 KiB

…css/frontend-style.css?ver=bed770e… (10up.com) 30d 24 KiB

…block-library/style.min.css?ver=6.4.2 (10up.com) 30d 15 KiB

…js/underscore.min.js?ver=1.13.4 (10up.com) 30d 8 KiB

…fonts/10up.ttf (10up.com) 30d 6 KiB

…dist/i18n.min.js?ver=7701b0c… (10up.com) 30d 4 KiB

…js/web-vitals.js?ver=170… (10up.com) 30d 3 KiB

…vendor/regenerator-runtime.min.js?ver=0.14.0 (10up.com) 30d 3 KiB

…vendor/wp-polyfill-inert.min.js?ver=3.1.2 (10up.com) 30d 3 KiB

about:blank 6/42
23/12/2023, 08:56 about:blank

Cache Transfer
URL
TTL Size

…dist/hooks.min.js?ver=c6aec9a… (10up.com) 30d 2 KiB

…js/frontend.js?ver=e8f3ca1… (10up.com) 30d 2 KiB

…build/loader.js?ver=f5c2d06… (10up.com) 30d 2 KiB

…js/wp-util.min.js?ver=6.4.2 (10up.com) 30d 1 KiB

…js/videos.js?ver=dacb491… (10up.com) 30d 1 KiB

…reframe/reframe.min.js?ver=2.2.7 (10up.com) 30d 1 KiB

…js/videos.js?ver=1.0.1 (10up.com) 30d 1 KiB

…img/10up-icon.svg (10up.com) 30d 1 KiB

…img/10up-icon-reversed.svg (10up.com) 30d 1 KiB

…img/careers-bg-video.mp4 (10up.com) 30d 0 KiB

Parse.ly Analytics 23 KiB

…10up.com/p.js?ver=3.12.0 (cdn.parsely.com) 1d 23 KiB

Google Analytics Analytics 21 KiB

/analytics.js (www.google-analytics.com) 2h 21 KiB

Vimeo Video 12 KiB

/api/player.js?ver=1.0.1 (player.vimeo.com) 30m 12 KiB

Adobe TypeKit Cdn 0 KiB

/p.gif?s=… (p.typekit.net) 7d 0 KiB

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

about:blank 7/42
23/12/2023, 08:56 about:blank

Potential
URL
Savings

Adobe TypeKit Cdn 3,800 ms

…27/l?subset_id=2&fvd=n7&v=3 (use.typekit.net) 310 ms

…27/l?subset_id=2&fvd=n8&v=3 (use.typekit.net) 200 ms

…27/l?subset_id=2&fvd=n1&v=3 (use.typekit.net) 230 ms

…27/l?subset_id=2&fvd=i1&v=3 (use.typekit.net) 310 ms

…27/l?subset_id=2&fvd=n6&v=3 (use.typekit.net) 330 ms

…27/l?subset_id=2&fvd=n4&v=3 (use.typekit.net) 290 ms

…27/l?subset_id=2&fvd=i4&v=3 (use.typekit.net) 310 ms

…27/l?subset_id=2&fvd=n3&v=3 (use.typekit.net) 250 ms

…27/l?subset_id=2&fvd=n4&v=3 (use.typekit.net) 310 ms

…27/l?subset_id=2&fvd=i4&v=3 (use.typekit.net) 300 ms

…27/l?subset_id=2&fvd=n7&v=3 (use.typekit.net) 310 ms

…27/l?subset_id=2&fvd=n3&v=3 (use.typekit.net) 330 ms

…27/l?subset_id=2&fvd=i3&v=3 (use.typekit.net) 310 ms

Loom – Screen Recorder & Screen Capture Chrome Extension 0 ms

chrome-extension://liecbddmkiiihnedobmlmillhodjkdmb/fonts/CircularXXWeb-Book.woff2 0 ms

Image elements do not 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

URL

Cloudinary Content

img.alt- …11/pod-group-photo@2x.jpg (res.cloudinary.com)


story-image

about:blank 8/42
23/12/2023, 08:56 about:blank

URL

img.alt-
story-image
…11/10up-snorkeling.jpg (res.cloudinary.com)

img.alt-
story-image
…11/10up-talking.jpg (res.cloudinary.com)

img.alt-
story-image
…11/10up-family-feud.jpg (res.cloudinary.com)

Defer offscreen images — Potential savings of 4 KiB

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.

Resource Potential
URL
Size Savings

Torrent Scanner
4.5 KiB 4.5 KiB
Chrome Extension

chrome-

img.sts-logo extension://aegnopegbbhjeeiganiajffnalhlkkjb/img/asset 4.5 KiB 4.5 KiB


s/ts-free-logo.png

Remove duplicate modules in JavaScript bundles — Potential savings of 35 KiB

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

about:blank 9/42
23/12/2023, 08:56 about:blank

Transfer Potential
Source
Size Savings

node_modules/webextension-polyfill 10 KiB

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext- 10 KiB
sdk/content.js

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext- 10 KiB
sdk/content.js

webpack://@eyeo/webext-sdk/./core/lib/content/elemHideEmulation.js 10 KiB

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext- 10 KiB
sdk/content.js

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext- 10 KiB
sdk/content.js

webpack://@eyeo/webext-sdk/./core/lib/patterns.js 0 KiB

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext- 0 KiB
sdk/content.js

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext- 0 KiB
sdk/content.js

Other 0 KiB

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext-
sdk/content.js

webpack://@eyeo/webext-sdk/./core/lib/common.js 0 KiB

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext- 0 KiB
sdk/content.js

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext- 0 KiB
sdk/content.js

webpack://@eyeo/webext-sdk/./sdk/content/element-collapsing.js 0 KiB

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext- 0 KiB
sdk/content.js

chrome- 0 KiB
extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext-

about:blank 10/42
23/12/2023, 08:56 about:blank

Transfer Potential
Source
Size Savings

sdk/content.js

webpack://@eyeo/webext-sdk/./sdk/content/subscribe-links.js 0 KiB

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext- 0 KiB
sdk/content.js

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext- 0 KiB
sdk/content.js

Avoid serving legacy JavaScript to modern browsers — Potential savings of 26 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

Show 3rd-party resources (3)

Potential
URL
Savings

Parse.ly Analytics 9.0 KiB

…10up.com/p.js?ver=3.12.0 (cdn.parsely.com) 9.0 KiB

p.js:7 Date.prototype.toJSON

@babel/plugin-
p.js:7
transform-classes

Loom – Screen Recorder & Screen Capture Chrome Extension 8.4 KiB

chrome-
extension://liecbddmkiiihnedobmlmillhodjkdmb/js/companion 8.4 KiB
Bubble.js

@babel/plugin-
companionBubble.js:4
transform-classes

companionBubble.js:4 Object.keys

Unattributable 8.3 KiB

chrome-
8.3 KiB
extension://chklaanhfefbnpoihckbnefhakgolnmc/js/content.js

content.js:503 Date.prototype.toJSON

about:blank 11/42
23/12/2023, 08:56 about:blank

Potential
URL
Savings

10up.com 1st Party 0.1 KiB

…vendor/wp-polyfill-inert.min.js?ver=3.1.2 (10up.com) 0.1 KiB

@babel/plugin-
wp-polyfill-inert.min.js:1
transform-classes

Vimeo Video 0.1 KiB

/api/player.js?ver=1.0.1 (player.vimeo.com) 0.1 KiB

@babel/plugin-
player.js:2
transform-classes

Page prevented back/forward cache restoration — 1 failure reason

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

Failure reason Failure type

The page has an unload handler in the main frame. Actionable

/careers/ (10up.com)

JavaScript execution time — 0.6 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

Show 3rd-party resources (2)

Total CPU Script Script


URL
Time Evaluation Parse

Unattributable 476 ms 129 ms 16 ms

Unattributable 396 ms 79 ms 0 ms

chrome-
extension://kbfnbcaeplbcioakkpcpgfkobkghlhen/src/js/Grammarly 80 ms 50 ms 16 ms
-check.js

Loom – Screen Recorder & Screen Capture Chrome Extension 268 ms 156 ms 94 ms

about:blank 12/42
23/12/2023, 08:56 about:blank

Total CPU Script Script


URL
Time Evaluation Parse

chrome-
extension://liecbddmkiiihnedobmlmillhodjkdmb/js/companionBu 268 ms 156 ms 94 ms
bble.js

10up.com 1st Party 229 ms 48 ms 37 ms

/careers/ (10up.com) 229 ms 48 ms 37 ms

Parse.ly Analytics 108 ms 82 ms 1 ms

…10up.com/p.js?ver=3.12.0 (cdn.parsely.com) 108 ms 82 ms 1 ms

Minimizes main-thread work — 1.3 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

Script Evaluation 582 ms

Other 406 ms

Script Parsing & Compilation 187 ms

Style & Layout 59 ms

Garbage Collection 57 ms

Parse HTML & CSS 31 ms

Rendering 13 ms

Avoid long main-thread tasks — 3 long tasks found

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

Show 3rd-party resources (1)

about:blank 13/42
23/12/2023, 08:56 about:blank

Start
URL Duration
Time

Loom – Screen Recorder & Screen Capture Chrome Extension 221 ms

chrome-extension://liecbddmkiiihnedobmlmillhodjkdmb/js/companionBubble.js 590 ms 221 ms

10up.com 1st Party 55 ms

/careers/ (10up.com) 349 ms 55 ms

Unattributable 50 ms

Unattributable 502 ms 50 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

Element CLS Contribution

span

0.000

0.000

0.000

0.000

a 0.000

about:blank 14/42
23/12/2023, 08:56 about:blank

Element CLS Contribution

User Timing marks and measures — 5 user timings

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.

Name Type Start Time Duration

__v3 Mark 0.00 ms

@grammarly-extension:checkScriptInitStart Mark 2,157.94 ms

@grammarly-extension:checkScriptInitEnd Mark 2,165.52 ms

@grammarly-extension:checkScriptInitStart Mark 3,143.50 ms

@grammarly-extension:checkScriptInitEnd Mark 3,151.60 ms

Avoids enormous network payloads — Total size was 1,116 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.

Show 3rd-party resources (5)

Transfer
URL
Size

Cloudinary Content 288.6 KiB

…11/pod-group-photo@2x.jpg (res.cloudinary.com) 211.2 KiB

…11/10up-family-feud.jpg (res.cloudinary.com) 45.1 KiB

…11/10up-snorkeling.jpg (res.cloudinary.com) 32.3 KiB

10up.com 1st Party 262.5 KiB

…img/careers-hero-large-fallback.jpg (10up.com) 86.1 KiB

about:blank 15/42
23/12/2023, 08:56 about:blank

Transfer
URL
Size

…img/careers-hero-large-fallback.jpg (10up.com) 86.0 KiB

…vendor/wp-polyfill.min.js?ver=3.15.0 (10up.com) 35.8 KiB

…jquery/jquery.min.js?ver=3.7.1 (10up.com) 31.0 KiB

…css/frontend-style.css?ver=bed770e… (10up.com) 23.5 KiB

Google Tag Manager Tag-Manager 162.1 KiB

/gtag/js?id=G-C7B7GMVE23&l=dataLayer&cx=c (www.googletagmanager.com) 84.2 KiB

/gtm.js?id=GTM-5KQZN66 (www.googletagmanager.com) 77.9 KiB

Avoids an excessive DOM size — 409 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

Statistic Element Value

Total DOM Elements 409

li.benefits--column-1-item

Maximum DOM Depth 11

body.page-template-default.page.page-
id-11153
Maximum Child Elements 23

Avoid chaining critical requests — 16 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: 2,561.408 ms

Initial Navigation

about:blank 16/42
23/12/2023, 08:56 about:blank

/careers/ (10up.com)

…block-library/style.min.css?ver=6.4.2 (10up.com) - 123.051 ms, 14.75 KiB

…css/frontend-style.css?ver=bed770e… (10up.com)

…fonts/10up.ttf (10up.com) - 100.601 ms, 5.71 KiB

…27/l?subset_id=2&fvd=n7&v=3 (use.typekit.net) - 314.637 ms, 19.65 KiB

…27/l?subset_id=2&fvd=n8&v=3 (use.typekit.net) - 201.721 ms, 20.05 KiB

…27/l?subset_id=2&fvd=n1&v=3 (use.typekit.net) - 233.112 ms, 18.67 KiB

…27/l?subset_id=2&fvd=i1&v=3 (use.typekit.net) - 309.678 ms, 19.28 KiB

…27/l?subset_id=2&fvd=n6&v=3 (use.typekit.net) - 327.911 ms, 19.40 KiB

…27/l?subset_id=2&fvd=n4&v=3 (use.typekit.net) - 285.619 ms, 19.11 KiB

…27/l?subset_id=2&fvd=i4&v=3 (use.typekit.net) - 307.499 ms, 19.80 KiB

…27/l?subset_id=2&fvd=n3&v=3 (use.typekit.net) - 254.739 ms, 19.09 KiB

…27/l?subset_id=2&fvd=n4&v=3 (use.typekit.net) - 314.452 ms, 19.05 KiB

…27/l?subset_id=2&fvd=i4&v=3 (use.typekit.net) - 298.921 ms, 19.01 KiB

…27/l?subset_id=2&fvd=n7&v=3 (use.typekit.net) - 309.115 ms, 18.82 KiB

…27/l?subset_id=2&fvd=n3&v=3 (use.typekit.net) - 331.352 ms, 15.72 KiB

…27/l?subset_id=2&fvd=i3&v=3 (use.typekit.net) - 312.008 ms, 15.43 KiB

…js/web-vitals.js?ver=170… (10up.com) - 122.027 ms, 3.29 KiB

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

Transfer Main-Thread
Third-Party
Size Blocking Time

RocketReach Chrome Extension Chrome Extension 615 KiB 0 ms

chrome-
extension://oiecklaabeielolbliiddlbokpfnmhba/chunks/Company- 289 KiB 0 ms
12559e48.js

chrome-
extension://oiecklaabeielolbliiddlbokpfnmhba/chunks/logging- 263 KiB 0 ms
df72f020.js

chrome-extension://oiecklaabeielolbliiddlbokpfnmhba/ui/content-
56 KiB 0 ms
script/index.js

Cloudinary Content 311 KiB 0 ms

…11/pod-group-photo@2x.jpg (res.cloudinary.com) 211 KiB 0 ms

…11/10up-family-feud.jpg (res.cloudinary.com) 45 KiB 0 ms

…11/10up-snorkeling.jpg (res.cloudinary.com) 32 KiB 0 ms

…11/10up-talking.jpg (res.cloudinary.com) 23 KiB 0 ms

about:blank 17/42
23/12/2023, 08:56 about:blank

Transfer Main-Thread
Third-Party
Size Blocking Time

Adobe TypeKit Cdn 250 KiB 0 ms

…27/l?subset_id=2&fvd=n8&v=3 (use.typekit.net) 20 KiB 0 ms

…27/l?subset_id=2&fvd=i4&v=3 (use.typekit.net) 20 KiB 0 ms

…27/l?subset_id=2&fvd=n7&v=3 (use.typekit.net) 20 KiB 0 ms

…27/l?subset_id=2&fvd=n6&v=3 (use.typekit.net) 19 KiB 0 ms

…27/l?subset_id=2&fvd=i1&v=3 (use.typekit.net) 19 KiB 0 ms

Other resources 152 KiB 0 ms

Google Tag Manager Tag-Manager 162 KiB 0 ms

/gtag/js?id=G-
84 KiB 0 ms
C7B7GMVE23&l=dataLayer&cx=c (www.googletagmanager.com)

/gtm.js?id=GTM-5KQZN66 (www.googletagmanager.com) 78 KiB 0 ms

Loom – Screen Recorder & Screen Capture Chrome Extension 67 KiB 0 ms

chrome-
extension://liecbddmkiiihnedobmlmillhodjkdmb/fonts/CircularXXWeb- 67 KiB 0 ms
Book.woff2

Torrent Scanner Chrome Extension 32 KiB 0 ms

chrome-
21 KiB 0 ms
extension://aegnopegbbhjeeiganiajffnalhlkkjb/css/custom.css

chrome-
extension://aegnopegbbhjeeiganiajffnalhlkkjb/img/assets/ts-free- 4 KiB 0 ms
logo.png

Other resources 6 KiB 0 ms

Parse.ly Analytics 24 KiB 0 ms

…10up.com/p.js?ver=3.12.0 (cdn.parsely.com) 23 KiB 0 ms

Google Analytics Analytics 21 KiB 0 ms

/analytics.js (www.google-analytics.com) 21 KiB 0 ms

Vimeo Video 12 KiB 0 ms

/api/player.js?ver=1.0.1 (player.vimeo.com) 12 KiB 0 ms

Largest Contentful Paint element — 890 ms

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

about:blank 18/42
23/12/2023, 08:56 about:blank

Element

div.video-marketing__background-video

Phase % of LCP Timing

TTFB 209% 1,870 ms

Load Delay 0% 0 ms

Load Time 0% 0 ms

Render Delay -109% -980 ms

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

PASSED AUDITS (15) Hide

Eliminate render-blocking resources

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.

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.

Efficiently encode images

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 19/42
23/12/2023, 08:56 about:blank

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: More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the
most important origins.

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

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.

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

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

about:blank 20/42
23/12/2023, 08:56 about:blank

Element

div.video-marketing__background-video

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

Avoids document.write()

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

Avoid non-composited animations

Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animations
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

96

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

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.

about:blank 21/42
23/12/2023, 08:56 about:blank

Failing Elements

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

about:blank 22/42
23/12/2023, 08:56 about:blank

Failing Elements

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

about:blank 23/42
23/12/2023, 08:56 about:blank

Failing Elements

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

about:blank 24/42
23/12/2023, 08:56 about:blank

Failing Elements

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

about:blank 25/42
23/12/2023, 08:56 about:blank

Failing Elements

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

span.tu-card__action

a.tu-card.tu-card--promo-block.tu-card--link.flex-item.-sm-25.-lg-33.-bg-very-light-
gray.-border-medium-gray-2

These are opportunities to improve the legibility of your content.

AUDIO AND VIDEO

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

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

video

These are opportunities to provide alternative content for audio and video. This may improve the experience for users with
hearing or vision impairments.

about:blank 26/42
23/12/2023, 08:56 about:blank

ADDITIONAL ITEMS TO MANUALLY CHECK (10) Hide

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

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.

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.

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.

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.

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.

Custom controls have associated labels

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

about:blank 27/42
23/12/2023, 08:56 about:blank

Custom controls have ARIA roles

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

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

PASSED AUDITS (23) 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.

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

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.

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.

about:blank 28/42
23/12/2023, 08:56 about:blank

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

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

[role] values are valid

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

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.

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

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

Links are distinguishable without relying on color.

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for
users with low vision. Learn how to make links distinguishable.

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

about:blank 29/42
23/12/2023, 08:56 about:blank

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.

Heading elements appear 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.

Skip links are focusable.

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Values assigned to role="" are valid ARIA roles.

ARIA roles enable assistive technologies to know the role of each element on the web page. If the role values are
misspelled, not existing ARIA role values, or abstract roles, then the purpose of the element will not be communicated to
users of assistive technologies. Learn more about ARIA roles.

Image elements do not have [alt] attributes that are redundant text.

Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text
adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn
more about the alt attribute.

NOT APPLICABLE (36) 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.

button, link, and menuitem elements have accessible names

about:blank 30/42
23/12/2023, 08:56 about:blank

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.

Elements with role="dialog" or role="alertdialog" have accessible names.

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.

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

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.

Elements with the role=text attribute do not have focusable descendents.

Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's
focusable descendents will not be announced. Learn more about the role=text attribute.

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

about:blank 31/42
23/12/2023, 08:56 about:blank

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.

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.

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

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.

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.

<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.

If the webpage does not specify a consistent language, then the screen reader might not announce the page's text
correctly. Learn more about the lang attribute.

Input buttons have discernible text.

Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input
button. Learn more about input buttons.

about:blank 32/42
23/12/2023, 08:56 about:blank

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

Elements with visible text labels have matching accessible names.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users.
Learn more about accessible names.

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.

Select elements have associated label elements.

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the
select element.

Tables have different content in the summary attribute and <caption>.

The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate
table mark-up helps users of screen readers. Learn more about summary and caption.

Tables use <caption> instead of cells with the [colspan] attribute to indicate a caption.

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead
of cells with the [colspan] attribute may improve the experience for screen reader users. Learn more about captions.

<td> elements in a large <table> have one or more table headers.

Screen readers have features to make navigating tables easier. Ensuring that <td> elements in a large table (3 or more
cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more
about table headers.

about:blank 33/42
23/12/2023, 08:56 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.

All heading elements contain content.

A heading with no content or inaccessible text prevent screen reader users from accessing information on the page's
structure. Learn more about headings.

Identical links have the same purpose.

Links with the same destination should have the same description, to help users understand the link's purpose and decide
whether to follow it. Learn more about identical links.

Document has a main landmark.

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

Touch targets have sufficient size and spacing.

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

82

Best Practices

USER EXPERIENCE

Serves images with low resolution

about:blank 34/42
23/12/2023, 08:56 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.

Displayed Actual Expected


URL
size size size

Cloudinary Content

…11/10up- 1280 x 2560 x


720 x 470
snorkeling.jpg (res.cloudinary.com) 836 1672

img.alt-story-image

GENERAL

Registers an unload listener

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

Source

limit-time.js:102

Browser errors were 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

Source Description

10up.com 1st Party

careers/:363 ReferenceError: wp is not defined at https://10up.com/careers/:363:1

Issues were logged 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.

about:blank 35/42
23/12/2023, 08:56 about:blank

Issue type

Cookie

/api/player.js?ver=1.0.1 (player.vimeo.com)

/careers/ (10up.com)

/analytics.js (www.google-analytics.com)

/j/collect?v=… (www.google-analytics.com)

/g/collect?v=… (www.google-analytics.com)

Detected JavaScript libraries

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

Name Version

jQuery 3.7.1

Underscore 1.13.6

WordPress 6.4.2

core-js core-js-global@3.31.0

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

Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes
script-src High
instead, along with `'strict-dynamic'` if necessary.

`'unsafe-inline'` allows the execution of unsafe in-page scripts and event handlers.
script-src High
Consider using CSP nonces or hashes to allow scripts individually.

PASSED AUDITS (9) Hide

Uses HTTPS

about:blank 36/42
23/12/2023, 08:56 about:blank

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 deprecated APIs

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

Allows users to paste into input fields

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

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.

Displays images with correct aspect ratio

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

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.

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.

Show 3rd-party resources (1)

about:blank 37/42
23/12/2023, 08:56 about:blank

URL Map URL

Loom – Screen Recorder & Screen Capture


Chrome Extension

chrome- chrome-
extension://liecbddmkiiihnedobmlmillhodjkdmb/js/c extension://liecbddmkiiihnedobmlmillhodjkdmb/js/
ompanionBubble.js companionBubble.js.map

Error: Failed fetching source map (null)

Unattributable

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendo
r/@eyeo/webext-sdk/content.js

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendo
r/@eyeo/webext-sdk/content.js

NOT APPLICABLE (1) Hide

Fonts with font-display: optional are preloaded

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

Links do not have descriptive text — 3 links found

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

Show 3rd-party resources (1)

about:blank 38/42
23/12/2023, 08:56 about:blank

Link destination Link Text

Torrent Scanner Chrome Extension

chrome-extension://aegnopegbbhjeeiganiajffnalhlkkjb/faq.html Click here

Unattributable

/privacy-policy/ (www.adaware.com) Read more

/contact.aspx (pcsoftwareinfo.com) Click here

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

CRAWLING AND INDEXING

Links are not 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

Uncrawlable Link

a.license-buy-link

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

ADDITIONAL ITEMS TO MANUALLY CHECK (1) Hide

Structured data is valid

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

about:blank 39/42
23/12/2023, 08:56 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.

Document has a meta description

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

Page has successful HTTP status code

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

Page isn’t 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.

robots.txt is valid

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

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

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

about:blank 40/42
23/12/2023, 08:56 about:blank

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.

Failure reason

Page has no manifest <link> URL

PWA OPTIMIZED

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

about:blank 41/42
23/12/2023, 08:56 about:blank

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
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 Dec 23, 2023, Emulated Desktop with Single page load
8:52 AM GMT+5:30 Lighthouse 11.2.0
Initial page load Custom throttling Using Chromium 120.0.0.0
with devtools

Generated by Lighthouse 11.2.0 | File an issue

about:blank 42/42

You might also like