5.8 sec in total
882 ms
4.8 sec
133 ms
Click here to check amazing Farcol content. Otherwise, check out these important facts you probably never knew about farcol.pt
Comércio de equipamentos de protecção individual, EPIs. Luvas, calçado, vestuário, capacetes, auriculares, máscaras, filtros, viseiras e óculos de segurança.
Visit farcol.ptWe analyzed Farcol.pt page load time and found that the first response time was 882 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
farcol.pt performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value10.6 s
0/100
25%
Value8.9 s
15/100
10%
Value560 ms
52/100
30%
Value0.422
23/100
15%
Value10.5 s
23/100
10%
882 ms
105 ms
199 ms
322 ms
285 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 78% of them (53 requests) were addressed to the original Farcol.pt, 6% (4 requests) were made to Googletagmanager.com and 4% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (882 ms) belongs to the original domain Farcol.pt.
Page size can be reduced by 128.0 kB (9%)
1.3 MB
1.2 MB
In fact, the total size of Farcol.pt main page is 1.3 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. 65% of websites need less resources to load. Images take 907.5 kB which makes up the majority of the site volume.
Potential reduce by 37.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 5.1 kB, which is 11% 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 37.9 kB or 79% of the original size.
Potential reduce by 65.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. Farcol images are well optimized though.
Potential reduce by 20.1 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.
Potential reduce by 5.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. Farcol.pt has all CSS files already compressed.
Number of requests can be reduced by 40 (63%)
64
24
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Farcol. 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 from 19 to 1 for CSS and as a result speed up the page load time.
index.php
882 ms
bootstrap.css
105 ms
captchaStyle.css
199 ms
font-awesome.min.css
322 ms
animate.min.css
285 ms
sppagebuilder.css
329 ms
camera.css
286 ms
css
40 ms
system.css
281 ms
template.css
297 ms
megamenu.css
374 ms
off-canvas.css
377 ms
font-awesome.min.css
379 ms
corporate.css
390 ms
maximenuck.php
456 ms
maximenuresponsiveck.css
460 ms
mod_vikcookiespolicy.css
506 ms
template.css
505 ms
jquery.min.js
571 ms
jquery-noconflict.js
508 ms
jquery-migrate.min.js
549 ms
jquery.easing.1.3.js
553 ms
camera.js
695 ms
sppagebuilder.js
743 ms
bootstrap.js
606 ms
jquery.tap.min.js
679 ms
off-canvas.js
646 ms
script.js
701 ms
menu.js
699 ms
nav-collapse.js
739 ms
jquery.ui.core.min.js
775 ms
maximenuck.js
823 ms
api.js
40 ms
style.css
793 ms
js
59 ms
system.css
519 ms
trustlogo.js
62 ms
recaptcha__en.js
52 ms
Farcol_Logo.jpg
190 ms
pt_pt.gif
154 ms
en.gif
153 ms
search.png
181 ms
medic-p2.jpg
188 ms
casaco_av_parda_amarelo.jpg
188 ms
luva_hyflex_11-800.jpg
299 ms
arnes_antiqueda_Kratos_Confort_FA10206XX.jpg
369 ms
capacete_ps55whr.jpg
377 ms
oculos_evacana9.jpg
397 ms
auricular_mx340.jpg
376 ms
fato_macaco_weeback_01.jpg
378 ms
Bota_focus_20.jpg
462 ms
fontawesome-webfont.woff
530 ms
fontawesome-webfont.woff
596 ms
gtm.js
59 ms
seal_bg.gif
98 ms
warranty_level.gif
29 ms
comodo_secure_seal_113x59_transp.png
324 ms
camera-loader.gif
371 ms
lanterna_raibow1_home.jpg
495 ms
js
59 ms
js
134 ms
39 ms
37 ms
17 ms
20 ms
17 ms
sapato_ms100_home.jpg
249 ms
blank.gif
141 ms
farcol.pt accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
farcol.pt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
farcol.pt SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document doesn't use legible font sizes
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Farcol.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Farcol.pt 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.
farcol.pt
Open Graph description is not detected on the main page of Farcol. 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: