Tools & Wizards About Us
tracks.co screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

tracks.co

Tracks | Discover music and events. Find your tickets

Page Load Speed

3.7 sec in total

First Response

192 ms

Resources Loaded

2.9 sec

Page Rendered

568 ms

tracks.co screenshot

About Website

Welcome to tracks.co homepage info - get ready to check Tracks best content for France right away, or after learning these important things about tracks.co

Tracks on Tracks.co, a smarter way to discover music and events for artists and music lovers. Find your tickets

Visit tracks.co

Key Findings

We analyzed Tracks.co page load time and found that the first response time was 192 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

tracks.co performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.3 s

0/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value12,360 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value26.4 s

0/100

10%

Network Requests Diagram

tracks.co

192 ms

tracks.co

403 ms

tracks.min.css

189 ms

tracks-bower.min.js

662 ms

tracks-app.min.js

485 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 50% of them (33 requests) were addressed to the original Tracks.co, 8% (5 requests) were made to Maps.googleapis.com and 6% (4 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (899 ms) belongs to the original domain Tracks.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 682.4 kB (43%)

Content Size

1.6 MB

After Optimization

899.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tracks.co main page is 1.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 655.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 42.2 kB

  • Original 52.7 kB
  • After minification 40.4 kB
  • After compression 10.5 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 12.3 kB, which is 23% 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 42.2 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 737 B

  • Original 608.6 kB
  • After minification 607.9 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. Tracks images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 420.6 kB

  • Original 655.2 kB
  • After minification 655.2 kB
  • After compression 234.6 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 420.6 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 218.9 kB

  • Original 265.3 kB
  • After minification 265.1 kB
  • After compression 46.5 kB

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. Tracks.co needs all CSS files to be minified and compressed as it can save up to 218.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (41%)

Requests Now

56

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tracks.co

tracks.co

192 ms

tracks.co

tracks.co

403 ms

tracks.min.css

tracks.min.css

189 ms

tracks-bower.min.js

tracks-bower.min.js

662 ms

tracks-app.min.js

tracks-app.min.js

485 ms

twemoji.min.js

twemoji.min.js

38 ms

bootstrap.min.css

bootstrap.min.css

117 ms

font-awesome.min.css

font-awesome.min.css

213 ms

fontastic.min.css

fontastic.min.css

274 ms

papaparse.min.js

papaparse.min.js

90 ms

analytics.js

analytics.js

93 ms

sdk.js

sdk.js

46 ms

connect.html

connect.html

199 ms

modalAddEvent.html

modalAddEvent.html

129 ms

genericModal.html

genericModal.html

230 ms

authenticate

authenticate

254 ms

menu.html

menu.html

233 ms

musicPlayer.html

musicPlayer.html

899 ms

landing.html

landing.html

274 ms

1503923369.woff

1503923369.woff

76 ms

collect

collect

24 ms

collect

collect

51 ms

32 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

27 ms

ga-audiences

ga-audiences

149 ms

js

js

759 ms

api.js

api.js

700 ms

loader.html

loader.html

714 ms

fbReg.html

fbReg.html

727 ms

56_gold.png

56_gold.png

690 ms

41691970

41691970

688 ms

gotham-thin-webfont.woff

gotham-thin-webfont.woff

671 ms

120_white.png

120_white.png

228 ms

play.jpg

play.jpg

303 ms

profile.png

profile.png

391 ms

headphones_discreet.jpg

headphones_discreet.jpg

350 ms

mac.jpg

mac.jpg

336 ms

suit.jpg

suit.jpg

263 ms

girl.jpg

girl.jpg

454 ms

soundsymbol-0.svg

soundsymbol-0.svg

357 ms

soundsymbol-1.svg

soundsymbol-1.svg

354 ms

soundsymbol-2.svg

soundsymbol-2.svg

416 ms

soundsymbol-3.svg

soundsymbol-3.svg

419 ms

soundsymbol-4.svg

soundsymbol-4.svg

418 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

515 ms

recaptcha__en.js

recaptcha__en.js

151 ms

common.js

common.js

68 ms

util.js

util.js

105 ms

controls.js

controls.js

102 ms

places_impl.js

places_impl.js

102 ms

XdyCMhTiZ4u9_m.json

XdyCMhTiZ4u9_m.json

172 ms

artworks-000241214943-ljur0p-t500x500.jpg

artworks-000241214943-ljur0p-t500x500.jpg

197 ms

15027749_1230946230312669_665777679146414873_n.jpg

15027749_1230946230312669_665777679146414873_n.jpg

117 ms

18034264_1381302175261963_1019256685094986449_n.jpg

18034264_1381302175261963_1019256685094986449_n.jpg

115 ms

1003075_10152058393187821_7888490620303712835_n.jpg

1003075_10152058393187821_7888490620303712835_n.jpg

114 ms

14705807_1317817748251814_8730433090888463197_n.jpg

14705807_1317817748251814_8730433090888463197_n.jpg

113 ms

powered-by-google-on-white3.png

powered-by-google-on-white3.png

102 ms

autocomplete-icons.png

autocomplete-icons.png

141 ms

fallback

fallback

49 ms

fallback__ltr.css

fallback__ltr.css

4 ms

css

css

53 ms

logo_48.png

logo_48.png

17 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

53 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

52 ms

collect

collect

18 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

6 ms

Accessibility Review

tracks.co accessibility score

65

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tracks.co best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

tracks.co SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

tracks.co

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