1.7 sec in total
100 ms
1.3 sec
332 ms
Welcome to gescan.com homepage info - get ready to check Gescan best content for Canada right away, or after learning these important things about gescan.com
Electrical supplies, Electrical Wholesaler, Electrical distributor in Canada. Electrical supply for Residential, Commercial, and Industrial projects.
Visit gescan.comWe analyzed Gescan.com page load time and found that the first response time was 100 ms and then it took 1.6 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.
gescan.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value10.8 s
0/100
25%
Value10.3 s
9/100
10%
Value2,930 ms
3/100
30%
Value1.048
2/100
15%
Value26.8 s
1/100
10%
100 ms
246 ms
167 ms
158 ms
160 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Gescan.com, 73% (46 requests) were made to Cdn.gescan.com and 3% (2 requests) were made to Survey.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (357 ms) relates to the external source Google-analytics.com.
Page size can be reduced by 976.4 kB (57%)
1.7 MB
730.9 kB
In fact, the total size of Gescan.com 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. 50% of websites need less resources to load. Javascripts take 913.1 kB which makes up the majority of the site volume.
Potential reduce by 91.5 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 28.8 kB, which is 27% 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 91.5 kB or 87% of the original size.
Potential reduce by 30.6 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. Gescan images are well optimized though.
Potential reduce by 623.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 623.4 kB or 68% of the original size.
Potential reduce by 230.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. Gescan.com needs all CSS files to be minified and compressed as it can save up to 230.9 kB or 85% of the original size.
Number of requests can be reduced by 18 (33%)
54
36
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gescan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
gescan.com
100 ms
www.gescan.com
246 ms
785a2c0ce586021a9a5c5e0f992da0cd.css
167 ms
741698e320fae4095cd61833a1ebfdb0.css
158 ms
bc72ea0920ef5f6f978ec4f1973b75d2.css
160 ms
840d26bd559dd1633cda42ffb23d92af.js
208 ms
fe960bb48ec53262fc377a141a6f7ce4.js
191 ms
fb9a80675eb9a2d3311db505ecc80975.js
191 ms
c37af562a3d8a41d3ae7004fcf572928.js
192 ms
bd41e8e794f38a81749f24ef040ff428.js
193 ms
a98aca91188d78ea663600dfa2a5f2b8.js
193 ms
077f3af3ae19a0c114673f2fb5859c10.js
195 ms
async_survey
131 ms
conversion.js
40 ms
d5fea06c9332bbcff35f608bd6f7d6b1.js
331 ms
fbevents.js
294 ms
prum.min.js
331 ms
blank.gif
124 ms
logo.png
123 ms
gescan_logo_mobile.png
123 ms
slider_2.jpg
275 ms
lithonia_2.jpg
118 ms
prompt_embed_static.js
278 ms
analytics.js
357 ms
281 ms
gescan.ttf
174 ms
Oswald-Regular.woff
173 ms
Oswald-Light.woff
171 ms
Oswald-Bold.woff
205 ms
2ed81787-b55f-46b2-ae83-a244faf0afc3.js
262 ms
g-spot.gif
85 ms
credit-app-rotating-banner_1.jpg
89 ms
philips_9.jpg
88 ms
lithonia_6.jpg
89 ms
credit-app.png
84 ms
485x97-fluke.jpg
82 ms
nwua0j-t-b-bs2-tcvbc-image_1.jpg
250 ms
nzoxuk-t-b-be1-tcv-image_1.jpg
231 ms
o33c5v-stanpro-rmpn0whib-image_1.jpg
232 ms
nxjath-legrand-wp3402wh10-image_1.jpg
230 ms
o33cyg-philips-458380-image_1.jpg
253 ms
naro0g-kidde-900-0133-image_1.jpg
230 ms
nvz3jn-stanpro-stnvt4f2t8032w-image_1.jpg
253 ms
ngoztt-legrand-co1045-image_1.jpg
252 ms
nx7juz-philips-453597-image_1.png
251 ms
o2yc5a-acuity-225nyu-image_1.jpg
251 ms
nkeh0p-kidde-900-0119-image_1.jpg
265 ms
nvz6cu-t-b-st050-464-image_1.jpg
290 ms
nd7clo-legrand-wp3475-wh-image_1.jpg
278 ms
nmtm3q-acuity-184ch2-image_1.jpg
280 ms
nvx2ob-philips-456566-image_1.jpg
277 ms
legrand_4.jpg
289 ms
philips-vendor-banner.jpg
282 ms
stanpro_1.jpg
310 ms
kidde.jpg
308 ms
tnb.jpg
307 ms
258 ms
widget_v2.132.js
97 ms
collect
147 ms
172 ms
collect
73 ms
eaabeb7623228b7fee405700c24eedb2.css
20 ms
ga-audiences
17 ms
gescan.com 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
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.
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
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
gescan.com 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
Registers an unload listener
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
gescan.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gescan.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Gescan.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.
gescan.com
Open Graph description is not detected on the main page of Gescan. 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: