epicgame.com

epicgame.com may not be SSL secured

Free website and domain report on epicgame.com

Last Updated: 18th October, 2023 Update Now
Overview

Snoop Summary for epicgame.com

This is a free and comprehensive report about epicgame.com. The domain epicgame.com is currently hosted on a server located in Australia with the IP address 103.224.182.249, where the local currency is AUD and English is the local language. Epicgame.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If epicgame.com was to be sold it would possibly be worth $769 USD (based on the daily revenue potential of the website over a 24 month period). Epicgame.com is somewhat popular with an estimated 365 daily unique visitors. This report was last updated 18th October, 2023.

About epicgame.com

Site Preview: epicgame.com epicgame.com
Title:
Description: See related links to what you are looking for.
Keywords and Tags: parked domain
Related Terms:
Fav Icon:
Age: Over 20 years old
Domain Created: 12th September, 2003
Domain Updated: 24th July, 2020
Domain Expires: 12th September, 2021
Review

Snoop Score

1/5

Valuation

$769 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,484,884
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: 365
Monthly Visitors: 11,109
Yearly Visitors: 133,225
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $32 USD
Yearly Revenue: $380 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: epicgame.com 12
Domain Name: epicgame 8
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 77
Performance 96
Accessibility 68
Best Practices 86
SEO 100
Progressive Web App 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://ww25.epicgame.com/
Updated: 30th September, 2020

3.33 seconds
First Contentful Paint (FCP)
17%
53%
30%

0.00 seconds
First Input Delay (FID)
97%
1%
2%

Simulate loading on desktop
96

Performance

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

Metrics

Speed Index — 1.0 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.2 s
The timing of the largest text or image that is painted.
Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 40 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 CPU Idle — 1.3 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 120 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive epicgame.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://epicgame.com/
0
352.98299975693
336
0
302
text/html
http://ww25.epicgame.com/?subid1=20201001-0522-1954-8d4a-8eaa762a1ec4
353.46999997273
485.79599987715
4447
4028
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
502.0339996554
529.57399981096
62418
176723
200
text/javascript
Script
http://ww25.epicgame.com/px.gif?ch=1&rn=2.0039859109055964
502.80099967495
597.0049998723
275
42
200
image/gif
Image
http://ww25.epicgame.com/px.gif?ch=2&rn=2.0039859109055964
503.09899961576
620.55299989879
275
42
200
image/gif
Image
http://ww25.epicgame.com/glp?r=&u=http%3A%2F%2Fww25.epicgame.com%2F&rw=800&rh=600&ww=1350&wh=940&subid1=20201001-0522-1954-8d4a-8eaa762a1ec4
703.79900000989
753.20499995723
10012
9668
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Open+Sans
756.91899983212
771.19899960235
1529
2470
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Quicksand
758.24099965394
772.16900000349
1491
1090
200
text/css
Stylesheet
http://ww25.epicgame.com/public/legacy/10352/resources/arrows-bg.jpg
769.32199997827
832.61799998581
96086
95846
200
image/jpeg
Image
http://ww25.epicgame.com/public/legacy/10352/resources/arrows-bg-ext.png
769.68899974599
811.87399988994
1379
1143
200
image/png
Image
https://www.google.com/dp/ads?max_radlink_len=60&r=m&cpp=0&client=dp-bodis30_3ph&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol119&hl=en&adsafe=low&type=3&swp=as-drid-2264520213939778&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300255%2C17300340%2C17300379%2C17300395%2C17300397&format=r7&num=0&output=afd_ads&domain_name=ww25.epicgame.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1601493740185&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=900&frm=0&uio=ff6fa6st24sa11lt30sl1sr1-&cont=Sb&csize=w400h0&inames=master-1&jsv=71661&rurl=http%3A%2F%2Fww25.epicgame.com%2F%3Fsubid1%3D20201001-0522-1954-8d4a-8eaa762a1ec4
781.72599989921
870.64299965277
8239
10498
200
text/html
Document
http://ads.pro-market.net/ads/scripts/site-110930.js
783.66799978539
911.27899987623
1085
1404
200
application/x-javascript
Script
https://fonts.gstatic.com/s/quicksand/v21/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xDwxUD2GFw.woff
790.00099981204
792.63099981472
17716
17096
200
font/woff
Font
https://www.google.com/adsense/domains/caf.js
892.93799968436
912.79299976304
64466
176620
200
text/javascript
Script
https://pbid.pro-market.net/engine?site=110930;size=1x1;e=0;category=x4tx%20e8ql89mf%203g3;kw=fx94xa5m%204nm;rnd=(1601493740340)
925.52199959755
963.01299985498
1000
370
200
text/html
Document
https://fonts.googleapis.com/css?family=open%20sans%7Copen%20sans
957.36499968916
984.70599995926
0
0
-1
Stylesheet
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6ImVwaWNnYW1lLmNvbSIsInNlcnZlciI6OTEsInRlcm1zIjpbXSwiVVJMIjoiaHR0cDpcL1wvd3cyNS5lcGljZ2FtZS5jb21cLyIsInJlZmVycmVyIjoiIiwic3ViSWRzIjpbIjIwMjAxMDAxLTA1MjItMTk1NC04ZDRhLThlYWE3NjJhMWVjNCJdLCJkdyI6MTM1MCwiZGgiOjk0MCwicnciOjgwMCwicmgiOjYwMH0&t=1601493740&abp=0
966.01299988106
1043.7099998817
356
0
200
text/plain
XHR
https://ads.pro-market.net/ads/scripts/dda4-1-7a.js
983.44999970868
1139.5799997263
8970
29271
200
application/x-javascript
Script
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
998.34599997848
1001.5699998476
6585
13716
200
text/javascript
Script
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)
519.469
10.008
573.992
10.97
784.727
29.234
904.148
9.485
913.68
7.374
942.803
11.166
965.961
26.634
1002.112
6.611
1015.644
9.936
1033.203
124.06
1171.285
7.292
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Epicgame.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Epicgame.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Epicgame.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Epicgame.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Epicgame.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Epicgame.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 53 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://ww25.epicgame.com/public/legacy/10352/resources/arrows-bg.jpg
95846
54366
Enable text compression — Potential savings of 8 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://ww25.epicgame.com/glp?r=&u=http%3A%2F%2Fww25.epicgame.com%2F&rw=800&rh=600&ww=1350&wh=940&subid1=20201001-0522-1954-8d4a-8eaa762a1ec4
9668
5549
http://ww25.epicgame.com/?subid1=20201001-0522-1954-8d4a-8eaa762a1ec4
4028
2208
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 130 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://ww25.epicgame.com/?subid1=20201001-0522-1954-8d4a-8eaa762a1ec4
133.322
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Epicgame.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://epicgame.com/
190
http://ww25.epicgame.com/?subid1=20201001-0522-1954-8d4a-8eaa762a1ec4
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Epicgame.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 20 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://ww25.epicgame.com/glp?r=&u=http%3A%2F%2Fww25.epicgame.com%2F&rw=800&rh=600&ww=1350&wh=940&subid1=20201001-0522-1954-8d4a-8eaa762a1ec4
20234

Diagnostics

Avoids enormous network payloads — Total size was 280 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://ww25.epicgame.com/public/legacy/10352/resources/arrows-bg.jpg
96086
https://www.google.com/adsense/domains/caf.js
64466
http://www.google.com/adsense/domains/caf.js
62418
https://fonts.gstatic.com/s/quicksand/v21/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xDwxUD2GFw.woff
17716
http://ww25.epicgame.com/glp?r=&u=http%3A%2F%2Fww25.epicgame.com%2F&rw=800&rh=600&ww=1350&wh=940&subid1=20201001-0522-1954-8d4a-8eaa762a1ec4
10012
https://ads.pro-market.net/ads/scripts/dda4-1-7a.js
8970
https://www.google.com/dp/ads?max_radlink_len=60&r=m&cpp=0&client=dp-bodis30_3ph&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol119&hl=en&adsafe=low&type=3&swp=as-drid-2264520213939778&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300255%2C17300340%2C17300379%2C17300395%2C17300397&format=r7&num=0&output=afd_ads&domain_name=ww25.epicgame.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1601493740185&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=900&frm=0&uio=ff6fa6st24sa11lt30sl1sr1-&cont=Sb&csize=w400h0&inames=master-1&jsv=71661&rurl=http%3A%2F%2Fww25.epicgame.com%2F%3Fsubid1%3D20201001-0522-1954-8d4a-8eaa762a1ec4
8239
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
6585
http://ww25.epicgame.com/?subid1=20201001-0522-1954-8d4a-8eaa762a1ec4
4447
https://fonts.googleapis.com/css?family=Open+Sans
1529
Avoids an excessive DOM size — 16 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
16
Maximum DOM Depth
7
Maximum Child Elements
6
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. Epicgame.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.2 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://www.google.com/adsense/domains/caf.js
159.688
149.001
5.894
Minimizes main-thread work — 0.3 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)
Script Evaluation
213.995
Other
52.874
Script Parsing & Compilation
19.656
Style & Layout
17.688
Rendering
13.769
Parse HTML & CSS
4.868
Garbage Collection
4.668
Keep request counts low and transfer sizes small — 19 requests • 280 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
19
286665
Script
6
153536
Image
4
98015
Font
1
17716
Document
3
13686
Stylesheet
3
3020
Other
2
692
Media
0
0
Third-party
12
173855
Minimize third-party usage — Third-party code blocked the main thread for 60 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)
141708
60.944
20736
0
11055
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
1.3654123107491E-5
5.6156431126298E-6
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
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://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
1100
124
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

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

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

Other

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

Opportunities

Remove unused JavaScript — Potential savings of 76 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://www.google.com/adsense/domains/caf.js
62418
40673
https://www.google.com/adsense/domains/caf.js
64466
36670

Diagnostics

Serve static assets with an efficient cache policy — 5 resources found
Epicgame.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://ww25.epicgame.com/public/legacy/10352/resources/arrows-bg.jpg
0
96086
http://ww25.epicgame.com/public/legacy/10352/resources/arrows-bg-ext.png
0
1379
http://ww25.epicgame.com/px.gif?ch=1&rn=2.0039859109055964
0
275
http://ww25.epicgame.com/px.gif?ch=2&rn=2.0039859109055964
0
275
http://ads.pro-market.net/ads/scripts/site-110930.js
86400000
1085

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/quicksand/v21/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xDwxUD2GFw.woff
2.6300000026822
Avoid `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.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 199
68

Accessibility

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

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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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"]`
Epicgame.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Epicgame.com may provide relevant information that dialogue cannot, by using audio descriptions.

Navigation

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

Contrast

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

Names and labels

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

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

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

Best Practices

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

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.

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

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.

Audits

Does not use HTTPS — 10 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
http://epicgame.com/
http://ww25.epicgame.com/?subid1=20201001-0522-1954-8d4a-8eaa762a1ec4
http://www.google.com/adsense/domains/caf.js
http://ww25.epicgame.com/px.gif?ch=1&rn=2.0039859109055964
http://ww25.epicgame.com/px.gif?ch=2&rn=2.0039859109055964
http://ww25.epicgame.com/glp?r=&u=http%3A%2F%2Fww25.epicgame.com%2F&rw=800&rh=600&ww=1350&wh=940&subid1=20201001-0522-1954-8d4a-8eaa762a1ec4
http://ww25.epicgame.com/public/legacy/10352/resources/arrows-bg.jpg
http://ww25.epicgame.com/public/legacy/10352/resources/arrows-bg-ext.png
http://ads.pro-market.net/ads/scripts/site-110930.js
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6ImVwaWNnYW1lLmNvbSIsInNlcnZlciI6OTEsInRlcm1zIjpbXSwiVVJMIjoiaHR0cDpcL1wvd3cyNS5lcGljZ2FtZS5jb21cLyIsInJlZmVycmVyIjoiIiwic3ViSWRzIjpbIjIwMjAxMDAxLTA1MjItMTk1NC04ZDRhLThlYWE3NjJhMWVjNCJdLCJkdyI6MTM1MCwiZGgiOjk0MCwicnciOjgwMCwicmgiOjYwMH0&t=1601493740&abp=0

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.
URL Description
https://www.google.com/dp/ads?max_radlink_len=60&r=m&cpp=0&client=dp-bodis30_3ph&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol119&hl=en&adsafe=low&type=3&swp=as-drid-2264520213939778&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300255%2C17300340%2C17300379%2C17300395%2C17300397&format=r7&num=0&output=afd_ads&domain_name=ww25.epicgame.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1601493740185&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=900&frm=0&uio=ff6fa6st24sa11lt30sl1sr1-&cont=Sb&csize=w400h0&inames=master-1&jsv=71661&rurl=http%3A%2F%2Fww25.epicgame.com%2F%3Fsubid1%3D20201001-0522-1954-8d4a-8eaa762a1ec4#master-1
Refused to apply style from 'https://fonts.googleapis.com/css?family=open%20sans%7Copen%20sans' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
https://www.google.com/dp/ads?max_radlink_len=60&r=m&cpp=0&client=dp-bodis30_3ph&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol119&hl=en&adsafe=low&type=3&swp=as-drid-2264520213939778&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300255%2C17300340%2C17300379%2C17300395%2C17300397&format=r7&num=0&output=afd_ads&domain_name=ww25.epicgame.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1601493740185&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=900&frm=0&uio=ff6fa6st24sa11lt30sl1sr1-&cont=Sb&csize=w400h0&inames=master-1&jsv=71661&rurl=http%3A%2F%2Fww25.epicgame.com%2F%3Fsubid1%3D20201001-0522-1954-8d4a-8eaa762a1ec4#master-1
Refused to apply style from 'https://fonts.googleapis.com/css?family=open%20sans%7Copen%20sans' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
100

SEO

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

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

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
33

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 epicgame.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

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 epicgame.com on mobile screens.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 10 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
http://epicgame.com/
http://ww25.epicgame.com/?subid1=20201001-0522-1954-8d4a-8eaa762a1ec4
http://www.google.com/adsense/domains/caf.js
http://ww25.epicgame.com/px.gif?ch=1&rn=2.0039859109055964
http://ww25.epicgame.com/px.gif?ch=2&rn=2.0039859109055964
http://ww25.epicgame.com/glp?r=&u=http%3A%2F%2Fww25.epicgame.com%2F&rw=800&rh=600&ww=1350&wh=940&subid1=20201001-0522-1954-8d4a-8eaa762a1ec4
http://ww25.epicgame.com/public/legacy/10352/resources/arrows-bg.jpg
http://ww25.epicgame.com/public/legacy/10352/resources/arrows-bg-ext.png
http://ads.pro-market.net/ads/scripts/site-110930.js
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6ImVwaWNnYW1lLmNvbSIsInNlcnZlciI6OTEsInRlcm1zIjpbXSwiVVJMIjoiaHR0cDpcL1wvd3cyNS5lcGljZ2FtZS5jb21cLyIsInJlZmVycmVyIjoiIiwic3ViSWRzIjpbIjIwMjAxMDAxLTA1MjItMTk1NC04ZDRhLThlYWE3NjJhMWVjNCJdLCJkdyI6MTM1MCwiZGgiOjk0MCwicnciOjgwMCwicmgiOjYwMH0&t=1601493740&abp=0
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.
Web app manifest does not 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.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 provide fallback content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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) 76
Performance 81
Accessibility 68
Best Practices 93
SEO 100
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://ww25.epicgame.com/
Updated: 30th September, 2020

3.25 seconds
First Contentful Paint (FCP)
25%
46%
29%

0.02 seconds
First Input Delay (FID)
95%
4%
1%

Simulate loading on mobile
81

Performance

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

Metrics

First Contentful Paint — 1.7 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 3.0 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0.097
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First Meaningful Paint — 1.9 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 Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://epicgame.com/
0
373.27100010589
336
0
302
text/html
http://ww25.epicgame.com/?subid1=20201001-0522-318b-a51c-bad5ae011090
373.97100031376
397.03400013968
4447
4028
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
415.47400038689
440.46400021762
62399
176677
200
text/javascript
Script
http://ww25.epicgame.com/px.gif?ch=1&rn=8.787628389841458
417.90500003844
442.3919999972
275
42
200
image/gif
Image
http://ww25.epicgame.com/px.gif?ch=2&rn=8.787628389841458
418.10200037435
460.36000037566
275
42
200
image/gif
Image
http://ww25.epicgame.com/glp?r=&u=http%3A%2F%2Fww25.epicgame.com%2F&rw=360&rh=640&ww=360&wh=640&subid1=20201001-0522-318b-a51c-bad5ae011090
519.38900025561
568.52299999446
8641
8297
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Quicksand
574.18800005689
588.26300036162
1512
1089
200
text/css
Stylesheet
https://www.google.com/dp/ads?max_radlink_len=60&r=m&cpp=0&client=dp-bodis30_3ph&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol119&hl=en&adsafe=low&type=3&swp=as-drid-2264520213939778&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300339&format=r5&num=0&output=afd_ads&domain_name=ww25.epicgame.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1601493751475&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=79&frm=0&uio=ff6fa6st24sa11lt48sl1sr1-&cont=Sb&csize=w360h0&inames=master-1&jsv=71661&rurl=http%3A%2F%2Fww25.epicgame.com%2F%3Fsubid1%3D20201001-0522-318b-a51c-bad5ae011090
610.04800023511
706.3939999789
8174
10207
200
text/html
Document
http://ads.pro-market.net/ads/scripts/site-110930.js
615.87500013411
637.36800011247
1085
1404
200
application/x-javascript
Script
https://pbid.pro-market.net/engine?site=110930;size=1x1;e=0;category=x4tx%20e8ql89mf%203g3;kw=fx94xa5m%204nm;rnd=(1601493751538)
656.30000038072
697.36500037834
1033
370
200
text/html
Document
https://ads.pro-market.net/ads/scripts/dda4-1-7a.js
727.74300025776
813.6180001311
8970
29271
200
application/x-javascript
Script
https://www.google.com/adsense/domains/caf.js
729.27600005642
756.83700013906
63731
176620
200
text/javascript
Script
https://afs.googleusercontent.com/dp-bodis/arrow-blue-2.png
807.31000006199
810.71500014514
818
260
200
image/png
Image
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6ImVwaWNnYW1lLmNvbSIsInNlcnZlciI6OTEsInRlcm1zIjpbXSwiVVJMIjoiaHR0cDpcL1wvd3cyNS5lcGljZ2FtZS5jb21cLyIsInJlZmVycmVyIjoiIiwic3ViSWRzIjpbIjIwMjAxMDAxLTA1MjItMzE4Yi1hNTFjLWJhZDVhZTAxMTA5MCJdLCJkdyI6MzYwLCJkaCI6NjQwLCJydyI6MzYwLCJyaCI6NjQwfQ&t=1601493751&abp=0
811.40900030732
926.20600014925
356
0
200
text/plain
XHR
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=3aqtmb39owh8&aqid=99p0X5-JIcSL6toP9tqUyAE&pbt=bo&adbn=master-1&uio=|24|||||%2F%2Fafs.googleusercontent.com%2Fdp-bodis%2Farrow-blue-2.png|24||||10||||||||%23777777|transparent||||||%23cccccc||||||trebuchet%20ms%2Carial|trebuchet%20ms%2Carial||16||||24||||||48||_blank|||||||||%23ffffff|true||true|true||||Sb||relatedsearch|||360|true|
841.93300036713
861.15800030529
545
0
204
text/html
Image
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
847.04999998212
851.02300019935
6586
13716
200
text/javascript
Script
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=ncr6af224lm&aqid=99p0X5-JIcSL6toP9tqUyAE&pbt=bs&adbx=0&adby=50&adbh=413&adbw=360&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=7166121592703734751&csadii=27&csadr=234&pblt=1&lle=0&llm=0&ifv=1
2340.7420003787
0
0
-1
Image
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)
440.445
10.552
452.408
5.648
496.144
11.956
610.178
45.57
678.648
15.295
740.054
9.294
750.467
9.852
809.927
38.369
858.19
17.392
876.625
5.051
886.101
8.759
901.258
157.411
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
First Contentful Paint (3G) — 3395.5 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Epicgame.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Epicgame.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Epicgame.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Epicgame.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Epicgame.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Epicgame.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
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression — Potential savings of 7 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://ww25.epicgame.com/glp?r=&u=http%3A%2F%2Fww25.epicgame.com%2F&rw=360&rh=640&ww=360&wh=640&subid1=20201001-0522-318b-a51c-bad5ae011090
8297
4542
http://ww25.epicgame.com/?subid1=20201001-0522-318b-a51c-bad5ae011090
4028
2208
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 20 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://ww25.epicgame.com/?subid1=20201001-0522-318b-a51c-bad5ae011090
24.059
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Epicgame.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://epicgame.com/
630
http://ww25.epicgame.com/?subid1=20201001-0522-318b-a51c-bad5ae011090
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Epicgame.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 20 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://ww25.epicgame.com/glp?r=&u=http%3A%2F%2Fww25.epicgame.com%2F&rw=360&rh=640&ww=360&wh=640&subid1=20201001-0522-318b-a51c-bad5ae011090
20349

Diagnostics

Avoids enormous network payloads — Total size was 165 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
63731
http://www.google.com/adsense/domains/caf.js
62399
https://ads.pro-market.net/ads/scripts/dda4-1-7a.js
8970
http://ww25.epicgame.com/glp?r=&u=http%3A%2F%2Fww25.epicgame.com%2F&rw=360&rh=640&ww=360&wh=640&subid1=20201001-0522-318b-a51c-bad5ae011090
8641
https://www.google.com/dp/ads?max_radlink_len=60&r=m&cpp=0&client=dp-bodis30_3ph&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol119&hl=en&adsafe=low&type=3&swp=as-drid-2264520213939778&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300339&format=r5&num=0&output=afd_ads&domain_name=ww25.epicgame.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1601493751475&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=79&frm=0&uio=ff6fa6st24sa11lt48sl1sr1-&cont=Sb&csize=w360h0&inames=master-1&jsv=71661&rurl=http%3A%2F%2Fww25.epicgame.com%2F%3Fsubid1%3D20201001-0522-318b-a51c-bad5ae011090
8174
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
6586
http://ww25.epicgame.com/?subid1=20201001-0522-318b-a51c-bad5ae011090
4447
https://fonts.googleapis.com/css?family=Quicksand
1512
http://ads.pro-market.net/ads/scripts/site-110930.js
1085
https://pbid.pro-market.net/engine?site=110930;size=1x1;e=0;category=x4tx%20e8ql89mf%203g3;kw=fx94xa5m%204nm;rnd=(1601493751538)
1033
Uses efficient cache policy on static assets — 4 resources found
Epicgame.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://ww25.epicgame.com/px.gif?ch=1&rn=8.787628389841458
0
275
http://ww25.epicgame.com/px.gif?ch=2&rn=8.787628389841458
0
275
https://afs.googleusercontent.com/dp-bodis/arrow-blue-2.png
82800000
818
http://ads.pro-market.net/ads/scripts/site-110930.js
86400000
1085
Avoids an excessive DOM size — 18 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
18
Maximum DOM Depth
6
Maximum Child Elements
6
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. Epicgame.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 — 1.2 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://www.google.com/adsense/domains/caf.js
844.132
787.268
28.396
http://ww25.epicgame.com/glp?r=&u=http%3A%2F%2Fww25.epicgame.com%2F&rw=360&rh=640&ww=360&wh=640&subid1=20201001-0522-318b-a51c-bad5ae011090
184.376
134.08
4.084
Unattributable
134.88
10.612
0.852
http://ww25.epicgame.com/?subid1=20201001-0522-318b-a51c-bad5ae011090
131.864
37.436
7.752
http://www.google.com/adsense/domains/caf.js
83.672
51.092
18.244
http://ads.pro-market.net/ads/scripts/site-110930.js
60.972
49.3
8.46
https://www.google.com/dp/ads?max_radlink_len=60&r=m&cpp=0&client=dp-bodis30_3ph&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol119&hl=en&adsafe=low&type=3&swp=as-drid-2264520213939778&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300339&format=r5&num=0&output=afd_ads&domain_name=ww25.epicgame.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1601493751475&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=79&frm=0&uio=ff6fa6st24sa11lt48sl1sr1-&cont=Sb&csize=w360h0&inames=master-1&jsv=71661&rurl=http%3A%2F%2Fww25.epicgame.com%2F%3Fsubid1%3D20201001-0522-318b-a51c-bad5ae011090
57.968
12.172
6.976
Minimizes main-thread work — 1.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)
Script Evaluation
1142.664
Other
240.004
Script Parsing & Compilation
96.072
Style & Layout
87.332
Rendering
35.704
Parse HTML & CSS
23
Garbage Collection
16.676
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 — 17 requests • 165 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
17
169183
Script
6
151412
Document
3
13654
Image
5
1913
Stylesheet
1
1512
Other
2
692
Media
0
0
Font
0
0
Third-party
12
155209
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.09678760415669
9.2708433100278E-6
Avoid long main-thread tasks — 4 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)
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
4560
630
https://www.google.com/adsense/domains/caf.js
4200
153
http://ww25.epicgame.com/glp?r=&u=http%3A%2F%2Fww25.epicgame.com%2F&rw=360&rh=640&ww=360&wh=640&subid1=20201001-0522-318b-a51c-bad5ae011090
2838
91
http://ads.pro-market.net/ads/scripts/site-110930.js
2430
61
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

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

Largest Contentful Paint — 3.1 s
The timing of the largest text or image that is painted.
Time to Interactive — 4.9 s
The time taken for the page to become fully interactive.
Total Blocking Time — 450 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).

Other

First CPU Idle — 4.6 s
The time taken for the page's main thread to be quiet enough to handle input.

Opportunities

Remove unused JavaScript — Potential savings of 74 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://www.google.com/adsense/domains/caf.js
62399
39964
https://www.google.com/adsense/domains/caf.js
63731
36133

Other

Max Potential First Input Delay — 630 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 130 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive epicgame.com as laggy when the latency is higher than 0.05 seconds.

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 580 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)
141435
578.672
11088
0
1512
0
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 135
Avoid `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.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 199
68

Accessibility

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

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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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"]`
Epicgame.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Epicgame.com may provide relevant information that dialogue cannot, by using audio descriptions.

Navigation

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

Contrast

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

Names and labels

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

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

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

Best Practices

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

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.

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

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

Audits

Does not use HTTPS — 8 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
http://epicgame.com/
http://ww25.epicgame.com/?subid1=20201001-0522-318b-a51c-bad5ae011090
http://www.google.com/adsense/domains/caf.js
http://ww25.epicgame.com/px.gif?ch=1&rn=8.787628389841458
http://ww25.epicgame.com/px.gif?ch=2&rn=8.787628389841458
http://ww25.epicgame.com/glp?r=&u=http%3A%2F%2Fww25.epicgame.com%2F&rw=360&rh=640&ww=360&wh=640&subid1=20201001-0522-318b-a51c-bad5ae011090
http://ads.pro-market.net/ads/scripts/site-110930.js
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6ImVwaWNnYW1lLmNvbSIsInNlcnZlciI6OTEsInRlcm1zIjpbXSwiVVJMIjoiaHR0cDpcL1wvd3cyNS5lcGljZ2FtZS5jb21cLyIsInJlZmVycmVyIjoiIiwic3ViSWRzIjpbIjIwMjAxMDAxLTA1MjItMzE4Yi1hNTFjLWJhZDVhZTAxMTA5MCJdLCJkdyI6MzYwLCJkaCI6NjQwLCJydyI6MzYwLCJyaCI6NjQwfQ&t=1601493751&abp=0
100

SEO

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

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 epicgame.com on mobile screens.
Document uses legible font sizes — 85.42% legible text
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.
Source Selector % of Page Text Font Size
.amo
14.58%
11px
85.42%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
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.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
36

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 epicgame.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

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 epicgame.com on mobile screens.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 8 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
http://epicgame.com/
http://ww25.epicgame.com/?subid1=20201001-0522-318b-a51c-bad5ae011090
http://www.google.com/adsense/domains/caf.js
http://ww25.epicgame.com/px.gif?ch=1&rn=8.787628389841458
http://ww25.epicgame.com/px.gif?ch=2&rn=8.787628389841458
http://ww25.epicgame.com/glp?r=&u=http%3A%2F%2Fww25.epicgame.com%2F&rw=360&rh=640&ww=360&wh=640&subid1=20201001-0522-318b-a51c-bad5ae011090
http://ads.pro-market.net/ads/scripts/site-110930.js
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6ImVwaWNnYW1lLmNvbSIsInNlcnZlciI6OTEsInRlcm1zIjpbXSwiVVJMIjoiaHR0cDpcL1wvd3cyNS5lcGljZ2FtZS5jb21cLyIsInJlZmVycmVyIjoiIiwic3ViSWRzIjpbIjIwMjAxMDAxLTA1MjItMzE4Yi1hNTFjLWJhZDVhZTAxMTA5MCJdLCJkdyI6MzYwLCJkaCI6NjQwLCJydyI6MzYwLCJyaCI6NjQwfQ&t=1601493751&abp=0
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.
Web app manifest does not 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.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 provide fallback content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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.
Hosting

Server Location

Server IP Address: 103.224.182.249
Continent: Oceania
Country: Australia
Australia Flag
Region:
City:
Longitude: 143.2104
Latitude: -33.494
Currencies: AUD
Languages: English

Web Hosting Provider

Name IP Address
Trellian Pty. Limited
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Sea Wasp, LLC 104.143.9.90
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating: 0.1/5
WOT Trustworthiness: 1/100
WOT Child Safety: 1/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: openresty
Date: 30th September, 2020
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBANDrp2lz7AOmADaN8tA50LsWcjLFyQFcb/P2Txc58oYOeILb3vBw7J6f4pamkAQVSQuqYsKx3YzdUHCvbVZvFUsCAwEAAQ==_VYR3Wy8Qy+P8YtfG1FN8RFc2El0vl3WPEh2+D/w2EwpQstM+M69D7oMEzQFWE1mFowokFB3DhgiJStb4PQv9aA==

Whois Lookup

Created: 12th September, 2003
Changed: 24th July, 2020
Expires: 12th September, 2021
Registrar: Sea Wasp, LLC
Status: clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
renewPeriod
Nameservers: ns1.above.com
ns2.above.com
Owner Name: Namase Patel
Owner Organization: Mumbai Domains
Owner Street: 1415, Mahatma Gandhi Rd, Mhada
Owner Post Code: 400 066
Owner City: Mumbai
Owner State: Maharashtra
Owner Country: IN
Owner Phone: +91.9820133717
Owner Email: namasepatel@yahoo.co.in
Admin Name: Namase Patel
Admin Organization: Mumbai Domains
Admin Street: 1415, Mahatma Gandhi Rd, Mhada
Admin Post Code: 400 066
Admin City: Mumbai
Admin State: Maharashtra
Admin Country: IN
Admin Phone: +91.9820133717
Admin Email: namasepatel@yahoo.co.in
Tech Name: Namase Patel
Tech Organization: Mumbai Domains
Tech Street: 1415, Mahatma Gandhi Rd, Mhada
Tech Post Code: 400 066
Tech City: Mumbai
Tech State: Maharashtra
Tech Country: IN
Tech Phone: +91.9820133717
Tech Email: namasepatel@yahoo.co.in
Full Whois:
Domain Name: EPICGAME.COM
Registry Domain ID: 103456234_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.fabulous.com
Registrar URL: http://www.fabulous.com
Updated Date: 2020-07-24T14:38:35Z
Creation Date: 2003-09-12T11:54:16Z
Registrar Registration Expiration Date: 2021-09-12T11:54:16Z
Registrar: Sea Wasp, LLC
Sponsoring Registrar IANA ID: 411
Registrar Abuse Contact Email: abuse@fabulous.com
Registrar Abuse Contact Phone: +1.5045078209
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: renewPeriod (https://www.icann.org/epp#renewPeriod)
Registry Registrant ID: Not Available From Registry
Registrant Name: Namase Patel
Registrant Organization: Mumbai Domains
Registrant Street: 1415, Mahatma Gandhi Rd, Mhada
Registrant City: Mumbai
Registrant State/Province: Maharashtra
Registrant Postal Code: 400 066
Registrant Country: IN
Registrant Phone: +91.9820133717
Registrant Phone Ext:
Registrant Fax: +91.9999999
Registrant Fax Ext:
Registrant Email: namasepatel@yahoo.co.in
Registry Admin ID: Not Available From Registry
Admin Name: Namase Patel
Admin Organization: Mumbai Domains
Admin Street: 1415, Mahatma Gandhi Rd, Mhada
Admin City: Mumbai
Admin State/Province: Maharashtra
Admin Postal Code: 400 066
Admin Country: IN
Admin Phone: +91.9820133717
Admin Phone Ext:
Admin Fax: +91.9999999
Admin Fax Ext:
Admin Email: namasepatel@yahoo.co.in
Registry Tech ID: Not Available From Registry
Tech Name: Namase Patel
Tech Organization: Mumbai Domains
Tech Street: 1415, Mahatma Gandhi Rd, Mhada
Tech City: Mumbai
Tech State/Province: Maharashtra
Tech Postal Code: 400 066
Tech Country: IN
Tech Phone: +91.9820133717
Tech Phone Ext:
Tech Fax: +91.9999999
Tech Fax Ext:
Tech Email: namasepatel@yahoo.co.in
Name Server: ns1.above.com
Name Server: ns2.above.com
URL of the ICANN WHOIS Data Problem Reporting System
http://wdprs.internic.net
>>> Last update of WHOIS database: 2020-09-30T09:22:17Z <<<
For more information on Whois status codes,
please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en.


The compilation, repackaging, dissemination, or other use of this WHOIS
data is expressly prohibited without the prior written consent of
Sea Wasp, LLC.

Sea Wasp reserves the right to terminate your access to its WHOIS
database in its sole discretion, including without limitation, for
excessive querying of the database or for failure to otherwise abide by
this policy.

Sea Wasp, LLC reserves the right to modify these terms at any time.

NOTE: THE WHOIS DATABASE IS A CONTACT DATABASE ONLY.
LACK OF A DOMAIN RECORD DOES NOT SIGNIFY DOMAIN AVAILABILITY.

Nameservers

Name IP Address
ns1.above.com 103.224.182.9
ns2.above.com 103.224.182.10
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$10 USD 1/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
$201 USD 1/5
$241 USD 1/5
0/5