Tools & Wizards About Us
egos.io screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

egos.io

CampaignTracker | Home

Page Load Speed

908 ms in total

First Response

35 ms

Resources Loaded

443 ms

Page Rendered

430 ms

egos.io screenshot

About Website

Welcome to egos.io homepage info - get ready to check Egos best content right away, or after learning these important things about egos.io

Home - Our quick, easy UTM builder and URL shortener gives you the ability to manage links and maintain accurate UTM tagged links.

Visit egos.io

Key Findings

We analyzed Egos.io page load time and found that the first response time was 35 ms and then it took 873 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

egos.io performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.052

99/100

15%

TTI (Time to Interactive)

Value6.3 s

61/100

10%

Network Requests Diagram

egos.io

35 ms

campaigntracker.io

114 ms

style.css

14 ms

animate.css

27 ms

wow.min.js

28 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Egos.io, 50% (10 requests) were made to Cdn.campaigntracker.io and 30% (6 requests) were made to Campaigntracker.io. The less responsive or slowest element that took the longest time to load (205 ms) relates to the external source Cdn.campaigntracker.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 78.8 kB (84%)

Content Size

93.4 kB

After Optimization

14.6 kB

  • HTML
  • CSS

In fact, the total size of Egos.io main page is 93.4 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. Only 10% of websites need less resources to load. HTML takes 80.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 66.4 kB

  • Original 80.3 kB
  • After minification 70.8 kB
  • After compression 14.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. This page needs HTML code to be minified as it can gain 9.6 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 66.4 kB or 83% of the original size.

CSS Optimization

-95%

Potential reduce by 12.4 kB

  • Original 13.0 kB
  • After minification 654 B
  • After compression 594 B

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Egos.io needs all CSS files to be minified and compressed as it can save up to 12.4 kB or 95% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (17%)

Requests Now

18

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

egos.io

egos.io

35 ms

campaigntracker.io

campaigntracker.io

114 ms

style.css

style.css

14 ms

animate.css

animate.css

27 ms

wow.min.js

wow.min.js

28 ms

script.js

script.js

42 ms

main.js

main.js

41 ms

css2

css2

47 ms

gtm.js

gtm.js

141 ms

logo-white.svg

logo-white.svg

31 ms

imac.webp

imac.webp

125 ms

coingecko.webp

coingecko.webp

142 ms

spiffster.webp

spiffster.webp

151 ms

ncsu.webp

ncsu.webp

200 ms

crownjewelmarketing.webp

crownjewelmarketing.webp

205 ms

vizeo.webp

vizeo.webp

174 ms

ct-create-tagged-url.webp

ct-create-tagged-url.webp

178 ms

avatar-119582d9d04973e07e2bd75695ec146f.webp

avatar-119582d9d04973e07e2bd75695ec146f.webp

184 ms

avatar-11aa7c7c317701328aad5c66e3469d63.webp

avatar-11aa7c7c317701328aad5c66e3469d63.webp

164 ms

avatar-111f92b0a68921a8b3ad8a7eb7431e94.webp

avatar-111f92b0a68921a8b3ad8a7eb7431e94.webp

187 ms

Accessibility Review

egos.io accessibility score

75

Accessibility Issues

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

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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 IDs are not unique

Best Practices

egos.io best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

egos.io SEO score

100

Search Engine Optimization Advices

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

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

egos.io

Open Graph data is detected on the main page of Egos. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: