Tools & Wizards About Us
caferacer.net screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

caferacer.net

Cafe Racer Forum

Page Load Speed

2.2 sec in total

First Response

344 ms

Resources Loaded

1.5 sec

Page Rendered

362 ms

caferacer.net screenshot

About Website

Click here to check amazing Cafe Racer content for United States. Otherwise, check out these important facts you probably never knew about caferacer.net

A forum community dedicated to Cafe Racer style race bikes owners and enthusiasts. Come join the discussion about restoration, performance, racing...

Visit caferacer.net

Key Findings

We analyzed Caferacer.net page load time and found that the first response time was 344 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

caferacer.net performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value3,040 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value32.4 s

0/100

10%

Network Requests Diagram

www.caferacer.net

344 ms

css2

76 ms

lux.js

67 ms

lazysizes.min.js

52 ms

css.php

53 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 75% of them (77 requests) were addressed to the original Caferacer.net, 9% (9 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Config.htplayground.com. The less responsive or slowest element that took the longest time to load (672 ms) belongs to the original domain Caferacer.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 222.7 kB (13%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Caferacer.net main page is 1.7 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. 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. Images take 820.2 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 142.1 kB

  • Original 161.0 kB
  • After minification 141.2 kB
  • After compression 18.9 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 19.8 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 142.1 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 3.4 kB

  • Original 820.2 kB
  • After minification 816.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. Cafe Racer images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 77.3 kB

  • Original 726.0 kB
  • After minification 725.9 kB
  • After compression 648.7 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 77.3 kB or 11% of the original size.

CSS Optimization

-0%

Potential reduce by 12 B

  • Original 2.8 kB
  • After minification 2.8 kB
  • After compression 2.8 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. Caferacer.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 66 (73%)

Requests Now

90

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.caferacer.net

www.caferacer.net

344 ms

css2

css2

76 ms

lux.js

lux.js

67 ms

lazysizes.min.js

lazysizes.min.js

52 ms

css.php

css.php

53 ms

css.php

css.php

52 ms

css.php

css.php

56 ms

css.php

css.php

56 ms

css.php

css.php

50 ms

css.php

css.php

118 ms

css.php

css.php

63 ms

css.php

css.php

64 ms

css.php

css.php

63 ms

css.php

css.php

62 ms

css.php

css.php

115 ms

css.php

css.php

122 ms

css.php

css.php

123 ms

css.php

css.php

125 ms

css.php

css.php

124 ms

css.php

css.php

144 ms

css.php

css.php

116 ms

css.php

css.php

149 ms

css.php

css.php

137 ms

css.php

css.php

123 ms

css.php

css.php

128 ms

preamble.ts.907080ffb7051fef2dbd.js

preamble.ts.907080ffb7051fef2dbd.js

134 ms

apstag.js

apstag.js

61 ms

gpt.js

gpt.js

298 ms

data

data

64 ms

load-vs-cmp.js

load-vs-cmp.js

106 ms

caferacer.net

caferacer.net

285 ms

libs

libs

114 ms

flag-icon.min.css

flag-icon.min.css

133 ms

vendor-compiled.ts.62299a387a56864606b4.js

vendor-compiled.ts.62299a387a56864606b4.js

133 ms

core-compiled.js

core-compiled.js

135 ms

show_more.ts.68e09591c7e1385ec17c.js

show_more.ts.68e09591c7e1385ec17c.js

134 ms

california_featured_threads.ts.418b0d678c7a4c9a7243.js

california_featured_threads.ts.418b0d678c7a4c9a7243.js

133 ms

imagefeed.tsx.b4bd4d613d015b334c59.js

imagefeed.tsx.b4bd4d613d015b334c59.js

276 ms

ad_stack_hometalk.ts.f1a470b787153d85e73e.js

ad_stack_hometalk.ts.f1a470b787153d85e73e.js

135 ms

action-override.ts.15af7dcd1a2323ee568d.js

action-override.ts.15af7dcd1a2323ee568d.js

134 ms

california-gallery.ts.c21a837d2e0bcc719cc4.js

california-gallery.ts.c21a837d2e0bcc719cc4.js

134 ms

advanced-search-gtm.ts.8befec7617a4acc64776.js

advanced-search-gtm.ts.8befec7617a4acc64776.js

135 ms

header-gtm.ts.1e4a36ecb156718b788c.js

header-gtm.ts.1e4a36ecb156718b788c.js

138 ms

scroll-analytic.ts.42a9d1697cd7cf9d0834.js

scroll-analytic.ts.42a9d1697cd7cf9d0834.js

136 ms

core-override.ts.17c4c7d751a41f364eac.js

core-override.ts.17c4c7d751a41f364eac.js

132 ms

identity.ts.276ff63b490513779254.js

identity.ts.276ff63b490513779254.js

102 ms

hide-search.ts.8c70e1ff93fd473005ee.js

hide-search.ts.8c70e1ff93fd473005ee.js

102 ms

marketplace-gtm.ts.c05b5113d864a2678aed.js

marketplace-gtm.ts.c05b5113d864a2678aed.js

162 ms

autocomplete_search.ts.c447d05ae350fd050438.js

autocomplete_search.ts.c447d05ae350fd050438.js

162 ms

page-view-counter.ts.6c7689e5145fa0d66141.js

page-view-counter.ts.6c7689e5145fa0d66141.js

160 ms

desktop-adhesion-close.ts.3ee54f612de9f7130972.js

desktop-adhesion-close.ts.3ee54f612de9f7130972.js

161 ms

runtime.db367ecdd4c7b111f776.js

runtime.db367ecdd4c7b111f776.js

153 ms

structure-override.ts.26738dfbaafd7ff3fe8e.js

structure-override.ts.26738dfbaafd7ff3fe8e.js

153 ms

unregister-serviceworkers.ts.63ec51f854d745830847.js

unregister-serviceworkers.ts.63ec51f854d745830847.js

154 ms

tooltip-override.ts.7a2bc65662802ef419f9.js

tooltip-override.ts.7a2bc65662802ef419f9.js

153 ms

281 ms

form-override.ts.5e4145ac0b821155d537.js

form-override.ts.5e4145ac0b821155d537.js

187 ms

override-notice-enable-push.ts.97ee5b6bcf795115c122.js

override-notice-enable-push.ts.97ee5b6bcf795115c122.js

187 ms

california-time.ts.c5b727205a1c56e0c4ff.js

california-time.ts.c5b727205a1c56e0c4ff.js

219 ms

gtm.js

gtm.js

324 ms

caferacer_net.svg

caferacer_net.svg

313 ms

onetap

onetap

296 ms

privacyoptions123x59.png

privacyoptions123x59.png

182 ms

avsforum_com_profile.png

avsforum_com_profile.png

272 ms

skyscrapercity_com_profile.png

skyscrapercity_com_profile.png

272 ms

dealsforum_com_profile.png

dealsforum_com_profile.png

322 ms

caferacer_net_banner_720w.jpg

caferacer_net_banner_720w.jpg

133 ms

restyled-thread-creation-icon.svg

restyled-thread-creation-icon.svg

130 ms

restyled-new-navigation-icon.svg

restyled-new-navigation-icon.svg

132 ms

restyled-forum-navigation-icon.svg

restyled-forum-navigation-icon.svg

133 ms

ellipsis-white-large.svg

ellipsis-white-large.svg

136 ms

login-icon-white.svg

login-icon-white.svg

138 ms

11304.jpg

11304.jpg

134 ms

discussion-icon-white.svg

discussion-icon-white.svg

134 ms

33472.jpg

33472.jpg

139 ms

button_light_secondary.svg

button_light_secondary.svg

158 ms

arrow-right-bleu.svg

arrow-right-bleu.svg

159 ms

4538.jpg

4538.jpg

157 ms

4522.jpg

4522.jpg

248 ms

8000.jpg

8000.jpg

157 ms

updated-fora-logo.svg

updated-fora-logo.svg

249 ms

bbb-logo.svg

bbb-logo.svg

250 ms

172 ms

176 ms

292 ms

672 ms

251 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZg.ttf

80 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZg.ttf

227 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZg.ttf

288 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfMZg.ttf

272 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeMZg.ttf

287 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf

271 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZg.ttf

271 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYMZg.ttf

287 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYMZg.ttf

288 ms

fa-solid-900-subset.v13.woff

fa-solid-900-subset.v13.woff

234 ms

fa-regular-400-subset.v13.woff

fa-regular-400-subset.v13.woff

246 ms

fa-light-300-subset.v13.woff

fa-light-300-subset.v13.woff

245 ms

pubads_impl.js

pubads_impl.js

39 ms

css.php

css.php

86 ms

client

client

133 ms

one_tap.ts.86ae79f1a96eb250d342.js

one_tap.ts.86ae79f1a96eb250d342.js

109 ms

Accessibility Review

caferacer.net accessibility score

87

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

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

caferacer.net 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

caferacer.net SEO score

88

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

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 Caferacer.net 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 Caferacer.net 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

caferacer.net

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