2.2 sec in total
127 ms
1.5 sec
576 ms
Click here to check amazing Gillette content for Canada. Otherwise, check out these important facts you probably never knew about gillette.ca
Experience an exceptional shave with Gillette men's razors, engineered to give you a comfortably smooth shave every time. Shop shaving products & more!
Visit gillette.caWe analyzed Gillette.ca page load time and found that the first response time was 127 ms and then it took 2 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.
gillette.ca performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value21.4 s
0/100
25%
Value21.7 s
0/100
10%
Value47,110 ms
0/100
30%
Value0.033
100/100
15%
Value71.4 s
0/100
10%
127 ms
299 ms
249 ms
223 ms
197 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 5% of them (5 requests) were addressed to the original Gillette.ca, 92% (97 requests) were made to Cdn.voyager.pgsitecore.com and 1% (1 request) were made to S.btstatic.com. The less responsive or slowest element that took the longest time to load (477 ms) relates to the external source Cdn.voyager.pgsitecore.com.
Page size can be reduced by 245.2 kB (28%)
866.9 kB
621.8 kB
In fact, the total size of Gillette.ca main page is 866.9 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. 55% of websites need less resources to load. Images take 665.6 kB which makes up the majority of the site volume.
Potential reduce by 124.0 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 38.7 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 124.0 kB or 87% of the original size.
Potential reduce by 79.5 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. Obviously, Gillette needs image optimization as it can save up to 79.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 41.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 41.7 kB or 71% of the original size.
Number of requests can be reduced by 62 (61%)
101
39
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gillette. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
gillette.ca
127 ms
en-ca
299 ms
globalltr
249 ms
sitemaster
223 ms
sitelocale
197 ms
WebResource.axd
88 ms
ScriptResource.axd
110 ms
ScriptResource.axd
101 ms
commonscript
51 ms
adblock.js
35 ms
desktop
272 ms
siteroot
197 ms
tag.js
24 ms
async-ads.js
263 ms
logo-pgestore.png
96 ms
logo-oralb.png
99 ms
Logo-Braun-DT.png
103 ms
ModalDialogClose.png
99 ms
flag-china_EN-CA_April28th2015.png
101 ms
flag-india_EN-CA_April28th2015.png
98 ms
flag-japan_EN-CA_April28th2015.png
102 ms
flag-kingdom-of-saudi-arabia_EN-CA_April28th2015.png
105 ms
flag-malaysia_EN-CA_April28th2015.png
105 ms
flag-middle-east_EN-CA_April28th2015.png
103 ms
flag-republic-of-korea_EN-CA_April28th2015.png
107 ms
flag-singapore_EN-CA_April28th2015.png
106 ms
flag-taiwan_EN-CA_April28th2015.png
108 ms
flag-thailand_EN-CA_April28th2015.png
108 ms
flag-united-arab-emirates_EN-CA_April28th2015.png
108 ms
flag-yemen_EN-CA_April28th2015.png
111 ms
flag-costa-rica_EN-CA_April28th2015.png
241 ms
flag-el-salvador_EN-CA_April28th2015.png
242 ms
flag-guatemala_EN-CA_April28th2015.png
243 ms
flag-honduras_EN-CA_April28th2015.png
246 ms
flag-nicaragua_EN-CA_April28th2015.png
245 ms
flag-panama_EN-CA_April28th2015.png
246 ms
flag-czech-republic_EN-CA_April28th2015.png
245 ms
flag-hungary_EN-CA_April28th2015.png
245 ms
flag-kazakhstan_EN-CA_April28th2015.png
246 ms
flag-poland_EN-CA_April28th2015.png
249 ms
flag-russian-federation_EN-CA_April28th2015.png
249 ms
flag-turkey_EN-CA_April28th2015.png
247 ms
flag-canada_EN-CA_April28th2015.png
247 ms
flag-mexico_EN-CA_April28th2015.png
248 ms
flag-puerto-rico_EN-CA_April28th2015.png
325 ms
flag-united-states_EN-CA_April28th2015.png
325 ms
flag-australia_EN-CA_April28th2015.png
328 ms
flag-new-zealand_EN-CA_April28th2015.png
325 ms
flag-argentina_EN-CA_April28th2015.png
251 ms
flag-bolivia_EN-CA_April28th2015.png
247 ms
flag-brazil_EN-CA_April28th2015.png
252 ms
flag-chile_EN-CA_April28th2015.png
254 ms
flag-colombia_EN-CA_April28th2015.png
252 ms
flag-ecuador_EN-CA_April28th2015.png
247 ms
flag-paraguay_EN-CA_April28th2015.png
246 ms
flag-peru_EN-CA_April28th2015.png
246 ms
flag-uraguay_EN-CA_April28th2015.png
248 ms
flag-venezuela_EN-CA_April28th2015.png
250 ms
flag-austria_EN-CA_April28th2015.png
247 ms
flag-belgium_EN-CA_April28th2015.png
247 ms
flag-france_EN-CA_April28th2015.png
249 ms
flag-germany_EN-CA_April28th2015.png
247 ms
flag-great-britain_EN-CA_April28th2015.png
246 ms
flag-greece_EN-CA_April28th2015.png
305 ms
flag-ireland_EN-CA_April28th2015.png
303 ms
flag-italy_EN-CA_April28th2015.png
174 ms
flag-portugal_EN-CA_April28th2015.png
176 ms
flag-spain_EN-CA_April28th2015.png
175 ms
flag-switzerland_EN-CA_April28th2015.png
171 ms
flag-netherlands_EN-CA_April28th2015.png
172 ms
logo-adchoices.png
174 ms
gillette-logo_En-CA_April15th2015.png
174 ms
SearchBoxImage.png
174 ms
GIL_US-EN_DT_NAV-DROP-DOWN-Razors-Blades.jpg
352 ms
Pillars-Families-PrePostShave_Aug2015.jpg
354 ms
menu-db.jpg
355 ms
Homepage%20Carousel%20Feb1.jpg
357 ms
00HomeCarouselGSCDT.jpg
364 ms
00HomeCarouselMACH3ENCADTFEB2015.jpg
353 ms
futuraeftuop-book-webfont-woff.woff
350 ms
iframe_api
279 ms
futuraeftuop-medium-webfont-woff.woff
277 ms
futuraeftuop-demibold-webfont-woff.woff
276 ms
GIL_US-EN-DT-HMP-RB-PILLAR_1dec2015.png
281 ms
home-pillar2_FEB2015-optimizedJULY2015.jpg
275 ms
home-pillar3_July2015.jpg
275 ms
GIL_CA-EN_DT_HMP_436_PILLAR_04.jpg
274 ms
GIL_CA-EN_DT_HMP_436_SUBSCRIPTION_2_4_16.jpg
292 ms
gillette-home-youtube-EN_July_2015.jpg
291 ms
gillette-callout-home-facial-hair-styles_July2015.jpg
290 ms
icon-social-fb.png
283 ms
icon-social-tw.png
282 ms
icon-social-yt.png
290 ms
icon-social-gp.png
475 ms
bbb-logo_En-CA_April15th2015.png
477 ms
header-bcgr.png
475 ms
arrow-topnav-off.png
471 ms
btn-arrow.png
474 ms
page_2on.png
471 ms
page_2off.png
421 ms
arrow_left.png
420 ms
arrowright.png
417 ms
footer_gradent.png
415 ms
tag
171 ms
arrow_subnav_post_right.png
230 ms
promobtn-bg.png
231 ms
gillette.ca 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
gillette.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
gillette.ca 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gillette.ca 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 Gillette.ca 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.
gillette.ca
Open Graph description is not detected on the main page of Gillette. 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: