Tools & Wizards About Us
swiftbrake.com screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

swiftbrake.com

Swift Brake and Clutch | Commercial Vehicle Spares | Texa Diagnostics

Page Load Speed

1.7 sec in total

First Response

291 ms

Resources Loaded

1.2 sec

Page Rendered

164 ms

swiftbrake.com screenshot

About Website

Visit swiftbrake.com now to see the best up-to-date Swift Brake content and also check out these interesting facts you probably never knew about swiftbrake.com

We supply high quality commercial vehicle spare parts for truck, trailer, bus, car and off-highway machines. We have a brake relining workshop and are the North East dealer for Texa diagnostic tools.

Visit swiftbrake.com

Key Findings

We analyzed Swiftbrake.com page load time and found that the first response time was 291 ms and then it took 1.4 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

swiftbrake.com performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

swiftbrake.com

291 ms

global.js

146 ms

font-awesome.min.css

222 ms

jquery.1.7.2.min.js

368 ms

mobilemenu.js

149 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 79% of them (42 requests) were addressed to the original Swiftbrake.com, 15% (8 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (552 ms) belongs to the original domain Swiftbrake.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 232.7 kB (35%)

Content Size

669.8 kB

After Optimization

437.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Swiftbrake.com main page is 669.8 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. 45% of websites need less resources to load. Images take 341.2 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 27.6 kB

  • Original 33.2 kB
  • After minification 31.5 kB
  • After compression 5.6 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 27.6 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 329 B

  • Original 341.2 kB
  • After minification 340.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. Swift Brake images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 100.5 kB

  • Original 172.2 kB
  • After minification 168.6 kB
  • After compression 71.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 100.5 kB or 58% of the original size.

CSS Optimization

-85%

Potential reduce by 104.2 kB

  • Original 123.2 kB
  • After minification 104.2 kB
  • After compression 19.0 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. Swiftbrake.com needs all CSS files to be minified and compressed as it can save up to 104.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (33%)

Requests Now

43

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

swiftbrake.com

swiftbrake.com

291 ms

global.js

global.js

146 ms

font-awesome.min.css

font-awesome.min.css

222 ms

jquery.1.7.2.min.js

jquery.1.7.2.min.js

368 ms

mobilemenu.js

mobilemenu.js

149 ms

googlefont.js

googlefont.js

148 ms

oo_base_min.js

oo_base_min.js

226 ms

oo_dhtml_min.js

oo_dhtml_min.js

219 ms

image_preview.js

image_preview.js

224 ms

core.css

core.css

297 ms

page269464.css

page269464.css

294 ms

image_preview.css

image_preview.css

295 ms

sbcookieconsent.css

sbcookieconsent.css

296 ms

sbcookieconsent.js

sbcookieconsent.js

234 ms

webfont.js

webfont.js

58 ms

swiftbrake.jpg

swiftbrake.jpg

108 ms

swiftbrake-logo.jpg

swiftbrake-logo.jpg

109 ms

layout_bg.jpg

layout_bg.jpg

375 ms

spacer.gif

spacer.gif

110 ms

image_2261696.jpg

image_2261696.jpg

109 ms

logo_2262653.jpg

logo_2262653.jpg

109 ms

2119889.15519.jpg

2119889.15519.jpg

155 ms

2119890.15519.jpg

2119890.15519.jpg

156 ms

2119891.15519.jpg

2119891.15519.jpg

157 ms

fade.png

fade.png

158 ms

f_shapes.hexagon-rounded_ffffff_ffffff.png

f_shapes.hexagon-rounded_ffffff_ffffff.png

157 ms

2119887.15518.jpg

2119887.15518.jpg

229 ms

2119886.15518.jpg

2119886.15518.jpg

229 ms

2119885.15518.jpg

2119885.15518.jpg

230 ms

2119884.15518.jpg

2119884.15518.jpg

231 ms

2119883.15518.jpg

2119883.15518.jpg

234 ms

2119882.15518.jpg

2119882.15518.jpg

303 ms

2119881.15518.jpg

2119881.15518.jpg

304 ms

image_2261675.jpg

image_2261675.jpg

304 ms

image_2261676.jpg

image_2261676.jpg

305 ms

image_2261653.jpg

image_2261653.jpg

310 ms

image_2261655.jpg

image_2261655.jpg

377 ms

image_2261659.jpg

image_2261659.jpg

377 ms

image_2261665.jpg

image_2261665.jpg

377 ms

image_2261658.jpg

image_2261658.jpg

378 ms

image_2228677.jpg

image_2228677.jpg

386 ms

info-default-bg.gif

info-default-bg.gif

447 ms

ga.js

ga.js

8 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

552 ms

css

css

22 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf

6 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8Jow.ttf

16 ms

va9b4kzIxd1KFppkaRKvDRPJVDf_vB_ekGrW.ttf

va9b4kzIxd1KFppkaRKvDRPJVDf_vB_ekGrW.ttf

17 ms

va9b4kzIxd1KFppkaRKvDRPJVDf_WxjekGrW.ttf

va9b4kzIxd1KFppkaRKvDRPJVDf_WxjekGrW.ttf

16 ms

QGY9z_wNahGAdqQ43Rh_ebrnlwyYfEPxPoGU3ms5pIfd.ttf

QGY9z_wNahGAdqQ43Rh_ebrnlwyYfEPxPoGU3ms5pIfd.ttf

17 ms

QGY9z_wNahGAdqQ43Rh_ebrnlwyYfEPxPoGUOWw5pIfd.ttf

QGY9z_wNahGAdqQ43Rh_ebrnlwyYfEPxPoGUOWw5pIfd.ttf

17 ms

va9Z4kzIxd1KFrBtW-13ZHhT-jDqdFwG1FrRPXk.ttf

va9Z4kzIxd1KFrBtW-13ZHhT-jDqdFwG1FrRPXk.ttf

27 ms

va9Z4kzIxd1KFrBtW-13ZHhT-jDqdFzh01rRPXk.ttf

va9Z4kzIxd1KFrBtW-13ZHhT-jDqdFzh01rRPXk.ttf

85 ms

Accessibility Review

swiftbrake.com accessibility score

80

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

Links do not have a discernible name

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

swiftbrake.com SEO score

90

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

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

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 Swiftbrake.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 Swiftbrake.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

swiftbrake.com

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