Tools & Wizards About Us
forcor.com.ar screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

forcor.com.ar

Repuestos Ford - Concesionaria Oficial Ford - Forcor S.A

Page Load Speed

3.4 sec in total

First Response

431 ms

Resources Loaded

2.7 sec

Page Rendered

254 ms

forcor.com.ar screenshot

About Website

Click here to check amazing Forcor content for Argentina. Otherwise, check out these important facts you probably never knew about forcor.com.ar

Concesionaria oficial de Ford. Repuestos Ford. Ventas en Córdoba Capital, Hernando y Buenos Aires. Desde 1963 en Argentina - Forcor S.A.

Visit forcor.com.ar

Key Findings

We analyzed Forcor.com.ar page load time and found that the first response time was 431 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

forcor.com.ar performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value4,930 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.089

92/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

forcor.com.ar

431 ms

www.forcor.com.ar

241 ms

gtm.js

70 ms

bootstrap.min.css

42 ms

style.css

204 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 91% of them (107 requests) were addressed to the original Forcor.com.ar, 3% (3 requests) were made to Use.fontawesome.com and 2% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (786 ms) belongs to the original domain Forcor.com.ar.

Page Optimization Overview & Recommendations

Page size can be reduced by 402.0 kB (33%)

Content Size

1.2 MB

After Optimization

813.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Forcor.com.ar main page is 1.2 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. Javascripts take 584.1 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 70.3 kB

  • Original 83.4 kB
  • After minification 83.4 kB
  • After compression 13.1 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 70.3 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 541.0 kB
  • After minification 541.0 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. Forcor images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 331.7 kB

  • Original 584.1 kB
  • After minification 584.1 kB
  • After compression 252.4 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 331.7 kB or 57% of the original size.

CSS Optimization

-1%

Potential reduce by 62 B

  • Original 7.0 kB
  • After minification 7.0 kB
  • After compression 6.9 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. Forcor.com.ar has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 83 (76%)

Requests Now

109

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forcor.com.ar

forcor.com.ar

431 ms

www.forcor.com.ar

www.forcor.com.ar

241 ms

gtm.js

gtm.js

70 ms

bootstrap.min.css

bootstrap.min.css

42 ms

style.css

style.css

204 ms

cf7ic-style.css

cf7ic-style.css

57 ms

styles.css

styles.css

52 ms

prettyPhoto.min.css

prettyPhoto.min.css

55 ms

uacf7-frontend.css

uacf7-frontend.css

45 ms

form-style.css

form-style.css

82 ms

star-rating.css

star-rating.css

83 ms

all.css

all.css

84 ms

masterslider.main.css

masterslider.main.css

95 ms

custom.css

custom.css

87 ms

style.css

style.css

103 ms

um-modal.min.css

um-modal.min.css

115 ms

jquery-ui.min.css

jquery-ui.min.css

111 ms

tipsy.min.css

tipsy.min.css

113 ms

um-raty.min.css

um-raty.min.css

119 ms

select2.min.css

select2.min.css

623 ms

um-fileupload.min.css

um-fileupload.min.css

149 ms

um-confirm.min.css

um-confirm.min.css

137 ms

default.min.css

default.min.css

146 ms

default.date.min.css

default.date.min.css

148 ms

default.time.min.css

default.time.min.css

166 ms

fonticons-ii.min.css

fonticons-ii.min.css

176 ms

fonticons-fa.min.css

fonticons-fa.min.css

175 ms

um-fontawesome.min.css

um-fontawesome.min.css

205 ms

common.min.css

common.min.css

198 ms

um-responsive.min.css

um-responsive.min.css

203 ms

um-styles.min.css

um-styles.min.css

218 ms

cropper.min.css

cropper.min.css

224 ms

um-profile.min.css

um-profile.min.css

230 ms

um-account.min.css

um-account.min.css

223 ms

um-misc.min.css

um-misc.min.css

238 ms

um-old-default.min.css

um-old-default.min.css

246 ms

jquery.min.js

jquery.min.js

31 ms

infinite-scroll.pkgd.min.js

infinite-scroll.pkgd.min.js

248 ms

um-gdpr.min.js

um-gdpr.min.js

257 ms

api.js

api.js

39 ms

9a0b1a8e85.js

9a0b1a8e85.js

81 ms

api.js

api.js

58 ms

bootstrap.min.js

bootstrap.min.js

44 ms

rs6.css

rs6.css

257 ms

jquery.js

jquery.js

233 ms

forcor.js

forcor.js

230 ms

lazysizes.min.js

lazysizes.min.js

226 ms

index.js

index.js

245 ms

index.js

index.js

237 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

226 ms

underscore.min.js

underscore.min.js

220 ms

front.js

front.js

246 ms

rbtools.min.js

rbtools.min.js

239 ms

rs6.min.js

rs6.min.js

244 ms

scripts.js

scripts.js

230 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

244 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

250 ms

wp-polyfill.min.js

wp-polyfill.min.js

253 ms

index.js

index.js

245 ms

wp-util.min.js

wp-util.min.js

228 ms

hooks.min.js

hooks.min.js

241 ms

i18n.min.js

i18n.min.js

300 ms

tipsy.min.js

tipsy.min.js

249 ms

um-confirm.min.js

um-confirm.min.js

233 ms

picker.min.js

picker.min.js

224 ms

picker.date.min.js

picker.date.min.js

236 ms

picker.time.min.js

picker.time.min.js

241 ms

es_ES.min.js

es_ES.min.js

222 ms

common.min.js

common.min.js

228 ms

cropper.min.js

cropper.min.js

228 ms

common-frontend.min.js

common-frontend.min.js

229 ms

um-modal.min.js

um-modal.min.js

240 ms

jquery-form.min.js

jquery-form.min.js

241 ms

fileupload.js

fileupload.js

252 ms

um-functions.min.js

um-functions.min.js

241 ms

um-responsive.min.js

um-responsive.min.js

227 ms

um-conditional.min.js

um-conditional.min.js

246 ms

select2.full.min.js

select2.full.min.js

284 ms

es.js

es.js

237 ms

um-raty.min.js

um-raty.min.js

237 ms

um-scripts.min.js

um-scripts.min.js

242 ms

um-profile.min.js

um-profile.min.js

253 ms

um-account.min.js

um-account.min.js

237 ms

recaptcha__en.js

recaptcha__en.js

120 ms

fbevents.js

fbevents.js

90 ms

logo.svg

logo.svg

76 ms

bg-usados.png

bg-usados.png

363 ms

angleBottom.svg

angleBottom.svg

81 ms

bg-footer.jpg

bg-footer.jpg

80 ms

9a0b1a8e85.css

9a0b1a8e85.css

96 ms

fordantenna-regular-webfont_0-webfont.svg

fordantenna-regular-webfont_0-webfont.svg

83 ms

fordantenna-light-webfont_0-webfont.svg

fordantenna-light-webfont_0-webfont.svg

82 ms

FordAntenna-ExtraLight.svg

FordAntenna-ExtraLight.svg

85 ms

FordAntenna-Medium.svg

FordAntenna-Medium.svg

210 ms

FordAntenna-Semibold.svg

FordAntenna-Semibold.svg

84 ms

fordantenna-bold-webfont_0-webfont.svg

fordantenna-bold-webfont_0-webfont.svg

212 ms

fordantenna-black-webfont_0-webfont.svg

fordantenna-black-webfont_0-webfont.svg

211 ms

fa-solid-900.woff

fa-solid-900.woff

759 ms

fa-regular-400.woff

fa-regular-400.woff

209 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

211 ms

font-awesome-css.min.css

font-awesome-css.min.css

13 ms

FordAntenna-ExtraLight.woff

FordAntenna-ExtraLight.woff

115 ms

FordAntenna-Semibold.woff

FordAntenna-Semibold.woff

69 ms

FordAntenna-Medium.woff

FordAntenna-Medium.woff

786 ms

respuestos.jpg

respuestos.jpg

59 ms

ford-ranger-2023.jpg

ford-ranger-2023.jpg

59 ms

bronco.jpg

bronco.jpg

58 ms

ford-territory.jpg

ford-territory.jpg

60 ms

contacto.jpg

contacto.jpg

60 ms

territory-th-146x109.png

territory-th-146x109.png

559 ms

th-f-bronco-146x109.png

th-f-bronco-146x109.png

107 ms

ford-kuga-hibrida-146x109.png

ford-kuga-hibrida-146x109.png

107 ms

ford-maverick-146x109.png

ford-maverick-146x109.png

570 ms

ranger-th-2023-146x109.png

ranger-th-2023-146x109.png

601 ms

nva-ra-raptor-th-146x109.png

nva-ra-raptor-th-146x109.png

637 ms

nva-f150-r-th-146x109.png

nva-f150-r-th-146x109.png

754 ms

th-f-150-146x109.png

th-f-150-146x109.png

379 ms

Accessibility Review

forcor.com.ar accessibility score

61

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible 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.

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

forcor.com.ar best practices score

83

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

SEO Factors

forcor.com.ar SEO score

84

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forcor.com.ar can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Forcor.com.ar 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

forcor.com.ar

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