Digdig - Digdig.io

Overview

Snoop Summary for digdig.io

This is a free and comprehensive report about digdig.io. Our records indicate that digdig.io is privately registered by REDACTED FOR PRIVACY. Digdig.io has the potential to be earning an estimated $7 USD per day from advertising revenue. If digdig.io was to be sold it would possibly be worth $4,946 USD (based on the daily revenue potential of the website over a 24 month period). Digdig.io receives an estimated 2,372 unique visitors every day - a large amount of traffic! This report was last updated 10th November, 2024.

About digdig.io

Site Preview:
Title:	digdig.io
Description:	Dig and destroy your foes
Keywords and Tags:	games
Related Terms:	destroy, foes io, foes io com, foes io play, foes io unblocked, foes io unblocked 66
Fav Icon:
Age:	Over 3 years old
Domain Created:	29th June, 2021
Domain Updated:	31st May, 2024
Domain Expires:	29th June, 2025

Review

Snoop Score

2/5

Valuation

$4,946 USD

Note: All valuation figures are estimates.

Popularity

Modest

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	222,029
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:	2,372
Monthly Visitors:	72,207
Yearly Visitors:	865,915

Note: All visitors figures are estimates.

Visitors By Country

Revenue

Daily Revenue:	$7 USD
Monthly Revenue:	$206 USD
Yearly Revenue:	$2,468 USD

Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top Ranking Keywords (US)

Domain Analysis

	Value	Length
Domain:	digdig.io	9
Domain Name:	digdig	6
Extension (TLD):	io	2

Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

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

URL: https://digdig.io/

Updated: 12th August, 2021

1.48 seconds

First Contentful Paint (FCP)

83%

10%

7%

0.01 seconds

First Input Delay (FID)

98%

2%

0%

Simulate loading on desktop

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for digdig.io. 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.

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

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

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

Other

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://digdig.io/	http/1.1	0	68.514999933541	750	0	301
https://digdig.io/	h2	69.203999824822	423.76899998635	2543	4486	200	text/html	Document
https://fonts.googleapis.com/css?family=Ubuntu:700	h2	438.34099988453	449.57099994645	1239	1728	200	text/css	Stylesheet
https://static.digdig.io/a59c3d4102ded0d8fdea4e0a0c20851e8e084ac3/client.js	h2	453.11999996193	554.03899983503	107110	106215	200	text/plain	Script
https://fonts.gstatic.com/s/ubuntu/v15/4iCv6KVjbNBYlgoCxCvjsGyNPYZvgw.woff2	h2	453.96299986169	456.90999994986	14853	14096	200	font/woff2	Font
https://static.digdig.io/a59c3d4102ded0d8fdea4e0a0c20851e8e084ac3/client.wasm	h2	573.04199994542	739.32399996556	1618014	1617123	200	application/octet-stream	Fetch
https://static.digdig.io/a59c3d4102ded0d8fdea4e0a0c20851e8e084ac3/client.wasm	h2	747.37300002016	928.78299998119	1618024	1617123	200	application/octet-stream	Fetch
https://api.n.m28.io/endpoint/digdig-ffa/findEach/	h2	1339.3790000118	1652.5079999119	921	216	200	application/json	XHR
https://api.n.m28.io/endpoint/latency/findEach/	h2	1657.6229999773	1956.4049998298	1270	1323	200	application/json	XHR

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)
434.691	6.726
570.294	10.756
747.326	7.595
938.514	10.092
948.636	295.493
1244.174	78.594
1325.16	8.91
1344.997	10.109
1363.055	8.619
1382.084	9.191
1391.567	9.898
1401.597	10.756
1416.175	10.913
1432.691	8.204
1448.813	8.917
1465.718	9.939
1483.688	11.143
1498.787	10.147
1515.633	11.011
1532.648	11.212
1548.942	13.728
1565.614	9.644
1582.227	10.721
1598.85	11.945
1615.564	12.581
1632.242	12.318
1648.88	11.891
1670.251	12.146
1684.61	12.206
1698.847	11.116
1715.535	11.242
1732.184	10.333
1748.774	11.351
1765.542	10.34
1782.218	12.173
1798.813	12.404
1815.989	10.856
1832.193	11.135
1849.015	12.472
1865.631	10.319
1882.245	11.359
1898.808	11.36
1915.616	9.927
1932.303	11.522
1948.794	11.707
1967.283	11.121
1982.093	11.369
1998.79	12.38
2016.062	13.089
2032.369	12.173
2048.856	11.966
2065.427	10.375
2082.279	10.267
2098.859	11.205
2115.661	13.441
2132.081	12.381
2148.994	11.51
2165.535	13.13
2182.138	11.781
2198.919	10.706
2215.563	12.551
2232.218	10.4
2248.995	10.588
2265.5	15.693
2282.502	13.01
2299.897	11.191
2315.503	10.907
2332.158	11.884
2348.969	12.377
2365.422	12.927
2382.215	10.776
2399.026	10.525
2415.551	10.518
2432.128	10.856
2448.99	10.073
2465.524	11.414
2482.154	11.567
2498.845	11.842
2515.551	11.464
2532.165	10.2
2548.791	11.54
2565.402	9.618
2582.127	10.834
2598.821	10.5
2615.976	11.052
2632.243	10.548
2648.919	10.812
2665.659	11.103
2682.155	11.061
2698.951	9.973
2715.641	12.954
2732.17	10.291
2748.793	10.681
2765.49	8.648
2782.142	10.754
2798.949	14.266
2815.581	12.697
2832.274	13.958
2849.194	11.901
2867.616	12.954
2883.037	11.444
2898.822	11.928
2915.767	11.401
2932.216	10.689
2948.884	10.599
2966.512	10.377
2982.066	10.439
2998.917	10.913
3016.492	10.603
3032.102	11.576
3048.922	12.363
3065.88	10.948
3082.513	12.511
3100.125	12.867
3117.407	11.856
3135.393	11.72
3151.707	10.594
3168.03	10.128
3182.321	11.075
3198.795	9.29
3215.492	12.838
3232.396	11.196
3248.841	10.987
3266.037	11.702
3282.135	10.597
3298.889	10.611
3315.525	10.909
3332.307	10.783
3349.045	10.39
3365.517	10.266
3382.287	11.184
3399.188	12.028
3415.582	11.247
3432.11	12.468
3448.808	10.043
3465.438	10.778
3482.092	11.295
3498.699	9.989
3515.499	10.18
3532.397	10.56
3548.895	10.35
3565.52	10.657
3582.247	10.373
3599.027	11.274
3615.574	11.299
3632.122	11.525
3648.842	11.073
3665.404	10.875
3682.166	10.865
3698.813	10.556
3715.427	9.124
3732.049	11.015
3748.824	10.166
3765.499	9.2
3782.295	10.865
3800.03	11.303
3815.813	11.783
3832.643	10.392
3848.956	10.475
3865.505	11.776
3882.458	10.836
3898.832	10.813
3915.466	11.721
3932.225	10.509
3948.803	10.687
3965.473	11.363
3982.117	10.143
3998.809	9.498
4015.412	9.458
4032.066	10.544
4049.059	10.789
4065.377	10.578
4082.36	9.878
4098.839	11.723
4115.353	10.091
4132.389	8.606
4148.686	10.377
4165.382	9.211
4182.131	10.116
4198.711	9.611
4215.387	11.052
4232.153	8.77
4248.818	8.783
4265.423	9.934
4282.182	9.874

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.

Opportunities

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

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

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

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Digdig.io should consider minifying JS files.

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

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

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
https://static.digdig.io/a59c3d4102ded0d8fdea4e0a0c20851e8e084ac3/client.js	107110	74111

Show Details

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

Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.

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

Initial server response time was short — Root document took 360 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)
https://digdig.io/	355.563

Show Details

Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Digdig.io should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
http://digdig.io/	190
https://digdig.io/	0

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Digdig.io 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
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.

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

Diagnostics

Uses efficient cache policy on static assets — 1 resource found
Digdig.io 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)
https://static.digdig.io/a59c3d4102ded0d8fdea4e0a0c20851e8e084ac3/client.js	2678400000	107110

Show Details

Avoids an excessive DOM size — 22 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		22
Maximum DOM Depth	Google Chrome	5
Maximum Child Elements	body	8

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. Digdig.io 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.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)
https://digdig.io/	1514.178	3.551	1.311
https://static.digdig.io/a59c3d4102ded0d8fdea4e0a0c20851e8e084ac3/client.js	870.144	738.505	2.937
Unattributable	53.516	10.041	0.192

Show Details

Keep request counts low and transfer sizes small — 9 requests • 3,286 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	9	3364724
Other	5	3238979
Script	1	107110
Font	1	14853
Document	1	2543
Stylesheet	1	1239
Image	0	0
Media	0	0
Third-party	4	18283

Show Details

Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Third-Party	Transfer Size (Bytes)	Main-Thread Blocking Time (Ms)
SHOW DETAILS	16092	0

Show Details

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 — 1 element found
The element which was identified as the Largest Contentful Paint.

Element
Loading...

Show Details

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 — 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)
https://static.digdig.io/a59c3d4102ded0d8fdea4e0a0c20851e8e084ac3/client.js	741	148

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.

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.

Metrics

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

Other

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

Opportunities

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

URL	Transfer Size (Bytes)	Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Ubuntu:700	1239	230

Show Details

Diagnostics

Avoid enormous network payloads — Total size was 3,286 KiB
Large network payloads can cost users money and are linked to long load times.

URL	Transfer Size (Bytes)
https://static.digdig.io/a59c3d4102ded0d8fdea4e0a0c20851e8e084ac3/client.wasm	1618024
https://static.digdig.io/a59c3d4102ded0d8fdea4e0a0c20851e8e084ac3/client.wasm	1618014
https://static.digdig.io/a59c3d4102ded0d8fdea4e0a0c20851e8e084ac3/client.js	107110
https://fonts.gstatic.com/s/ubuntu/v15/4iCv6KVjbNBYlgoCxCvjsGyNPYZvgw.woff2	14853
https://digdig.io/	2543
https://api.n.m28.io/endpoint/latency/findEach/	1270
https://fonts.googleapis.com/css?family=Ubuntu:700	1239
https://api.n.m28.io/endpoint/digdig-ffa/findEach/	921
http://digdig.io/	750

Show Details

Minimize main-thread work — 2.4 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	1557.258
Script Evaluation	752.097
Other	102.123
Style & Layout	10.661
Garbage Collection	10.085
Script Parsing & Compilation	4.44
Parse HTML & CSS	2.238

Show Details

Opportunities

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

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
https://static.digdig.io/a59c3d4102ded0d8fdea4e0a0c20851e8e084ac3/client.wasm	1617123	876670
https://static.digdig.io/a59c3d4102ded0d8fdea4e0a0c20851e8e084ac3/client.js	106215	70919

Show Details

Diagnostics

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

URL	Potential Savings (Ms)
https://fonts.gstatic.com/s/ubuntu/v15/4iCv6KVjbNBYlgoCxCvjsGyNPYZvgw.woff2	2.9470000881702

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

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of digdig.io. 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 `[alt]` 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.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Digdig.io 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

Best practices

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

Failing Elements
meta

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 digdig.io should incorporate. This includes practices such as protecting pages with HTTPS.

Passing (16)
Failing (3)

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

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.

Avoids front-end JavaScript libraries with known security vulnerabilities
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.

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.

Audits

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.

Avoids Application Cache
Application cache is deprecated and is no longer recommended.

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

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

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

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

Audits

Does not use HTTPS — 1 insecure request 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://digdig.io/	Allowed

Show Details

Audits

Charset declaration is missing or occurs too late in the HTML
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

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

Source	Description
SHOW DETAILS	WebSocket connection to 'wss://fv.s.m28n.net/' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
SHOW DETAILS	WebSocket connection to 'wss://fx.s.m28n.net/' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED

Show Details

SEO

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

Passing (14)
Manual Checks (1)

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of digdig.io on mobile screens.

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.

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.

Progressive Web App

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

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.

Sets 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

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of digdig.io on mobile screens.

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

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

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

Progressive Web App

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

URL: https://digdig.io/

Updated: 12th August, 2021

2.33 seconds

First Contentful Paint (FCP)

62%

24%

14%

0.18 seconds

First Input Delay (FID)

67%

14%

19%

Simulate loading on mobile