fortnite.com

fortnite.com is SSL secured

Free website and domain report on fortnite.com

Last Updated: 21st August, 2024 Update Now
Overview

Snoop Summary for fortnite.com

This is a free and comprehensive report about fortnite.com. Our records indicate that fortnite.com is owned/operated by DNStination Inc.. Fortnite.com is expected to earn an estimated $16 USD per day from advertising revenue. The sale of fortnite.com would possibly be worth $11,551 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Fortnite.com receives an estimated 5,547 unique visitors every day - a huge amount of traffic! This report was last updated 21st August, 2024.

About fortnite.com

Site Preview: fortnite.com fortnite.com
Title: Just a moment...
Description:
Keywords and Tags: durr burger onesie, epic games season 9 recap, fortnite retail row, fortnite season 9 recap, games, invitational, onesie fortnite, popular, season 8 recap, season 9 recap, season 9 recap video, seasonrecap fortnite com season 9
Related Terms: fortnite 3d, fortnite db, fortnite db v2, fortnite earnings, fortnite lego, fortnite marshmello, fortnite rankings, is fortnite ending, marshmello fortnite, now.gg fortnite
Fav Icon:
Age: Over 14 years old
Domain Created: 26th May, 2010
Domain Updated: 19th October, 2023
Domain Expires: 20th November, 2025
Review

Snoop Score

3/5 (Great!)

Valuation

$11,551 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 97,971
Alexa Reach:
SEMrush Rank (US): 371,005
SEMrush Authority Score: 56
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 2,999 0
Traffic: 3,343 0
Cost: $427 USD $0 USD
Traffic

Visitors

Daily Visitors: 5,547
Monthly Visitors: 168,833
Yearly Visitors: 2,024,655
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $16 USD
Monthly Revenue: $481 USD
Yearly Revenue: $5,770 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 100,346
Referring Domains: 3,626
Referring IPs: 4,373
Fortnite.com has 100,346 backlinks according to SEMrush. 85% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve fortnite.com's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of fortnite.com's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://dropnite.com/map.php?id=481
Target: https://fortnite.com/fn/9760-0331-8032

2
Source: https://dropnite.com/author.php?map_author=INXCOGNITO
Target: https://fortnite.com/fn/1855-7601-3275

3
Source: https://dropnite.com/map.php?id=908
Target: https://fortnite.com/fn/5706-0887-1146

4
Source: https://dropnite.com/map.php?id=6270
Target: https://fortnite.com/fn/7462-5963-0869

5
Source: https://dropnite.com/map.php?id=1055
Target: https://fortnite.com/fn/3809-0635-1092

Top Ranking Keywords (US)

1
Keyword: season 9 recap
Ranked Page: https://seasonrecap.fortnite.com/

2
Keyword: durr burger onesie
Ranked Page: https://merch-eu.fortnite.com/products/durrr-burger-onesie

3
Keyword: fortnite season 9 recap
Ranked Page: https://seasonrecap.fortnite.com/

4
Keyword: onesie fortnite
Ranked Page: https://merch-eu.fortnite.com/products/durrr-burger-onesie

5
Keyword: invitational
Ranked Page: https://www.fortnite.com/fortnite/competitive/en-US/news/fncs-invitational-official-rules

Domain Analysis

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

Page Speed Analysis

Average Load Time: 1.77 seconds
Load Time Comparison: Faster than 50% of sites

PageSpeed Insights

Avg. (All Categories) 66
Performance 36
Accessibility 79
Best Practices 87
SEO 92
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.epicgames.com/fortnite/en-US/home
Updated: 6th September, 2021

2.56 seconds
First Contentful Paint (FCP)
56%
26%
18%

0.01 seconds
First Input Delay (FID)
96%
2%
2%

Simulate loading on desktop
36

Performance

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

Opportunities

Defer offscreen images — Potential savings of 249 KiB
Time to Interactive can be slowed down by resources on the page. Fortnite.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn2.unrealengine.com/carousel2-3840x2138-718d0721e284.jpg
258345
239208
https://static-assets-prod.epicgames.com/fortnite/static/webpack/ef532e79e05e2d24a0f6332068f3a61b.gif
15660
15660
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Fortnite.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Fortnite.com should consider minifying JS files.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
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 300 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://www.epicgames.com/fortnite/en-US/home
298.147
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Fortnite.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 18 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)
https://tracking.epicgames.com/tracking.js
8300
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
5138
https://static-assets-prod.epicgames.com/fortnite/static/vendor/assets/js/es5-fortnite.js
4592
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids an excessive DOM size — 392 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
392
Maximum DOM Depth
17
Maximum Child Elements
12
Avoid chaining critical requests — 12 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Fortnite.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.0 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://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
942.373
735.414
67.528
https://static-assets-prod.epicgames.com/fortnite/static/vendor/TweenMax-1.19.0.min.js
444.34
26.109
1.874
https://www.epicgames.com/fortnite/en-US/home
202.926
5.8
13.251
Unattributable
118.229
3.764
0.231
https://static-assets-prod.epicgames.com/fortnite/static/webpack/polyfill.fortnite-site.1ab6b17ed82671772813.js
60.627
57.991
2.474
https://static-assets-prod.epicgames.com/fortnite/static/vendor/assets/js/es5-fortnite.js
50.141
40.652
5.962
Minimizes main-thread work — 1.9 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
891.429
Rendering
337.825
Other
271.445
Style & Layout
166.726
Parse HTML & CSS
107.276
Script Parsing & Compilation
94.077
Garbage Collection
30.85
Keep request counts low and transfer sizes small — 41 requests • 6,687 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
41
6847196
Image
22
4908953
Script
6
1191029
Font
5
391755
Stylesheet
2
249808
Document
1
88784
Other
5
16867
Media
0
0
Third-party
22
4892695
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.86869565217391
0.075985198889917
0.018042192215364
0.00061687980179041
0.00026117894833868
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 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://static-assets-prod.epicgames.com/fortnite/static/webpack/polyfill.fortnite-site.1ab6b17ed82671772813.js
4180
430
https://static-assets-prod.epicgames.com/fortnite/static/vendor/TweenMax-1.19.0.min.js
4762
127
https://static-assets-prod.epicgames.com/fortnite/static/vendor/TweenMax-1.19.0.min.js
4633
92
https://static-assets-prod.epicgames.com/fortnite/static/vendor/TweenMax-1.19.0.min.js
4892
87
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

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://fortnite.com/
http/1.1
0
84.724000189453
246
0
301
text/html
https://fortnite.com/
http/1.1
85.307999979705
227.10100002587
236
0
301
text/html
https://www.epicgames.com/fortnite/
http/1.1
227.77600027621
290.04200035706
786
0
302
text/html
https://www.epicgames.com/fortnite/en-US/
http/1.1
290.49100028351
468.15800014883
580
0
302
text/html
https://www.epicgames.com/fortnite/en-US/home
h2
468.79200031981
765.94200031832
88784
413950
200
text/html
Document
https://static-assets-prod.epicgames.com/fortnite/static/webpack/thirdParty.fortnite-site.1ab6b17ed82671772813.css
h2
795.77000020072
1271.5520001948
71155
339535
200
text/css
Stylesheet
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.css
h2
796.04599997401
1054.578000214
178653
943742
200
text/css
Stylesheet
https://tracking.epicgames.com/tracking.js
http/1.1
826.61200035363
970.16100026667
18236
57349
200
application/javascript
Script
https://cdn2.unrealengine.com/en-c2s7-c2s7-500x500-6ad51843777e.png
h2
826.84100000188
908.08100020513
8706
8061
200
image/png
Image
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
h2
827.04300014302
1381.8129999563
160287
159640
200
image/png
Image
https://cdn2.unrealengine.com/17br-kiwi-keyart-newsheader-1900x600-13e833a96802.jpg
h2
827.21400028095
1030.9790000319
167593
166945
200
image/jpeg
Image
https://cdn2.unrealengine.com/17br-comp-fncs-characters-newsthumb-1-576x576-fd21ef7ceed7.jpg
h2
827.55400007591
1401.7110001296
43729
43082
200
image/jpeg
Image
https://cdn2.unrealengine.com/15br-fortographyicon-newsthumb-576x576-purple-576x576-6cbbc41897da.jpg
h2
827.86400010809
1233.1130001694
55927
55280
200
image/jpeg
Image
https://cdn2.unrealengine.com/evergreens-purpink-newsthumb-576x576-bdad52d496b8.jpg
h2
829.13500024006
1027.8690000996
143490
142842
200
image/jpeg
Image
https://cdn2.unrealengine.com/15stw-blog-evergreen-orange-blogthumbnail-576x576-576x576-869eab716798.jpg
h2
829.5150003396
1386.9050000794
149621
148973
200
image/jpeg
Image
https://cdn2.unrealengine.com/17br-shangchi-blogthumb-576x576-576x576-48a75f2e5569.jpg
h2
829.85800039023
995.81600027159
116027
115379
200
image/jpeg
Image
https://cdn2.unrealengine.com/newsthumb-alt-576x576-34205f2abf62.jpg
h2
830.22100012749
975.14100000262
42397
41750
200
image/jpeg
Image
https://cdn2.unrealengine.com/17br-nightfaircltm-blogheader-1900x600-5710a0843bde.jpg
h2
830.45700006187
1066.9180001132
553200
552552
200
image/jpeg
Image
https://cdn2.unrealengine.com/17cm-islandgamescreativechallengeblog-newsthumb-576x576-f9e519858c14.jpg
h2
830.82600031048
1020.0500003994
49004
48357
200
image/jpeg
Image
https://cdn2.unrealengine.com/17br-wildweeks-week3-newsthumb-576x576-30a3f359d756.jpg
h2
831.24299999326
1024.8870002106
41740
41093
200
image/jpeg
Image
https://cdn2.unrealengine.com/skyland-thumb-1010x511-df7d7e1e485a.jpg
h2
831.66800020263
1031.8010002375
140225
139577
200
image/jpeg
Image
https://cdn2.unrealengine.com/13br-evergreens-green-newsthumb-576x576-4a87b157276a.jpg
h2
831.93100010976
1024.0980000235
147732
147084
200
image/jpeg
Image
https://cdn2.unrealengine.com/subs-social-progressivebackbling-newsheader-1920x1080-a2710288d1c9.jpg
h2
832.41200027987
1455.246000085
173969
173321
200
image/jpeg
Image
https://cdn2.unrealengine.com/br17-mikelowrey-thumb-576x576-e12b7ef050c4.jpg
h2
832.93600007892
1002.9530003667
28358
27711
200
image/jpeg
Image
https://cdn2.unrealengine.com/seasonalpromo-3840x2334-9a54224f9ed6.png
h2
833.32500001416
1099.6460001916
1848532
1847884
200
image/png
Image
https://cdn2.unrealengine.com/Common+Assets%2FLegal+Icons%2FESRB_FN-369x217-3386d50bb6a48893e81914fb8e44834ef4458c63.png
h2
833.64300010726
1130.9490003623
9303
8558
200
image/png
Image
https://static-assets-prod.epicgames.com/fortnite/static/webpack/polyfill.fortnite-site.1ab6b17ed82671772813.js
h2
833.97500030696
978.2350002788
31489
91661
200
application/javascript
Script
https://static-assets-prod.epicgames.com/fortnite/static/vendor/jquery-3.1.0.min.js
h2
834.32599995285
1162.9440002143
30706
86351
200
application/javascript
Script
https://static-assets-prod.epicgames.com/fortnite/static/vendor/TweenMax-1.19.0.min.js
h2
834.81200039387
1161.6390002891
37958
111633
200
application/javascript
Script
https://static-assets-prod.epicgames.com/fortnite/static/vendor/assets/js/es5-fortnite.js
h2
835.00199997798
1063.0360003561
82826
352469
200
application/javascript
Script
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
h2
835.38000006229
1124.3350002915
989814
3980672
200
application/javascript
Script
data
1292.0220000669
1292.127000168
0
3014
200
image/png
Image
data
1310.2480000816
1310.4120003991
0
3037
200
image/png
Image
data
1310.9010001644
1311.0230001621
0
2959
200
image/png
Image
https://cdn2.unrealengine.com/carousel2-3840x2138-718d0721e284.jpg
h2
1312.4140002765
1347.4790002219
258993
258345
200
image/jpeg
Image
https://cdn2.unrealengine.com/keyart-3840x2138-3739f0c12539.jpg
h2
1313.6599999852
1351.1700001545
753380
752720
200
image/jpeg
Image
https://static-assets-prod.epicgames.com/fortnite/static/webpack/e868c17ab696cf4b6b618bcb2fdca65e.woff
h2
1323.8310003653
1385.2420002222
108351
107728
200
application/font-woff
Font
https://static-assets-prod.epicgames.com/fortnite/static/webpack/57988d1e313ced044867ac305c58ce7b.woff
h2
1324.561000336
1368.0590000004
85319
84696
200
application/font-woff
Font
https://static-assets-prod.epicgames.com/fortnite/static/webpack/55b8ce1f9a32bb0f83f14813eac0b7ca.woff
h2
1325.4370000213
1366.3970003836
85550
84928
200
application/font-woff
Font
https://static-assets-prod.epicgames.com/fortnite/static/webpack/e6c685200f5521b6574f7099061e59e1.ttf
h2
1326.0210002773
1367.4510000274
24377
46104
200
application/font-sfnt
Font
https://static-assets-prod.epicgames.com/fortnite/static/webpack/834e3616d9e57f3f027e96394f43efa0.woff
h2
1326.3509999961
1392.3949999735
88158
87536
200
application/font-woff
Font
https://tracking.epicgames.com/track.png?referringUrl=none&location=https%3A%2F%2Fwww.epicgames.com%2Ffortnite%2Fen-US%2Fhome&now=1630967275075&eventType=pageView
http/1.1
2250.884000212
2396.0260003805
469
0
204
Image
https://www.epicgames.com/fortnite/api/blog/getPosts?category=&postsPerPage=6&offset=0&locale=en-US&rootPageSlug=blog
h2
2299.3740001693
2396.6180002317
15019
52140
200
application/json
XHR
https://static-assets-prod.epicgames.com/fortnite/static/webpack/ef532e79e05e2d24a0f6332068f3a61b.gif
h2
2323.9290001802
2381.9840000942
16271
15660
200
image/gif
Image
data
2518.8919999637
2711.1530001275
7436
7436
200
font/ttf
Font
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)
778.341
10.236
810.03
25.873
835.992
8.298
982.982
7.239
1067.369
40.922
1137.667
9.179
1282.064
14.605
1301.501
68.136
1370.151
859.876
2230.089
9.433
2255.033
7.504
2262.596
20.511
2289.537
5.056
2294.826
13.439
2316.935
5.325
2330.449
183.124
2513.877
5.166
2520.218
34.207
2557.203
30.761
2592.793
126.819
2720.671
6.478
2740.156
32.931
2796.585
87.151
3927.103
13.579
3940.708
6.733
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 1.5 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 4.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 270 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).

Opportunities

Eliminate render-blocking resources — Potential savings of 710 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Fortnite.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://static-assets-prod.epicgames.com/fortnite/static/webpack/thirdParty.fortnite-site.1ab6b17ed82671772813.css
71155
310
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.css
178653
160
Reduce unused CSS — Potential savings of 234 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Fortnite.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.css
178653
175693
https://static-assets-prod.epicgames.com/fortnite/static/webpack/thirdParty.fortnite-site.1ab6b17ed82671772813.css
71155
63991
Efficiently encode images — Potential savings of 353 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn2.unrealengine.com/17br-nightfaircltm-blogheader-1900x600-5710a0843bde.jpg
552552
203150
https://cdn2.unrealengine.com/15stw-blog-evergreen-orange-blogthumbnail-576x576-576x576-869eab716798.jpg
148973
66029
https://cdn2.unrealengine.com/evergreens-purpink-newsthumb-576x576-bdad52d496b8.jpg
142842
59898
https://cdn2.unrealengine.com/17br-shangchi-blogthumb-576x576-576x576-48a75f2e5569.jpg
115379
32435
Avoid multiple page redirects — Potential savings of 640 ms
Redirects can cause additional delays before the page can begin loading. Fortnite.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://fortnite.com/
190
https://fortnite.com/
150
https://www.epicgames.com/fortnite/
230
https://www.epicgames.com/fortnite/en-US/
70
https://www.epicgames.com/fortnite/en-US/home
0

Metrics

Speed Index — 3.7 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 4.4 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.964
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 430 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 2.4 s
The time taken for the primary content of the page to be rendered.

Opportunities

Properly size images — Potential savings of 1,820 KiB
Images can slow down the page's load time. Fortnite.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn2.unrealengine.com/seasonalpromo-3840x2334-9a54224f9ed6.png
1847884
1619366
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
159640
145917
https://cdn2.unrealengine.com/17br-kiwi-keyart-newsheader-1900x600-13e833a96802.jpg
166945
82663
https://cdn2.unrealengine.com/en-c2s7-c2s7-500x500-6ad51843777e.png
8061
7945
https://cdn2.unrealengine.com/Common+Assets%2FLegal+Icons%2FESRB_FN-369x217-3386d50bb6a48893e81914fb8e44834ef4458c63.png
8558
7540
Reduce unused JavaScript — Potential savings of 657 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-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
989814
551582
https://static-assets-prod.epicgames.com/fortnite/static/vendor/assets/js/es5-fortnite.js
82826
69224
https://static-assets-prod.epicgames.com/fortnite/static/vendor/TweenMax-1.19.0.min.js
37958
28916
https://static-assets-prod.epicgames.com/fortnite/static/vendor/jquery-3.1.0.min.js
30706
22952
Serve images in next-gen formats — Potential savings of 1,806 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn2.unrealengine.com/seasonalpromo-3840x2334-9a54224f9ed6.png
1847884
940835.2
https://cdn2.unrealengine.com/17br-nightfaircltm-blogheader-1900x600-5710a0843bde.jpg
552552
392139.1
https://cdn2.unrealengine.com/keyart-3840x2138-3739f0c12539.jpg
752720
227599.55
https://cdn2.unrealengine.com/15stw-blog-evergreen-orange-blogthumbnail-576x576-576x576-869eab716798.jpg
148973
93677
https://cdn2.unrealengine.com/evergreens-purpink-newsthumb-576x576-bdad52d496b8.jpg
142842
87546
https://cdn2.unrealengine.com/17br-shangchi-blogthumb-576x576-576x576-48a75f2e5569.jpg
115379
60083
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
159640
47104

Diagnostics

Avoid enormous network payloads — Total size was 6,687 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdn2.unrealengine.com/seasonalpromo-3840x2334-9a54224f9ed6.png
1848532
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
989814
https://cdn2.unrealengine.com/keyart-3840x2138-3739f0c12539.jpg
753380
https://cdn2.unrealengine.com/17br-nightfaircltm-blogheader-1900x600-5710a0843bde.jpg
553200
https://cdn2.unrealengine.com/carousel2-3840x2138-718d0721e284.jpg
258993
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.css
178653
https://cdn2.unrealengine.com/subs-social-progressivebackbling-newsheader-1920x1080-a2710288d1c9.jpg
173969
https://cdn2.unrealengine.com/17br-kiwi-keyart-newsheader-1900x600-13e833a96802.jpg
167593
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
160287
https://cdn2.unrealengine.com/15stw-blog-evergreen-orange-blogthumbnail-576x576-576x576-869eab716798.jpg
149621
Serve static assets with an efficient cache policy — 14 resources found
Fortnite.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)
https://tracking.epicgames.com/tracking.js
0
18236
https://static-assets-prod.epicgames.com/fortnite/static/webpack/55b8ce1f9a32bb0f83f14813eac0b7ca.woff
262615000
85550
https://static-assets-prod.epicgames.com/fortnite/static/webpack/834e3616d9e57f3f027e96394f43efa0.woff
286854000
88158
https://static-assets-prod.epicgames.com/fortnite/static/vendor/assets/js/es5-fortnite.js
448164000
82826
https://static-assets-prod.epicgames.com/fortnite/static/webpack/e868c17ab696cf4b6b618bcb2fdca65e.woff
575806000
108351
https://static-assets-prod.epicgames.com/fortnite/static/webpack/e6c685200f5521b6574f7099061e59e1.ttf
748924000
24377
https://static-assets-prod.epicgames.com/fortnite/static/webpack/ef532e79e05e2d24a0f6332068f3a61b.gif
1127797000
16271
https://static-assets-prod.epicgames.com/fortnite/static/vendor/jquery-3.1.0.min.js
1453867000
30706
https://static-assets-prod.epicgames.com/fortnite/static/webpack/polyfill.fortnite-site.1ab6b17ed82671772813.js
1628442000
31489
https://static-assets-prod.epicgames.com/fortnite/static/webpack/thirdParty.fortnite-site.1ab6b17ed82671772813.css
1628451000
71155
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
1628453000
989814
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.css
1628467000
178653
https://static-assets-prod.epicgames.com/fortnite/static/vendor/TweenMax-1.19.0.min.js
1704080000
37958
https://static-assets-prod.epicgames.com/fortnite/static/webpack/57988d1e313ced044867ac305c58ce7b.woff
2249803000
85319
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://static-assets-prod.epicgames.com/fortnite/static/webpack/e868c17ab696cf4b6b618bcb2fdca65e.woff
61.410999856889
https://static-assets-prod.epicgames.com/fortnite/static/webpack/57988d1e313ced044867ac305c58ce7b.woff
43.497999664396
https://static-assets-prod.epicgames.com/fortnite/static/webpack/55b8ce1f9a32bb0f83f14813eac0b7ca.woff
40.960000362247
https://static-assets-prod.epicgames.com/fortnite/static/webpack/e6c685200f5521b6574f7099061e59e1.ttf
41.429999750108
https://static-assets-prod.epicgames.com/fortnite/static/webpack/834e3616d9e57f3f027e96394f43efa0.woff
66.04399997741
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://cdn2.unrealengine.com/seasonalpromo-3840x2334-9a54224f9ed6.png
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
https://cdn2.unrealengine.com/Common+Assets%2FLegal+Icons%2FESRB_FN-369x217-3386d50bb6a48893e81914fb8e44834ef4458c63.png
79

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
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.

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.

Names and labels

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

Internationalization and localization

`<html>` element has 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.
`<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"]`
Fortnite.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Buttons do not 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.
Failing Elements
 
Links do not 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.

Navigation

Heading elements are not 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.
Failing Elements

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that fortnite.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.
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

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.
Name Version
jQuery
3.1.0
React
GreenSock JS
1.19.0
Workbox
core-js
core-js-global@2.6.12; core-js-global@2.6.12
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.
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://fortnite.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
3
Medium
1
High

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js.map
https://static-assets-prod.epicgames.com/fortnite/static/webpack/polyfill.fortnite-site.1ab6b17ed82671772813.js
https://static-assets-prod.epicgames.com/fortnite/static/webpack/polyfill.fortnite-site.1ab6b17ed82671772813.js.map
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for fortnite.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 fortnite.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.
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 fortnite.com. This includes details about web app manifests.

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

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not 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) 58
Performance 11
Accessibility 74
Best Practices 87
SEO 75
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.epicgames.com/fortnite/en-US/home
Updated: 6th September, 2021

3.12 seconds
First Contentful Paint (FCP)
45%
29%
26%

0.02 seconds
First Input Delay (FID)
89%
5%
6%

Simulate loading on mobile
11

Performance

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

Opportunities

Defer offscreen images — Potential savings of 279 KiB
Time to Interactive can be slowed down by resources on the page. Fortnite.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn2.unrealengine.com/15stw-blog-evergreen-orange-newsheader-1900x600-1900x600-eb91e1b28cda.jpg
160555
160555
https://cdn2.unrealengine.com/17br-shangchi-blogheader-1900x600-1900x600-f964d456c061.jpg
103376
103376
https://static-assets-prod.epicgames.com/fortnite/static/webpack/ef532e79e05e2d24a0f6332068f3a61b.gif
15660
15660
https://cdn2.unrealengine.com/en-c2s7-c2s7-500x500-6ad51843777e.png
8061
6046
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Fortnite.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Fortnite.com should consider minifying JS files.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
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 200 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://www.epicgames.com/fortnite/en-US/home
203.437
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Fortnite.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 13 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)
https://tracking.epicgames.com/tracking.js
8315
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
5138
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids an excessive DOM size — 432 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
432
Maximum DOM Depth
20
Maximum Child Elements
13
Avoid chaining critical requests — 11 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Fortnite.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.
Keep request counts low and transfer sizes small — 46 requests • 8,854 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
46
9066924
Image
27
7201081
Script
5
1108226
Font
6
401844
Stylesheet
2
250150
Document
1
88769
Other
5
16854
Media
0
0
Third-party
27
7184838
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.85354838709677
0.065201612903226
0.0035597127677338
0.0024409956075907
0.001461465652442
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 9 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://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
22080
1124
https://static-assets-prod.epicgames.com/fortnite/static/webpack/polyfill.fortnite-site.1ab6b17ed82671772813.js
11730
259
https://static-assets-prod.epicgames.com/fortnite/static/vendor/TweenMax-1.19.0.min.js
12010
169
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.css
6480
125
https://www.epicgames.com/fortnite/en-US/home
2713
77
https://www.epicgames.com/fortnite/en-US/home
2825
77
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
23204
57
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
23534
57
https://static-assets-prod.epicgames.com/fortnite/static/webpack/thirdParty.fortnite-site.1ab6b17ed82671772813.css
4380
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

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://fortnite.com/
http/1.1
0
62.675999943167
246
0
301
text/html
https://fortnite.com/
http/1.1
63.241999829188
122.05299991183
251
0
301
text/html
https://www.epicgames.com/fortnite/
http/1.1
122.50399985351
186.20899994858
771
0
302
text/html
https://www.epicgames.com/fortnite/en-US/
http/1.1
186.76499999128
287.11799997836
567
0
302
text/html
https://www.epicgames.com/fortnite/en-US/home
h2
287.58400003426
490.0239999406
88769
413900
200
text/html
Document
https://static-assets-prod.epicgames.com/fortnite/static/webpack/thirdParty.fortnite-site.1ab6b17ed82671772813.css
h2
516.61999989301
714.30199989118
71497
339535
200
text/css
Stylesheet
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.css
h2
516.79799985141
759.65999998152
178653
943742
200
text/css
Stylesheet
https://tracking.epicgames.com/tracking.js
http/1.1
539.64599990286
615.69199990481
18269
57349
200
application/javascript
Script
https://cdn2.unrealengine.com/en-c2s7-c2s7-500x500-6ad51843777e.png
h2
539.86899997108
620.50399999134
8706
8061
200
image/png
Image
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
h2
540.25899991393
625.96499989741
160287
159640
200
image/png
Image
https://cdn2.unrealengine.com/17br-kiwi-keyart-newsheader-1900x600-13e833a96802.jpg
h2
540.48500000499
899.76599998772
167593
166945
200
image/jpeg
Image
https://cdn2.unrealengine.com/17br-comp-fncs-characters-newsthumb-1-576x576-fd21ef7ceed7.jpg
h2
540.70100001991
580.57300001383
43729
43082
200
image/jpeg
Image
https://cdn2.unrealengine.com/15br-fortographyicon-newsthumb-576x576-purple-576x576-6cbbc41897da.jpg
h2
540.88699980639
569.60099982098
55927
55280
200
image/jpeg
Image
https://cdn2.unrealengine.com/evergreens-purpink-newsheader-1920x1080-2448b2c09020.jpg
h2
541.52500000782
682.6080000028
219108
218460
200
image/jpeg
Image
https://cdn2.unrealengine.com/15stw-blog-evergreen-orange-newsheader-1900x600-1900x600-eb91e1b28cda.jpg
h2
541.6419999674
720.37200001068
161203
160555
200
image/jpeg
Image
https://cdn2.unrealengine.com/17br-shangchi-blogheader-1900x600-1900x600-f964d456c061.jpg
h2
541.97399993427
761.18299993686
104024
103376
200
image/jpeg
Image
https://cdn2.unrealengine.com/newsthumb-alt-576x576-34205f2abf62.jpg
h2
542.30499989353
906.52800002135
42397
41750
200
image/jpeg
Image
https://cdn2.unrealengine.com/17br-nightfaircltm-blogheader-1900x600-5710a0843bde.jpg
h2
542.45999990962
587.27699983865
553200
552552
200
image/jpeg
Image
https://cdn2.unrealengine.com/17cm-islandgamescreativechallengeblog-newsthumb-576x576-f9e519858c14.jpg
h2
542.67899994738
732.22999996506
49004
48357
200
image/jpeg
Image
https://cdn2.unrealengine.com/17br-wildweeks-week3-blogheader-1900x600-48f6f5010987.jpg
h2
542.91499988176
762.06999993883
185124
184476
200
image/jpeg
Image
https://cdn2.unrealengine.com/skyland-4302x2420-ecf80bdd0576.png
h2
543.14800002612
855.62299983576
3392861
3392213
200
image/png
Image
https://cdn2.unrealengine.com/13br-evergreens-green-1920x1080-7eb572aacb65.jpg
h2
543.34999993443
697.46900000609
227810
227162
200
image/jpeg
Image
https://cdn2.unrealengine.com/subs-social-progressivebackbling-newsheader-1920x1080-a2710288d1c9.jpg
h2
543.57700003311
743.90899995342
173969
173321
200
image/jpeg
Image
https://cdn2.unrealengine.com/br17-mikelowrey-thumb-576x576-e12b7ef050c4.jpg
h2
543.89499989338
696.40899985097
28358
27711
200
image/jpeg
Image
https://cdn2.unrealengine.com/seasonalpromo-m-1500x2401-d189c91bb5e8.png
h2
544.21700001694
829.97499988414
656729
656082
200
image/png
Image
https://cdn2.unrealengine.com/Common+Assets%2FLegal+Icons%2FESRB_FN-369x217-3386d50bb6a48893e81914fb8e44834ef4458c63.png
h2
544.40699983388
608.18799980916
9202
8558
200
image/png
Image
https://static-assets-prod.epicgames.com/fortnite/static/webpack/polyfill.fortnite-site.1ab6b17ed82671772813.js
h2
544.6299999021
675.89199985377
31489
91661
200
application/javascript
Script
https://static-assets-prod.epicgames.com/fortnite/static/vendor/jquery-3.1.0.min.js
h2
544.76099996828
680.03699998371
30663
86351
200
application/javascript
Script
https://static-assets-prod.epicgames.com/fortnite/static/vendor/TweenMax-1.19.0.min.js
h2
545.21199990995
725.80399992876
37946
111633
200
application/javascript
Script
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
h2
546.6759998817
972.51099999994
989859
3980672
200
application/javascript
Script
data
816.92399992608
817.04599992372
0
3014
200
image/png
Image
data
818.48899996839
818.57299990952
0
3037
200
image/png
Image
data
818.95400001667
819.0239998512
0
2959
200
image/png
Image
https://cdn2.unrealengine.com/carousel2-m-1508x2388-7fb69a478c86.jpg
h2
820.21899987012
861.07099987566
164900
164252
200
image/jpeg
Image
https://cdn2.unrealengine.com/keyart-m-754x1195-f9320c8403a7.jpg
h2
821.03500002995
861.65499989875
179434
178786
200
image/jpeg
Image
https://static-assets-prod.epicgames.com/fortnite/static/webpack/e868c17ab696cf4b6b618bcb2fdca65e.woff
h2
828.66499992087
871.45299999975
108351
107728
200
application/font-woff
Font
https://static-assets-prod.epicgames.com/fortnite/static/webpack/57988d1e313ced044867ac305c58ce7b.woff
h2
831.20399992913
917.28099994361
85319
84696
200
application/font-woff
Font
https://static-assets-prod.epicgames.com/fortnite/static/webpack/55b8ce1f9a32bb0f83f14813eac0b7ca.woff
h2
831.3639999833
874.10799995996
85550
84928
200
application/font-woff
Font
https://static-assets-prod.epicgames.com/fortnite/static/webpack/e6c685200f5521b6574f7099061e59e1.ttf
h2
831.49999985471
916.65499983355
24377
46104
200
application/font-sfnt
Font
https://static-assets-prod.epicgames.com/fortnite/static/webpack/834e3616d9e57f3f027e96394f43efa0.woff
h2
831.59799990244
1009.6529999282
88158
87536
200
application/font-woff
Font
https://cdn2.unrealengine.com/15br-fortographyicon-newsheader-1920x600-purple-1920x600-c5efbdf4a005.jpg
h2
1698.7499999814
1723.1209999882
46618
45971
200
image/jpeg
Image
https://cdn2.unrealengine.com/newsheader-1900x600-alt-1900x600-53c2a27c7054.jpg
h2
1700.0149998348
1789.2289999872
134962
134314
200
image/jpeg
Image
https://cdn2.unrealengine.com/17cm-islandgamescreativechallengeblog-blogheader-1900x600-f3425ffc0c8c.jpg
h2
1700.588000007
1733.853999991
189863
189215
200
image/jpeg
Image
https://cdn2.unrealengine.com/br17-mikelowrey-header-1900x600-c5be641a6010.jpg
h2
1701.6219999641
1726.4829999767
54503
53856
200
image/jpeg
Image
https://static-assets-prod.epicgames.com/fortnite/static/webpack/5df4bc87a714ce6e477fb713dff7c663.ttf
h2
1702.3679998238
1731.1729998328
10089
15412
200
application/font-sfnt
Font
https://tracking.epicgames.com/track.png?referringUrl=none&location=https%3A%2F%2Fwww.epicgames.com%2Ffortnite%2Fen-US%2Fhome&now=1630967306601&eventType=pageView
http/1.1
1727.492999984
1868.7630000059
469
0
204
Image
https://www.epicgames.com/fortnite/api/blog/getPosts?category=&postsPerPage=6&offset=0&locale=en-US&rootPageSlug=blog
h2
1755.382000003
1808.4019999951
15019
52140
200
application/json
XHR
https://static-assets-prod.epicgames.com/fortnite/static/webpack/ef532e79e05e2d24a0f6332068f3a61b.gif
h2
1760.6929999311
1790.7529999502
16271
15660
200
image/gif
Image
https://cdn2.unrealengine.com/17br-comp-fncs-characters-newsheader-1900x600-1900x600-f35c96631d1d.jpg
h2
1826.2289999984
1896.0959999822
174830
174182
200
image/jpeg
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)
502.114
7.558
529.43
19.361
548.839
5.266
628.541
6.3
724.615
12.441
773.786
31.195
804.996
17.293
826.614
38.585
865.601
64.84
942.605
10.628
963.968
84.295
1049.17
8.103
1176.139
561.88
1738.072
5.779
1758.21
5.959
1792.222
14.222
1806.587
9.511
1820.083
28.516
1878.831
5.15
2821.11
5.843
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.

Diagnostics

Reduce JavaScript execution time — 2.6 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://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
2622.244
2026.356
245.96
https://www.epicgames.com/fortnite/en-US/home
575.356
14.804
44.812
https://static-assets-prod.epicgames.com/fortnite/static/vendor/TweenMax-1.19.0.min.js
455.98
67.72
8.456
Unattributable
415.9
12.044
0.68
https://static-assets-prod.epicgames.com/fortnite/static/webpack/polyfill.fortnite-site.1ab6b17ed82671772813.js
143.168
135.2
7.344
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.css
124.78
0
0

Metrics

First Contentful Paint — 5.7 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 11.2 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 10.8 s
The timing of the largest text or image that is painted.
Time to Interactive — 18.7 s
The time taken for the page to become fully interactive.
Total Blocking Time — 950 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.927
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 1,120 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 6.8 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 11880 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 — Potential savings of 2,980 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Fortnite.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://static-assets-prod.epicgames.com/fortnite/static/webpack/thirdParty.fortnite-site.1ab6b17ed82671772813.css
71497
1080
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.css
178653
900
Properly size images — Potential savings of 1,267 KiB
Images can slow down the page's load time. Fortnite.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn2.unrealengine.com/seasonalpromo-m-1500x2401-d189c91bb5e8.png
656082
395792
https://cdn2.unrealengine.com/evergreens-purpink-newsheader-1920x1080-2448b2c09020.jpg
218460
165538
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
159640
137458
https://cdn2.unrealengine.com/17br-comp-fncs-characters-newsheader-1900x600-1900x600-f35c96631d1d.jpg
174182
131094
https://cdn2.unrealengine.com/17br-kiwi-keyart-newsheader-1900x600-13e833a96802.jpg
166945
125647
https://cdn2.unrealengine.com/15stw-blog-evergreen-orange-newsheader-1900x600-1900x600-eb91e1b28cda.jpg
160555
120838
https://cdn2.unrealengine.com/newsheader-1900x600-alt-1900x600-53c2a27c7054.jpg
134314
101088
https://cdn2.unrealengine.com/17br-shangchi-blogheader-1900x600-1900x600-f964d456c061.jpg
103376
77803
https://cdn2.unrealengine.com/15br-fortographyicon-newsheader-1920x600-purple-1920x600-c5efbdf4a005.jpg
45971
34835
https://cdn2.unrealengine.com/en-c2s7-c2s7-500x500-6ad51843777e.png
8061
7261
Reduce unused CSS — Potential savings of 233 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Fortnite.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.css
178653
174898
https://static-assets-prod.epicgames.com/fortnite/static/webpack/thirdParty.fortnite-site.1ab6b17ed82671772813.css
71497
64166
Reduce unused JavaScript — Potential savings of 589 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-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
989859
550865
https://static-assets-prod.epicgames.com/fortnite/static/vendor/TweenMax-1.19.0.min.js
37946
28973
https://static-assets-prod.epicgames.com/fortnite/static/vendor/jquery-3.1.0.min.js
30663
22919
Efficiently encode images — Potential savings of 316 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn2.unrealengine.com/17br-nightfaircltm-blogheader-1900x600-5710a0843bde.jpg
552552
203150
https://cdn2.unrealengine.com/17br-wildweeks-week3-blogheader-1900x600-48f6f5010987.jpg
184476
38408
https://cdn2.unrealengine.com/17br-comp-fncs-characters-newsheader-1900x600-1900x600-f35c96631d1d.jpg
174182
37249
https://cdn2.unrealengine.com/17cm-islandgamescreativechallengeblog-blogheader-1900x600-f3425ffc0c8c.jpg
189215
34619
https://cdn2.unrealengine.com/keyart-m-754x1195-f9320c8403a7.jpg
178786
10619
Serve images in next-gen formats — Potential savings of 1,843 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn2.unrealengine.com/17br-nightfaircltm-blogheader-1900x600-5710a0843bde.jpg
552552
392139.1
https://cdn2.unrealengine.com/seasonalpromo-m-1500x2401-d189c91bb5e8.png
656082
368942.7
https://cdn2.unrealengine.com/17cm-islandgamescreativechallengeblog-blogheader-1900x600-f3425ffc0c8c.jpg
189215
119755.6
https://cdn2.unrealengine.com/17br-wildweeks-week3-blogheader-1900x600-48f6f5010987.jpg
184476
118710.2
https://cdn2.unrealengine.com/17br-comp-fncs-characters-newsheader-1900x600-1900x600-f35c96631d1d.jpg
174182
111675.95
https://cdn2.unrealengine.com/keyart-m-754x1195-f9320c8403a7.jpg
178786
93908.25
https://cdn2.unrealengine.com/subs-social-progressivebackbling-newsheader-1920x1080-a2710288d1c9.jpg
173321
92881.15
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
159640
92517.85
https://cdn2.unrealengine.com/13br-evergreens-green-1920x1080-7eb572aacb65.jpg
227162
82787.05
https://cdn2.unrealengine.com/15stw-blog-evergreen-orange-newsheader-1900x600-1900x600-eb91e1b28cda.jpg
160555
79467.7
https://cdn2.unrealengine.com/17br-kiwi-keyart-newsheader-1900x600-13e833a96802.jpg
166945
79128.8
https://cdn2.unrealengine.com/evergreens-purpink-newsheader-1920x1080-2448b2c09020.jpg
218460
72472.95
https://cdn2.unrealengine.com/newsheader-1900x600-alt-1900x600-53c2a27c7054.jpg
134314
69388.65
https://cdn2.unrealengine.com/17br-shangchi-blogheader-1900x600-1900x600-f964d456c061.jpg
103376
56932.15
https://cdn2.unrealengine.com/carousel2-m-1508x2388-7fb69a478c86.jpg
164252
56478.8
Avoid multiple page redirects — Potential savings of 2,070 ms
Redirects can cause additional delays before the page can begin loading. Fortnite.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://fortnite.com/
630
https://fortnite.com/
480
https://www.epicgames.com/fortnite/
780
https://www.epicgames.com/fortnite/en-US/
180
https://www.epicgames.com/fortnite/en-US/home
0

Diagnostics

Avoid enormous network payloads — Total size was 8,854 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdn2.unrealengine.com/skyland-4302x2420-ecf80bdd0576.png
3392861
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
989859
https://cdn2.unrealengine.com/seasonalpromo-m-1500x2401-d189c91bb5e8.png
656729
https://cdn2.unrealengine.com/17br-nightfaircltm-blogheader-1900x600-5710a0843bde.jpg
553200
https://cdn2.unrealengine.com/13br-evergreens-green-1920x1080-7eb572aacb65.jpg
227810
https://cdn2.unrealengine.com/evergreens-purpink-newsheader-1920x1080-2448b2c09020.jpg
219108
https://cdn2.unrealengine.com/17cm-islandgamescreativechallengeblog-blogheader-1900x600-f3425ffc0c8c.jpg
189863
https://cdn2.unrealengine.com/17br-wildweeks-week3-blogheader-1900x600-48f6f5010987.jpg
185124
https://cdn2.unrealengine.com/keyart-m-754x1195-f9320c8403a7.jpg
179434
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.css
178653
Serve static assets with an efficient cache policy — 15 resources found
Fortnite.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)
https://tracking.epicgames.com/tracking.js
0
18269
https://static-assets-prod.epicgames.com/fortnite/static/webpack/55b8ce1f9a32bb0f83f14813eac0b7ca.woff
262525000
85550
https://static-assets-prod.epicgames.com/fortnite/static/webpack/834e3616d9e57f3f027e96394f43efa0.woff
286741000
88158
https://static-assets-prod.epicgames.com/fortnite/static/vendor/TweenMax-1.19.0.min.js
332685000
37946
https://static-assets-prod.epicgames.com/fortnite/static/webpack/e868c17ab696cf4b6b618bcb2fdca65e.woff
575785000
108351
https://static-assets-prod.epicgames.com/fortnite/static/webpack/e6c685200f5521b6574f7099061e59e1.ttf
748902000
24377
https://static-assets-prod.epicgames.com/fortnite/static/webpack/ef532e79e05e2d24a0f6332068f3a61b.gif
1127703000
16271
https://static-assets-prod.epicgames.com/fortnite/static/webpack/5df4bc87a714ce6e477fb713dff7c663.ttf
1564543000
10089
https://static-assets-prod.epicgames.com/fortnite/static/webpack/thirdParty.fortnite-site.1ab6b17ed82671772813.css
1628387000
71497
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.css
1628393000
178653
https://static-assets-prod.epicgames.com/fortnite/static/webpack/polyfill.fortnite-site.1ab6b17ed82671772813.js
1628410000
31489
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
1628446000
989859
https://static-assets-prod.epicgames.com/fortnite/static/vendor/jquery-3.1.0.min.js
1816738000
30663
https://static-assets-prod.epicgames.com/fortnite/static/webpack/57988d1e313ced044867ac305c58ce7b.woff
2249793000
85319
https://cdn2.unrealengine.com/Common+Assets%2FLegal+Icons%2FESRB_FN-369x217-3386d50bb6a48893e81914fb8e44834ef4458c63.png
4248102000
9202
Minimize main-thread work — 4.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
2323.96
Other
634.748
Style & Layout
475.072
Rendering
363.392
Script Parsing & Compilation
319.004
Parse HTML & CSS
234.544
Garbage Collection
119.684
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://static-assets-prod.epicgames.com/fortnite/static/webpack/e868c17ab696cf4b6b618bcb2fdca65e.woff
42.788000078872
https://static-assets-prod.epicgames.com/fortnite/static/webpack/57988d1e313ced044867ac305c58ce7b.woff
86.077000014484
https://static-assets-prod.epicgames.com/fortnite/static/webpack/55b8ce1f9a32bb0f83f14813eac0b7ca.woff
42.743999976665
https://static-assets-prod.epicgames.com/fortnite/static/webpack/e6c685200f5521b6574f7099061e59e1.ttf
85.15499997884
https://static-assets-prod.epicgames.com/fortnite/static/webpack/834e3616d9e57f3f027e96394f43efa0.woff
178.05500002578
https://static-assets-prod.epicgames.com/fortnite/static/webpack/5df4bc87a714ce6e477fb713dff7c663.ttf
28.805000009015
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://cdn2.unrealengine.com/seasonalpromo-m-1500x2401-d189c91bb5e8.png
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
https://cdn2.unrealengine.com/invasion-logo-en-2084x324-cfb7d39c2827.png
https://cdn2.unrealengine.com/Common+Assets%2FLegal+Icons%2FESRB_FN-369x217-3386d50bb6a48893e81914fb8e44834ef4458c63.png
74

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
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.
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.

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.

Names and labels

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

Internationalization and localization

`<html>` element has 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.
`<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"]`
Fortnite.com may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`button`, `link`, and `menuitem` elements do not 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.

Names and labels

Buttons do not 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.
Failing Elements
 
Links do not 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.

Navigation

Heading elements are not 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.
Failing Elements

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that fortnite.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.
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

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.
Name Version
jQuery
3.1.0
React
GreenSock JS
1.19.0
Workbox
core-js
core-js-global@2.6.12; core-js-global@2.6.12
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.
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://fortnite.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
3
Medium
1
High

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js
https://static-assets-prod.epicgames.com/fortnite/static/webpack/main.fortnite-site.1ab6b17ed82671772813.js.map
https://static-assets-prod.epicgames.com/fortnite/static/webpack/polyfill.fortnite-site.1ab6b17ed82671772813.js
https://static-assets-prod.epicgames.com/fortnite/static/webpack/polyfill.fortnite-site.1ab6b17ed82671772813.js.map
75

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for fortnite.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 fortnite.com on mobile screens.

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.
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.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 57% 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.
Tap Target Size Overlapping Target
36x36
36x36
26x17
26x17
FAQ
23x17
FAQ
23x17
30x17
34x17
35x17
35x17
107x17
83x14
 
26x22
 
 
26x22
 

Crawling and Indexing

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

Content Best Practices

Mobile Friendly

Document doesn't use legible font sizes — 52.94% 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
.egf .copyright .copyright-paragraph
42.81%
11.36px
.fortnite-wrapper h4
2.65%
10.8px
.egf .legal .links li a
1.02%
10.8px
.fortnite-wrapper a, .fortnite-wrapper ol, .fortnite-wrapper p, .fortnite-wrapper ul
0.31%
8.64px
#egh #rightNav.topNav .ctaWrapper .cta
0.27%
8.75px
52.94%
≥ 12px

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

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

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

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not 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: 3.223.11.152
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Amazon Data Services NoVa
Registration

Domain Registrant

Private Registration: No
Name: Domain Administrator
Organization: DNStination Inc.
Country: US
City: San Francisco
State: CA
Post Code: 94118
Email: admin@dnstinations.com
Phone: +1.4155319335
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
MarkMonitor, Inc. 172.64.148.104
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: fortnite.com
Issued By: Amazon RSA 2048 M03
Valid From: 26th September, 2023
Valid To: 24th October, 2024
Subject: CN = fortnite.com
Hash: 40bd7a91
Issuer: CN = Amazon RSA 2048 M03
O = Amazon
S = US
Version: 2
Serial Number: 14353883657565373874084392857646204811
Serial Number (Hex): 0ACC751A7D1BD1BD5CCB04EAB51D078B
Valid From: 26th September, 2024
Valid To: 24th October, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:55:D9:18:5F:D2:1C:CC:01:E1:58:B4:BE:AB:D9:55:42:01:D7:2E:02
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.r2m03.amazontrust.com/r2m03.crl

Certificate Policies: Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://ocsp.r2m03.amazontrust.com
CA Issuers - URI:http://crt.r2m03.amazontrust.com/r2m03.cer

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
Timestamp : Sep 26 07:55:27.874 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:04:C4:6F:23:E4:28:38:53:EB:19:E0:CC:
1F:61:A0:60:D2:08:9D:46:BB:DC:3A:53:4F:4E:06:BF:
E3:E8:C7:A7:02:21:00:B2:7B:3C:9B:2B:7D:9E:10:9B:
BE:CA:97:79:52:7B:B9:DD:F8:C5:FE:60:41:1F:8E:66:
D1:89:84:16:A8:77:24
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
Timestamp : Sep 26 07:55:27.864 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:21:6E:73:34:12:D0:1C:F4:4B:87:6E:4A:
5F:01:E2:93:E7:18:D7:82:84:62:6C:95:69:87:D0:69:
65:D4:FC:76:02:21:00:84:87:B4:40:0B:17:DC:DC:F7:
F5:34:45:D1:99:40:A9:B0:6E:78:65:56:5E:08:31:7A:
52:2B:E9:6B:48:FB:0C
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DA:B6:BF:6B:3F:B5:B6:22:9F:9B:C2:BB:5C:6B:E8:70:
91:71:6C:BB:51:84:85:34:BD:A4:3D:30:48:D7:FB:AB
Timestamp : Sep 26 07:55:27.796 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:B7:F7:B9:07:F5:0D:C1:E8:8E:60:21:
91:8D:4E:9F:81:9F:8B:BC:E4:6F:2B:C2:80:B9:F1:2D:
2D:04:76:23:5C:02:20:42:EE:35:34:EC:46:ED:29:E2:
D5:D1:B5:96:55:B3:73:C4:4E:23:67:86:2B:34:C7:11:
1A:7B:98:AA:C3:66:35
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.fortnite.com
DNS:fortnite.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
fortnite.com. 54.145.134.15 IN 60
fortnite.com. 54.235.165.70 IN 60
fortnite.com. 52.21.9.16 IN 60
fortnite.com. 3.87.85.152 IN 60
fortnite.com. 34.192.20.235 IN 60
fortnite.com. 54.210.9.46 IN 60
fortnite.com. 18.214.57.52 IN 60
fortnite.com. 54.86.163.210 IN 60

NS Records

Host Nameserver Class TTL
fortnite.com. ns-1369.awsdns-43.org. IN 21600
fortnite.com. ns-1743.awsdns-25.co.uk. IN 21600
fortnite.com. ns-506.awsdns-63.com. IN 21600
fortnite.com. ns-574.awsdns-07.net. IN 21600

MX Records

Priority Host Server Class TTL
10 fortnite.com. mxa-003d3601.gslb.pphosted.com. IN 60
10 fortnite.com. mxb-003d3601.gslb.pphosted.com. IN 60

SOA Records

Domain Name Primary NS Responsible Email TTL
fortnite.com. ns-1369.awsdns-43.org. awsdns-hostmaster.amazon.com. 900

TXT Records

Host Value Class TTL
fortnite.com. 19bb1198c0164b2e988d1cc7f05a4d08 IN 3600
fortnite.com. 8tg7dv1x967g01sjw0dcdrfnlgpmxq5j IN 3600
fortnite.com. ca3-0afdf752e4914b73aacd7096019a3cf0 IN 3600
fortnite.com. facebook-domain-verification=wdak0zd7nrui54kymhzb8ctry9oxkz IN 3600
fortnite.com. google-site-verification=42dUY67FlkKjjPh67P7O85fZYuY-EoG33qiJCMgAWA0 IN 3600
fortnite.com. google-site-verification=XRT98nvNEL5jiVkTZBzKdWyI1d82UE689jLKyMGErfY IN 3600
fortnite.com. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/2 301
date: 9th March, 2024
content-type: text/html
content-length: 178
location: https://www.fortnite.com

Whois Lookup

Created: 26th May, 2010
Changed: 19th October, 2023
Expires: 20th November, 2025
Registrar: MarkMonitor, Inc.
Status: clientUpdateProhibited
clientTransferProhibited
clientDeleteProhibited
Nameservers: ns-1369.awsdns-43.org
ns-1743.awsdns-25.co.uk
ns-506.awsdns-63.com
ns-574.awsdns-07.net
Owner Name: Domain Administrator
Owner Organization: DNStination Inc.
Owner Street: 3450 Sacramento Street, Suite 405
Owner Post Code: 94118
Owner City: San Francisco
Owner State: CA
Owner Country: US
Owner Phone: +1.4155319335
Owner Email: admin@dnstinations.com
Admin Name: Domain Administrator
Admin Organization: DNStination Inc.
Admin Street: 3450 Sacramento Street, Suite 405
Admin Post Code: 94118
Admin City: San Francisco
Admin State: CA
Admin Country: US
Admin Phone: +1.4155319335
Admin Email: admin@dnstinations.com
Tech Name: Domain Administrator
Tech Organization: DNStination Inc.
Tech Street: 3450 Sacramento Street, Suite 405
Tech Post Code: 94118
Tech City: San Francisco
Tech State: CA
Tech Country: US
Tech Phone: +1.4155319335
Tech Email: admin@dnstinations.com
Full Whois: Domain Name: fortnite.com
Registry Domain ID: 1599206193_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2023-10-19T11:01:48+0000
Creation Date: 2010-05-26T18:32:13+0000
Registrar Registration Expiration Date: 2025-11-20T00:00:00+0000
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2086851750
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Registry Registrant ID:
Registrant Name: Domain Administrator
Registrant Organization: DNStination Inc.
Registrant Street: 3450 Sacramento Street, Suite 405
Registrant City: San Francisco
Registrant State/Province: CA
Registrant Postal Code: 94118
Registrant Country: US
Registrant Phone: +1.4155319335
Registrant Phone Ext:
Registrant Fax: +1.4155319336
Registrant Fax Ext:
Registrant Email: admin@dnstinations.com
Registry Admin ID:
Admin Name: Domain Administrator
Admin Organization: DNStination Inc.
Admin Street: 3450 Sacramento Street, Suite 405
Admin City: San Francisco
Admin State/Province: CA
Admin Postal Code: 94118
Admin Country: US
Admin Phone: +1.4155319335
Admin Phone Ext:
Admin Fax: +1.4155319336
Admin Fax Ext:
Admin Email: admin@dnstinations.com
Registry Tech ID:
Tech Name: Domain Administrator
Tech Organization: DNStination Inc.
Tech Street: 3450 Sacramento Street, Suite 405
Tech City: San Francisco
Tech State/Province: CA
Tech Postal Code: 94118
Tech Country: US
Tech Phone: +1.4155319335
Tech Phone Ext:
Tech Fax: +1.4155319336
Tech Fax Ext:
Tech Email: admin@dnstinations.com
Name Server: ns-506.awsdns-63.com
Name Server: ns-574.awsdns-07.net
Name Server: ns-1369.awsdns-43.org
Name Server: ns-1743.awsdns-25.co.uk
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-03-09T14:31:27+0000 <<<

For more information on WHOIS status codes, please visit:
https://www.icann.org/resources/pages/epp-status-codes

If you wish to contact this domain’s Registrant, Administrative, or Technical
contact, and such email address is not visible above, you may do so via our web
form, pursuant to ICANN’s Temporary Specification. To verify that you are not a
robot, please enter your email address to receive a link to a page that
facilitates email communication with the relevant contact(s).

Web-based WHOIS:
https://domains.markmonitor.com/whois

If you have a legitimate interest in viewing the non-public WHOIS details, send
your request and the reasons for your request to whoisrequest@markmonitor.com
and specify the domain name in the subject line. We will review that request and
may ask for supporting documentation and explanation.

The data in MarkMonitor’s WHOIS database is provided for information purposes,
and to assist persons in obtaining information about or related to a domain
name’s registration record. While MarkMonitor believes the data to be accurate,
the data is provided "as is" with no guarantee or warranties regarding its
accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
(1) allow, enable, or otherwise support the transmission by email, telephone,
or facsimile of mass, unsolicited, commercial advertising, or spam; or
(2) enable high volume, automated, or electronic processes that send queries,
data, or email to MarkMonitor (or its systems) or the domain name contacts (or
its systems).

MarkMonitor reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by this policy.

MarkMonitor Domain Management(TM)
Protecting companies and consumers in a digital world.

Visit MarkMonitor at https://www.markmonitor.com
Contact us at +1.8007459229
In Europe, at +44.02032062220

Nameservers

Name IP Address
ns-1369.awsdns-43.org 205.251.197.89
ns-1743.awsdns-25.co.uk 205.251.198.207
ns-506.awsdns-63.com 205.251.193.250
ns-574.awsdns-07.net 205.251.194.62
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
$164 USD
0/5

Sites hosted on the same IP address