Tools & Wizards About Us
fortnitetracker.gg screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

fortnitetracker.gg

Fortnite Tracker - Fortnite Stats, Events, Leaderboard, Items Shop

Page Load Speed

3.8 sec in total

First Response

1.2 sec

Resources Loaded

2.1 sec

Page Rendered

571 ms

fortnitetracker.gg screenshot

About Website

Click here to check amazing Fortnite Tracker content for Egypt. Otherwise, check out these important facts you probably never knew about fortnitetracker.gg

Get a list of all New Fortnite Stats, Events, Leaderboard, Items Shop, Weapons, Creatives, Fish, updated daily on the Fortnite Tracker

Visit fortnitetracker.gg

Key Findings

We analyzed Fortnitetracker.gg page load time and found that the first response time was 1.2 sec and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

fortnitetracker.gg performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.301

39/100

15%

TTI (Time to Interactive)

Value8.9 s

35/100

10%

Network Requests Diagram

fortnitetracker.gg

1200 ms

gppstub.js

126 ms

vue.global.prod.min.js

12 ms

js

65 ms

ezvideojscss.css

40 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 57% of them (26 requests) were addressed to the original Fortnitetracker.gg, 15% (7 requests) were made to Media.fortniteapi.io and 4% (2 requests) were made to The.gatekeeperconsent.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Fortnitetracker.gg.

Page Optimization Overview & Recommendations

Page size can be reduced by 188.9 kB (47%)

Content Size

403.1 kB

After Optimization

214.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Fortnitetracker.gg main page is 403.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. HTML takes 221.3 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 187.3 kB

  • Original 221.3 kB
  • After minification 220.9 kB
  • After compression 34.0 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 187.3 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 939 B

  • Original 98.7 kB
  • After minification 97.8 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Fortnite Tracker images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 713 B

  • Original 83.1 kB
  • After minification 83.1 kB
  • After compression 82.4 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 31 (86%)

Requests Now

36

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fortnite Tracker. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fortnitetracker.gg

fortnitetracker.gg

1200 ms

gppstub.js

gppstub.js

126 ms

vue.global.prod.min.js

vue.global.prod.min.js

12 ms

js

js

65 ms

ezvideojscss.css

ezvideojscss.css

40 ms

ezvideojspluginscss.css

ezvideojspluginscss.css

15 ms

ezvideocss.css

ezvideocss.css

63 ms

ccpaplus.js

ccpaplus.js

183 ms

v.js

v.js

155 ms

boise.js

boise.js

30 ms

abilene.js

abilene.js

30 ms

tulsa.js

tulsa.js

30 ms

et.js

et.js

28 ms

axolotl.js

axolotl.js

23 ms

lazy_load.js

lazy_load.js

23 ms

js

js

132 ms

analytics.js

analytics.js

129 ms

mulvane.js

mulvane.js

71 ms

wichita.js

wichita.js

69 ms

raleigh.js

raleigh.js

70 ms

vista.js

vista.js

70 ms

screx.js

screx.js

119 ms

transparent.png

transparent.png

399 ms

tortoise.js

tortoise.js

75 ms

css_onload.js

css_onload.js

74 ms

drake.js

drake.js

73 ms

jellyfish.js

jellyfish.js

74 ms

transparent.png

transparent.png

499 ms

transparent.png

transparent.png

610 ms

transparent.png

transparent.png

612 ms

transparent.png

transparent.png

614 ms

transparent.png

transparent.png

615 ms

transparent.png

transparent.png

606 ms

abfe73f9c6bb341c0d9aa9c8bee8b70655bb91147058c21ae8717df763229acf-3d3cf0bc-d8d4-4bb3-b7e9-4308a0409729.jpeg

abfe73f9c6bb341c0d9aa9c8bee8b70655bb91147058c21ae8717df763229acf-3d3cf0bc-d8d4-4bb3-b7e9-4308a0409729.jpeg

512 ms

olathe.js

olathe.js

96 ms

vitals.js

vitals.js

50 ms

chanute.js

chanute.js

51 ms

collect

collect

47 ms

script_delay.js

script_delay.js

15 ms

bootstrap.min.css

bootstrap.min.css

175 ms

ionicons.min.css

ionicons.min.css

62 ms

css

css

112 ms

style.css

style.css

16 ms

collect

collect

142 ms

ionicons.ttf

ionicons.ttf

68 ms

HI_OiY8KO6hCsQSoAPmtMYebvpWfOMPT.ttf

HI_OiY8KO6hCsQSoAPmtMYebvpWfOMPT.ttf

95 ms

Accessibility Review

fortnitetracker.gg accessibility score

90

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best Practices

fortnitetracker.gg best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

fortnitetracker.gg SEO score

91

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fortnitetracker.gg can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fortnitetracker.gg main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

fortnitetracker.gg

Open Graph description is not detected on the main page of Fortnite Tracker. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: