Duckhuntjs - Duckhuntjs.com

Overview

Snoop Summary for duckhuntjs.com

This is a free and comprehensive report about duckhuntjs.com. The domain duckhuntjs.com is currently hosted on a server located in United States with the IP address 104.21.13.143, where the local currency is USD and English is the local language. Duckhuntjs.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If duckhuntjs.com was to be sold it would possibly be worth $948 USD (based on the daily revenue potential of the website over a 24 month period). Duckhuntjs.com receives an estimated 451 unique visitors every day - a decent amount of traffic! This report was last updated 24th October, 2022.

About duckhuntjs.com

Site Preview:
Title:	DuckHuntJS
Description:	An open source, web based, responsive implementation of Duck Hunt in canvas or webgl depending on your client.
Keywords and Tags:	games
Related Terms:	webgl
Fav Icon:
Age:	Over 8 years old
Domain Created:	30th September, 2015
Domain Updated:	30th September, 2022
Domain Expires:	30th September, 2027

Review

Snoop Score

1/5

Valuation

$948 USD

Note: All valuation figures are estimates.

Popularity

Low

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	1,940,328
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority:	0
Moz Page Authority:	0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors:	451
Monthly Visitors:	13,727
Yearly Visitors:	164,615

Note: All visitors figures are estimates.

Visitors By Country

Revenue

Daily Revenue:	$1 USD
Monthly Revenue:	$39 USD
Yearly Revenue:	$469 USD

Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top Ranking Keywords (US)

Domain Analysis

	Value	Length
Domain:	duckhuntjs.com	14
Domain Name:	duckhuntjs	10
Extension (TLD):	com	3

Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

PWA

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

Simulate loading on desktop

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for duckhuntjs.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.

Time to Interactive — 0.8 s
The time taken for the page to become fully interactive.

Speed Index — 1.0 s
The time taken for the page contents to be visibly populated.

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.

First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://duckhuntjs.com/	http/1.1	0	148.9700000966	1197	630	200	text/html	Document
http://duckhuntjs.com/duckhunt.js	http/1.1	155.31100006774	423.53300005198	554203	2615477	200	application/javascript	Script
http://duckhuntjs.com/audio.ogg	http/1.1	691.11800007522	784.53200007789	370053	369161	200	binary/octet-stream	XHR
http://duckhuntjs.com/sprites.json	http/1.1	721.17999999318	834.40200006589	11977	11137	200	binary/octet-stream	XHR
http://duckhuntjs.com/sprites.png	http/1.1	845.35900002811	1012.2609999962	352001	351118	200	image/png	Image

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
153.435	8.315
429.146	6.026
496.172	29.102
525.283	169.97
699.795	22.953
786.84	5.578
1027.194	45.525
1072.755	9.921
1082.692	9.157
1109.048	7.053
1126.443	7.048
1144.186	7.834
1152.042	7.787
1174.116	7.385
1188.861	7.945
1204.73	7.659
1220.132	7.61
1234.74	8.532
1249.546	8.378
1263.892	7.584
1278.603	8.519
1294.881	7.599
1311.578	7.373
1328.336	8.494
1344.804	8.627
1361.582	8.233
1378.265	7.145
1394.959	8.466
1411.589	8.754
1428.177	7.18
1444.837	7.208
1461.547	7.141
1478.175	7.072
1494.814	7.455
1511.506	6.593
1528.253	8.562
1544.954	9.094
1561.782	7.66
1578.449	8.676
1595.002	8.07
1611.522	7.205
1628.265	7.103
1645.199	7.581
1661.71	7.445
1678.153	7.724
1695.257	7.107
1711.67	8.807
1728.204	8.616
1744.843	7.274
1761.549	7.495
1778.311	8.473
1795.074	9.611
1811.61	10.664
1830.174	8.299
1846.041	9.026
1861.514	8.174
1878.174	8.167
1894.811	7.501
1911.414	7.45
1928.243	7.165
1944.985	7.966
1961.525	8.78
1978.36	8.123
1994.934	7.841
2011.648	9.565
2028.241	7.213
2045.031	8.092
2064.614	10.125
2079.911	7.824
2099.94	8.488
2116.093	8.342
2130.611	7.493
2144.854	7.903
2161.622	8.051
2179.206	9.572
2195.735	8.927
2211.479	8.608
2228.348	9.729
2246.417	7.599
2263.527	8.912
2278.115	8.72
2295.233	9.7
2311.462	7.457
2328.214	8.641
2344.923	8.809
2361.65	8.731
2378.008	7.443
2394.768	7.804
2411.558	7.849
2428.221	8.026
2444.797	6.74
2461.425	7.086
2478.094	7.911
2494.819	7.501
2512.435	9.261
2530.293	7.894
2545.977	9.27
2562.243	8.293
2580.142	8.836
2596.773	7.505
2611.622	8.821
2628.256	8.39
2644.942	7.966
2661.559	8.351
2678.186	8.141
2695.011	8.394
2711.442	8.043
2728.072	7.265
2744.976	8.484
2761.383	8.505
2778.186	7.53
2794.747	7.184
2812.778	10.429
2828.543	8.738
2847.883	12.795
2867.643	8.783
2882.87	9.08
2898.836	7.949
2913.982	8.867
2930.267	8.283
2945.151	7.32
2961.449	6.907
2978.108	7.991
2994.935	8.676
3011.44	8.48
3029.353	8
3046.034	8.021
3061.35	7.916
3078.102	8.838
3094.987	8.564
3111.756	9.1
3128.088	7.896
3144.754	7.46
3161.537	8.738
3178.209	8.978
3194.848	8.1
3211.48	7.692
3228.139	8.218
3244.706	11.822
3261.584	7.538
3278.089	7.617
3295.04	8.64
3311.615	7.789
3328.06	7.552
3344.781	7.801
3362.882	9.301
3384.56	8.376
3397.425	8.433
3411.378	8.949

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Duckhuntjs.com should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Duckhuntjs.com should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Duckhuntjs.com should consider minifying CSS files.

Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Duckhuntjs.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.

Enable text compression — Potential savings of 9 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
http://duckhuntjs.com/sprites.json	11137	8865

Show Details

Initial server response time was short — Root document took 150 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.

URL	Time Spent (Ms)
http://duckhuntjs.com/	149.965

Show Details

Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Duckhuntjs.com should avoid multiple or unnecessary page redirects.

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Duckhuntjs.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.

Avoid serving legacy JavaScript to modern browsers — Potential savings of 5 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

URL	Potential Savings (Bytes)
http://duckhuntjs.com/duckhunt.js	4634

Show Details

Avoids enormous network payloads — Total size was 1,259 KiB
Large network payloads can cost users money and are linked to long load times.

URL	Transfer Size (Bytes)
http://duckhuntjs.com/duckhunt.js	554203
http://duckhuntjs.com/audio.ogg	370053
http://duckhuntjs.com/sprites.png	352001
http://duckhuntjs.com/sprites.json	11977
http://duckhuntjs.com/	1197

Show Details

Avoids an excessive DOM size — 1 element
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.

Statistic	Element	Value
Total DOM Elements		1
Maximum DOM Depth	body > canvas	2
Maximum Child Elements	body	1

Show Details

Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Duckhuntjs.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

URL	Total CPU Time (Ms)	Script Evaluation (Ms)	Script Parse (Ms)
http://duckhuntjs.com/	991.491	3.788	1.25
http://duckhuntjs.com/duckhunt.js	453.526	284.131	51.42
Unattributable	53.014	2.039	0

Show Details

Minimizes main-thread work — 1.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

Category	Time Spent (Ms)
Rendering	1027.798
Script Evaluation	289.958
Other	119.126
Script Parsing & Compilation	52.67
Style & Layout	4.206
Garbage Collection	3.704
Parse HTML & CSS	0.609

Show Details

All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.

Keep request counts low and transfer sizes small — 5 requests • 1,259 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.

Resource Type	Requests	Transfer Size (Bytes)
Total	5	1289431
Script	1	554203
Other	2	382030
Image	1	352001
Document	1	1197
Stylesheet	0	0
Media	0	0
Font	0	0
Third-party	0	0

Show Details

Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).

Largest Contentful Paint element — 0 elements found
The element which was identified as the Largest Contentful Paint.

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.

Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.

Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.

Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

URL	Start Time (Ms)	Duration (Ms)
http://duckhuntjs.com/duckhunt.js	700	85

Show Details

Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Eliminate render-blocking resources — Potential savings of 600 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Duckhuntjs.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

URL	Transfer Size (Bytes)	Potential Savings (Ms)
http://duckhuntjs.com/duckhunt.js	554203	510

Show Details

Minify JavaScript — Potential savings of 285 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Duckhuntjs.com should consider minifying JS files.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
http://duckhuntjs.com/duckhunt.js	554203	292302

Show Details

Reduce unused JavaScript — Potential savings of 220 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
http://duckhuntjs.com/duckhunt.js	554203	225357

Show Details

Serve images in next-gen formats — Potential savings of 263 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.

URL	Resource Size (Bytes)	Potential Savings (Bytes)
http://duckhuntjs.com/sprites.png	351118	269348

Show Details

Metrics

Largest Contentful Paint
The timing of the largest text or image that is painted.

Other

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Serve static assets with an efficient cache policy — 2 resources found
Duckhuntjs.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.

URL	Cache TTL (Ms)	Transfer Size (Bytes)
http://duckhuntjs.com/duckhunt.js	14400000	554203
http://duckhuntjs.com/sprites.png	14400000	352001

Show Details

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of duckhuntjs.com on mobile screens.

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of duckhuntjs.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.

The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.

Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.

`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.

ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.

ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.

`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.

`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.

ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.

ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.

`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.

`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.

Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.

Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.

Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.

`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Duckhuntjs.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.

Failing Elements
html

Show Details

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.

Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.

Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.

The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.

User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.

Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.

Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.

Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.

Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.

HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that duckhuntjs.com should incorporate. This includes practices such as protecting pages with HTTPS.

Passing (14)
Failing (2)

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).

Description	Directive	Severity
No CSP found in enforcement mode		High

Show Details

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.

Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.

Name	Version
Pixi.js	4.8.9
GreenSock JS	1.20.5

Show Details

Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

URL	Map URL
http://duckhuntjs.com/duckhunt.js	http://duckhuntjs.com/duckhunt.js.map

Show Details

No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 5 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.

Insecure URL	Request Resolution
http://duckhuntjs.com/	Allowed
http://duckhuntjs.com/duckhunt.js	Allowed
http://duckhuntjs.com/audio.ogg	Allowed
http://duckhuntjs.com/sprites.json	Allowed
http://duckhuntjs.com/sprites.png	Allowed

Show Details

Includes front-end JavaScript libraries with known security vulnerabilities — 1 vulnerability detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Library Version	Vulnerability Count	Highest Severity
SHOW DETAILS	1	High

Show Details

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for duckhuntjs.com. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.

Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.

Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.

Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of duckhuntjs.com. This includes details about web app manifests.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

Failure reason
No manifest was fetched

Show Details

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of duckhuntjs.com on mobile screens.

Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.

Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.

Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

PWA

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

Simulate loading on mobile

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for duckhuntjs.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Duckhuntjs.com should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Duckhuntjs.com should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Duckhuntjs.com should consider minifying CSS files.

Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Duckhuntjs.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.

Serve images in next-gen formats — Potential savings of 263 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.

URL	Resource Size (Bytes)	Potential Savings (Bytes)
http://duckhuntjs.com/sprites.png	351118	269348

Show Details

Enable text compression — Potential savings of 9 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
http://duckhuntjs.com/sprites.json	11137	8865

Show Details

Initial server response time was short — Root document took 150 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.

URL	Time Spent (Ms)
http://duckhuntjs.com/	150.715

Show Details

Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Duckhuntjs.com should avoid multiple or unnecessary page redirects.

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Duckhuntjs.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.

Avoid serving legacy JavaScript to modern browsers — Potential savings of 5 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

URL	Potential Savings (Bytes)
http://duckhuntjs.com/duckhunt.js	4634

Show Details

Avoids enormous network payloads — Total size was 1,259 KiB
Large network payloads can cost users money and are linked to long load times.

URL	Transfer Size (Bytes)
http://duckhuntjs.com/duckhunt.js	554206
http://duckhuntjs.com/audio.ogg	370053
http://duckhuntjs.com/sprites.png	352000
http://duckhuntjs.com/sprites.json	11973
http://duckhuntjs.com/	1203

Show Details

Avoids an excessive DOM size — 2 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.

Statistic	Element	Value
Total DOM Elements		2
Maximum DOM Depth	body > button	2
Maximum Child Elements	body	2

Show Details

Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Duckhuntjs.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.

Keep request counts low and transfer sizes small — 5 requests • 1,259 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.

Resource Type	Requests	Transfer Size (Bytes)
Total	5	1289435
Script	1	554206
Other	2	382026
Image	1	352000
Document	1	1203
Stylesheet	0	0
Media	0	0
Font	0	0
Third-party	0	0

Show Details

Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).

Largest Contentful Paint element — 0 elements found
The element which was identified as the Largest Contentful Paint.

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.

Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.

Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.

Avoid long main-thread tasks — 20 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

URL	Start Time (Ms)	Duration (Ms)
http://duckhuntjs.com/duckhunt.js	3810	1382
http://duckhuntjs.com/duckhunt.js	15067	646
http://duckhuntjs.com/duckhunt.js	36488	638
http://duckhuntjs.com/duckhunt.js	15713	602
http://duckhuntjs.com/duckhunt.js	19326	497
http://duckhuntjs.com/duckhunt.js	20459	386
http://duckhuntjs.com/duckhunt.js	25912	356
http://duckhuntjs.com/duckhunt.js	20106	353
http://duckhuntjs.com/duckhunt.js	13144	313
http://duckhuntjs.com/duckhunt.js	27861	313
http://duckhuntjs.com/duckhunt.js	21452	311
http://duckhuntjs.com/duckhunt.js	19823	283
http://duckhuntjs.com/duckhunt.js	19054	272
http://duckhuntjs.com/duckhunt.js	23116	272
http://duckhuntjs.com/duckhunt.js	24573	260
http://duckhuntjs.com/duckhunt.js	22620	257
http://duckhuntjs.com/duckhunt.js	23840	243
http://duckhuntjs.com/duckhunt.js	22877	239
http://duckhuntjs.com/duckhunt.js	21763	238
http://duckhuntjs.com/duckhunt.js	21055	235

Show Details

Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://duckhuntjs.com/	http/1.1	0	149.7209998779	1203	630	200	text/html	Document
http://duckhuntjs.com/duckhunt.js	http/1.1	159.16199982166	425.22199987434	554206	2615477	200	application/javascript	Script
http://duckhuntjs.com/audio.ogg	http/1.1	876.58199993894	972.13999996893	370053	369161	200	binary/octet-stream	XHR
http://duckhuntjs.com/sprites.json	http/1.1	907.45399985462	1049.1039999761	11973	11137	200	binary/octet-stream	XHR
http://duckhuntjs.com/sprites.png	http/1.1	1059.7639998887	1144.6809999179	352000	351118	200	image/png	Image

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
154.093	8.845
429.441	5.983
503.096	30.958
534.072	345.575
880.487	28.769
974.089	5.519
1161.72	71.625
1233.37	28.595
1261.981	32.815
1295.096	30.623
1325.748	32.278
1358.067	54.642
1412.742	23.857
1436.637	32.646
1469.316	24.185
1493.532	28.127
1521.739	25.049
1546.825	24.456
1578.95	26.769
1605.755	33.898
1639.735	26.68
1666.463	23.328
1694.698	45.871
1740.597	39.814
1780.453	29.102
1809.592	55.726
1865.358	41.94
1907.338	35.612
1943.079	25.746
1968.863	29.102
1997.994	22.796
2020.825	32.654
2053.521	27.788
2081.344	23.227
2105.751	24.627
2130.423	27.95
2158.407	23.36
2181.804	20.063
2201.906	23.543
2225.829	34.603
2260.47	24.931
2285.427	20.956
2306.417	55.476
2361.924	56.813
2418.772	15.504
2435.488	17.528
2453.048	19.38
2472.462	22.994
2495.494	26.779
2522.307	25.099
2547.459	21.075
2568.562	22.679
2591.279	13.684
2605.365	16.678
2622.221	22.262
2644.511	17.121
2661.675	18.411
2680.122	18.363
2698.531	17.651
2716.399	18.872
2738.379	12.69
2754.932	17.685
2772.645	16.367
2789.041	17.775
2806.843	21.774
2828.653	22.862
2851.549	22.65
2874.247	21.139
2895.418	22.51
2917.965	22.166
2940.183	21.981
2962.233	20.545
2982.883	18.972
3001.879	21.413
3023.337	30.647
3054.022	23.342
3077.403	22.762
3100.222	21.701
3121.955	26.311
3148.303	22.871
3171.991	24.35
3196.377	37.258
3233.668	34.935
3268.647	78.183
3346.896	38.312
3385.218	15.073
3400.335	25.209
3425.578	31.9
3457.519	26.435
3483.979	23.695
3513.875	31.811
3545.724	24.115
3569.876	24.449
3595.421	23.512
3621.709	23.585
3645.328	23.126
3668.486	35.593
3704.115	21.074
3725.222	25.45
3750.72	24.313
3779	161.54
3940.581	150.423
4091.281	34.93
4126.34	26.733
4153.126	29.67
4200.506	31.892
4232.437	33.074
4265.549	42.802
4308.385	23.636
4332.048	58.09
4390.169	17.238
4407.658	49.035
4456.73	56.934
4533.264	25.756
4560.694	41.047
4601.771	35.077
4636.886	53.04
4690.024	28.739
4721.557	6.3
4727.907	37.149
4765.297	49.793
4815.158	27.178
4856.656	67.996
4924.714	124.362
5049.121	14.956
5064.087	6.46
5070.584	70.635
5172.211	88.213
5260.463	96.421
5357.058	52.44
5409.536	58.696
5468.445	40.528
5509.003	77.845
5586.888	59.423
5646.47	49.671
5696.167	56.775
5752.989	48.278
5801.451	64.172
5865.663	59.817
5925.693	68.094
5993.825	47.37
6041.397	38.598
6080.041	27.264
6108.021	16.256
6124.313	60.633
6184.988	24.501
6227.727	33.413
6274.699	37.551
6312.726	26.968
6345.809	64.993
6410.837	42.824
6453.828	35.282
6489.143	53.198
6542.406	44.208
6586.787	40.061
6626.887	54.163
6681.11	89.041
6770.169	9.881
6780.09	32.596
6813.062	28.611
6841.715	30.602
6872.352	25.812
6898.211	26.438
6924.683	33.145
6957.856	28.986
6986.878	32.894
7019.808	25.087
7044.938	28.189
7073.4	23.536
7108.383	23.598
7132.015	29.174
7161.238	29.663
7190.911	6.486
7197.446	78.337
7277.34	31.624
7309.191	23.401
7341.39	33.877
7375.315	29.531
7404.887	26.022
7430.939	26.195
7457.173	31.435
7488.656	33.631
7522.64	27.18
7549.854	22.823
7572.776	47.877
7620.691	41.258
7661.988	26.352
7688.422	32.038
7720.513	24.382
7744.93	26.662
7771.626	27.216
7798.874	25.804
7824.71	28.348
7853.107	26.161
7879.305	26.763
7906.109	24.48
7930.619	24.663
7955.315	22.442
7977.792	34.305
8012.133	23.026
8035.193	30.77
8065.997	23.127
8089.158	27.915
8117.114	51.723
8168.887	23.624
8192.668	22.51
8215.213	17.798
8233.037	23.806
8256.886	24.193
8281.116	21.717
8302.869	23.985
8326.897	28.672
8355.715	26.878
8382.626	29.252
8411.912	27.53
8439.48	36.454
8477.318	30.369
8507.749	18.539
8526.325	26.209
8552.585	28.529
8581.147	32.752
8613.939	26.975
8640.972	23.82
8665.11	22.741
8692.277	33.109
8725.428	26.042
8751.521	32.076
8783.633	23.871
8807.539	35.516
8843.127	54.196
8897.623	29.717
8927.489	39.037
8966.561	24.34
8990.953	21.224
9012.21	28.49
9040.8	21.708
9062.529	30.811
9093.38	17.476
9110.89	17.167
9128.082	20.963
9149.074	24.093
9185	19.019
9204.059	19.352
9223.476	23.15
9246.661	27.549
9274.262	18.67
9292.96	16.086
9309.078	16.677
9325.79	21.392
9347.222	19.355
9367.581	19.644
9387.349	159.463
9547.475	21.848
9569.703	19.179
9588.909	18.581
9607.517	17.452
9625.003	23.024
9648.067	33.349
9702.393	24.524
9726.953	24.54
9751.528	21.522
9773.596	23.373
9796.997	22.341
9823.66	24.325
9848.027	28.841
9876.922	23.153
9900.117	24.483
9924.69	26.867
9951.597	26.137
9977.774	25.871
10003.679	24.033
10027.745	24.164
10051.944	21.842
10074.108	22.764
10096.909	24.446
10121.393	21.598
10143.033	28.443
10171.532	26.709
10198.281	21.033
10222.854	24.184
10247.075	27.835
10274.943	22.946
10297.921	24.926
10322.881	26.488
10349.405	25.827
10375.264	22.653
10397.952	20.532
10418.629	24.841
10443.502	19.713
10463.259	19.491
10487.949	28.841
10517.013	21.553
10538.6	25.359
10563.99	18.352
10583.379	22.319
10605.737	31.915
10637.72	24.961
10662.73	23.434
10686.21	22.258
10708.506	23.614
10732.155	27.25
10759.44	28.636
10788.387	25.761
10814.165	10.108
10825.041	17.469

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 5.0 s
The time taken for the first image or text on the page to be rendered.

Time to Interactive — 40.9 s
The time taken for the page to become fully interactive.

Total Blocking Time — 22,050 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Largest Contentful Paint
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 1,380 ms
Users could experience a delay when interacting with the page.

First Meaningful Paint — 5.0 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 4,320 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Duckhuntjs.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

URL	Transfer Size (Bytes)	Potential Savings (Ms)
http://duckhuntjs.com/duckhunt.js	554206	2880

Show Details

Minify JavaScript — Potential savings of 285 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Duckhuntjs.com should consider minifying JS files.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
http://duckhuntjs.com/duckhunt.js	554206	292304

Show Details

Reduce unused JavaScript — Potential savings of 220 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
http://duckhuntjs.com/duckhunt.js	554206	224792

Show Details

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Serve static assets with an efficient cache policy — 2 resources found
Duckhuntjs.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.

URL	Cache TTL (Ms)	Transfer Size (Bytes)
http://duckhuntjs.com/duckhunt.js	14400000	554206
http://duckhuntjs.com/sprites.png	14400000	352000

Show Details

Reduce JavaScript execution time — 4.8 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

URL	Total CPU Time (Ms)	Script Evaluation (Ms)	Script Parse (Ms)
http://duckhuntjs.com/	30090.98	445.968	5.588
http://duckhuntjs.com/duckhunt.js	9118.748	3945.36	334.396
Unattributable	384.216	109.568	0

Show Details

Minimize main-thread work — 39.6 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

Category	Time Spent (Ms)
Rendering	32747.632
Script Evaluation	4500.896
Other	1885.428
Script Parsing & Compilation	339.984
Garbage Collection	71.72
Style & Layout	45.728
Parse HTML & CSS	2.788

Show Details

Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Source
SHOW DETAILS
SHOW DETAILS

Show Details

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of duckhuntjs.com on mobile screens.

First Contentful Paint (3G) — 9303 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.