1.7 sec in total
135 ms
955 ms
645 ms
Visit pj.ca now to see the best up-to-date PJ content for Canada and also check out these interesting facts you probably never knew about pj.ca
Pour vos recherches d'entreprises, de produits et de services au Canada, PagesJaunes.ca (PJ.ca) offre toute l'information de l'annuaire téléphonique d'entreprises et plus: vidéos, photos, adresses cou...
Visit pj.caWe analyzed Pj.ca page load time and found that the first response time was 135 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.
pj.ca performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value6.9 s
6/100
25%
Value4.6 s
70/100
10%
Value9,500 ms
0/100
30%
Value0.097
90/100
15%
Value16.3 s
5/100
10%
135 ms
279 ms
19 ms
34 ms
17 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Pj.ca, 65% (39 requests) were made to Static.yellowpages.ca and 5% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (279 ms) relates to the external source Pagesjaunes.ca.
Page size can be reduced by 779.2 kB (43%)
1.8 MB
1.0 MB
In fact, the total size of Pj.ca main page is 1.8 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. Javascripts take 861.0 kB which makes up the majority of the site volume.
Potential reduce by 67.4 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 11.3 kB, which is 13% 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 67.4 kB or 79% of the original size.
Potential reduce by 4.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. PJ images are well optimized though.
Potential reduce by 561.5 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 561.5 kB or 65% of the original size.
Potential reduce by 146.2 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. Pj.ca needs all CSS files to be minified and compressed as it can save up to 146.2 kB or 83% of the original size.
Number of requests can be reduced by 17 (32%)
53
36
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PJ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
pj.ca
135 ms
www.pagesjaunes.ca
279 ms
yellowHome.css
19 ms
yellowpages-theme.css
34 ms
categories.css
17 ms
yellowHead.js
12 ms
jquery.js
38 ms
4383492553.js
57 ms
sidebar-yplogo-fr.svg
26 ms
logo-fr.svg
18 ms
logo-fr.svg
21 ms
mtl.jpg
47 ms
logo-fr.svg
25 ms
iconLogo-FR.svg
21 ms
ypmtl_03.07_ontario.jpg
26 ms
ypmtl_02.29_spectacles.jpg
25 ms
iconLogo-FR.svg
44 ms
feb16_dine_mtl_4.jpg
45 ms
feb16_dine_mtl_5.jpg
27 ms
museosans-300-webfont.woff
45 ms
museosans-100-webfont.woff
25 ms
museosans-500-webfont.woff
43 ms
museosans-700-webfont.woff
44 ms
api.js
251 ms
yellowMessages-fr.js
55 ms
baseYellow.js
55 ms
yellow-desktop.js
59 ms
yellowHome.js
59 ms
tc.js
37 ms
feb16_dine_mtl_6.jpg
53 ms
iconLogo-FR.svg
169 ms
febmarch_shop_mtl_7.jpg
172 ms
febmarch_shop_mtl_8.jpg
198 ms
febmarch_shop_mtl_9.jpg
183 ms
iconLogo-FR.svg
184 ms
nexthomeroc_feb29_2016buyhome.jpg
192 ms
nexthomeroc_feb29_thebigshortcanada.jpg
196 ms
nexthomeroc_feb29_makemostamenities.jpg
196 ms
ypapp-desktop--fr.jpg
196 ms
appstore--fr.svg
191 ms
playstore--fr.svg
198 ms
logo-footer-fr.svg
202 ms
gw
175 ms
activityi;src=4181822;type=Yello0;cat=FRYel0;ord=3477880039718.002;
169 ms
fbevents.js
100 ms
amplitude-2.9.0-min.gz.js
171 ms
mixpanel-2.2.min.js
137 ms
ypca-icons.woff
29 ms
99 ms
130 ms
139 ms
38 ms
33 ms
recaptcha__fr_ca.js
82 ms
nr-852.min.js
29 ms
wrapper.js
124 ms
beacon.js
10 ms
as=110.js
72 ms
d901b4dcbe
51 ms
10 ms
pj.ca accessibility score
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
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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.
pj.ca 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
Browser errors were logged to the console
pj.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 uses legible font sizes
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pj.ca can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Pj.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.
pj.ca
Open Graph description is not detected on the main page of PJ. 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: