Tools & Wizards About Us
trek.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

trek.com

Trek Bikes - The world's best bikes and cycling gear

Page Load Speed

1.6 sec in total

First Response

54 ms

Resources Loaded

1.4 sec

Page Rendered

65 ms

trek.com screenshot

About Website

Visit trek.com now to see the best up-to-date Trek content for United States and also check out these interesting facts you probably never knew about trek.com

Discover the fun of riding with our wide range of electric, mountain, road, city, gravel, kids', and certified pre-owned bikes. Shop online or in-store!

Visit trek.com

Key Findings

We analyzed Trek.com page load time and found that the first response time was 54 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

trek.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value18.5 s

0/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value10,250 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.172

69/100

15%

TTI (Time to Interactive)

Value37.7 s

0/100

10%

Network Requests Diagram

trek.com

54 ms

trek.com

38 ms

88 ms

gtm.js

89 ms

common_start.9f395328.js

21 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Trek.com, 49% (19 requests) were made to Trekbikes.com and 10% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (618 ms) relates to the external source Static.cloudflareinsights.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 600.5 kB (61%)

Content Size

978.5 kB

After Optimization

378.0 kB

  • HTML
  • JavaScript

In fact, the total size of Trek.com main page is 978.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 665.8 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 591.1 kB

  • Original 665.8 kB
  • After minification 664.4 kB
  • After compression 74.7 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 591.1 kB or 89% of the original size.

JavaScript Optimization

-3%

Potential reduce by 9.4 kB

  • Original 312.7 kB
  • After minification 312.7 kB
  • After compression 303.3 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 22 (96%)

Requests Now

23

After Optimization

1

  • JavaScript

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

Network Requests Diagram

trek.com

trek.com

54 ms

trek.com

trek.com

38 ms

88 ms

gtm.js

gtm.js

89 ms

common_start.9f395328.js

common_start.9f395328.js

21 ms

legacy-base-vendors.809067c9.js

legacy-base-vendors.809067c9.js

40 ms

pedal-package.5c63ba89.js

pedal-package.5c63ba89.js

49 ms

vuejs-package.a535fa14.js

vuejs-package.a535fa14.js

37 ms

vendors.a151cd18.js

vendors.a151cd18.js

50 ms

chunk-common.41b56045.js

chunk-common.41b56045.js

59 ms

homepage_b2c_electra.72c24751.js

homepage_b2c_electra.72c24751.js

47 ms

common_end.2107b4b9.js

common_end.2107b4b9.js

58 ms

en.js

en.js

61 ms

uc.js

uc.js

98 ms

lightbox_inline.js

lightbox_inline.js

54 ms

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

618 ms

lightbox.js

lightbox.js

42 ms

bat.js

bat.js

171 ms

destination

destination

83 ms

destination

destination

125 ms

fbevents.js

fbevents.js

422 ms

client.js

client.js

428 ms

user.js

user.js

334 ms

js

js

126 ms

msei-0.min.js

msei-0.min.js

401 ms

roboto-v18-latin-ext-regular.d212a36a.woff

roboto-v18-latin-ext-regular.d212a36a.woff

93 ms

roboto-v18-latin-regular.8ae5c1b7.woff

roboto-v18-latin-regular.8ae5c1b7.woff

94 ms

roboto-v18-latin-ext-500.b5fcc695.woff

roboto-v18-latin-ext-500.b5fcc695.woff

93 ms

roboto-v18-latin-500.8382d75c.woff

roboto-v18-latin-500.8382d75c.woff

92 ms

roboto-v18-latin-ext-300.ee73c5c8.woff

roboto-v18-latin-ext-300.ee73c5c8.woff

93 ms

roboto-v18-latin-300.fc7fdc02.woff

roboto-v18-latin-300.fc7fdc02.woff

93 ms

roboto-v18-latin-ext-700.c52f983f.woff

roboto-v18-latin-ext-700.c52f983f.woff

384 ms

roboto-v18-latin-700.770e249a.woff

roboto-v18-latin-700.770e249a.woff

387 ms

main.js

main.js

105 ms

generic

generic

100 ms

pixel

pixel

34 ms

pixel

pixel

15 ms

google

google

4 ms

rubicon

rubicon

5 ms

Accessibility Review

trek.com accessibility score

91

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

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.

Best Practices

trek.com best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

trek.com SEO score

86

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

trek.com

Open Graph description is not detected on the main page of Trek. 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: