Publications.Gc.Ca - Info publications.gc.ca

publications.gc.ca receives about 13,574 unique visitors and 21,718 (1.60 per visitor) page views per day which should earn about $100.18/day from advertising revenue. Estimated site value is $73,155.39. According to Alexa Traffic Rank publications.gc.ca is ranked number 100,792 in the world and 0.0008% of global Internet users visit it. Site is hosted in Ottawa, Ontario, K1N, Canada and links to network IP address 205.193.152.59. This server doesn't support HTTPS and doesn't support HTTP/2.

About - publications.gc.ca

Welcome page introduces the Government of Canada Publications Web site and provides the choice of continuing in either English or French.
Edit Site Info

Technologies used on Website

Web Servers
Apache
Tag Managers
Google Tag Manager
Analytics
Matomo

publications.gc.ca Profile

Title: Publications du gouvernement du Canada | Government of Canada Publications
Description: Access over 100,000 free and priced publications authored by Government of Canada departments.
Last update was 14 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with publications.gc.ca in any way. Only publicly available statistics data are displayed.

How popular is publications.gc.ca?

13.6K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
13,574
Monthly Unique Visitors:
325,776
Pages per Visit:
1.60
Daily Pageviews:
21,718
Alexa Rank:
100,792 visit alexa
Alexa Reach:
0.0008%   (of global internet users)
Avg. visit duration:
02:52
Bounce rate:
73.27%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
14.53%
Referral:
15.77%
Search:
69.33%
Social:
0.36%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
Canada 58.6%65.8%3665

Where do visitors go on this site?

Reach%Pageviews%PerUser
publications.gc.ca
100.00%100.00%1.4

Competitive Data

SEMrush
Domain:
  publications.gc.ca
Rank:
(Rank based on keywords, cost and organic traffic)
  136,215
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  105,980
Organic Traffic:
(Number of visitors coming from top 20 search results)
  10,989
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $2,487.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is publications.gc.ca?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
publications.gc.ca
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
publications.gc.ca
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much publications.gc.ca can earn?

Daily Revenue:
$100.18
Monthly Revenue:
$3,005.40
Yearly Revenue:
$36,565.70
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Canada 14,290$100.18

How much money do publications.gc.ca lose due to Adblock?

Daily Revenue Loss:
$25.04
Monthly Revenue Loss:
$751.32
Yearly Revenue Loss:
$9,141.06
Daily Pageviews Blocked:
3,573
Monthly Pageviews Blocked:
107,178
Yearly Pageviews Blocked:
1,304,003
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Canada 3,573$25.04

How much is publications.gc.ca worth?

Website Value:
$73,155.39

+ Where is publications.gc.ca hosted?

Server IP:
205.193.152.59
ASN:
AS2665 
ISP:
Shared Services Canada 
Server Location:
Ottawa
Ontario, ON
K1N
Canada, CA
 

Other sites hosted on 205.193.152.59

There are no other sites hosted on this IP

+ How fast does publications.gc.ca load?

Average Load Time:
(623 ms) 93 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 30 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
111 ms5 ms2 ms
Remove unused CSS - Potential savings of 293 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

URL
SizePotential Savings
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css
296 KB293 KB
Avoids enormous network payloads - Total size was 603 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css
296 KB
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/js/wet-boew.min.js
128 KB
https://ajax.googleapis.com/ajax/libs/jquery/2.1.4/jquery.js
72 KB
http://publications.gc.ca/boew-wet/wet4.0ca/img/splash/sp-bg-2.jpg
36 KB
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/fonts/glyphicons-halflings-regular.woff
23 KB
http://www.googletagmanager.com/gtm.js?id=GTM-TLGQ9K
22 KB
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/assets/sig-spl.svg
11 KB
http://publications.gc.ca/
7 KB
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/assets/wmms-spl.svg
5 KB
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/messages.min.css
3 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
77 ms
Other
51 ms
Style & Layout
35 ms
Parse HTML & CSS
17 ms
Script Parsing & Compilation
12 ms
Rendering
5 ms
Avoids an excessive DOM size - 33 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
33
Maximum DOM Depth
8
Maximum Child Elements
9
Minify JavaScript - Potential savings of 34 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
https://ajax.googleapis.com/ajax/libs/jquery/2.1.4/jquery.js
72 KB34 KB
Keep request counts low and transfer sizes small - 12 requests • 603 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
12603 KB
Stylesheet
2299 KB
Script
4223 KB
Image
236 KB
Font
123 KB
Document
322 KB
Media
00 KB
Other
00 KB
Third-party
295 KB
Eliminate render-blocking resources - Potential savings of 280 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css
296 KB510
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/messages.min.css
3 KB110
Enable text compression - Potential savings of 324 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css
296 KB235 KB
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/js/wet-boew.min.js
127 KB83 KB
http://publications.gc.ca/
7 KB4 KB
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/messages.min.css
3 KB2 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://publications.gc.ca/
0 ms105 ms7 KB7 KB200text/htmlDocument
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css
116 ms342 ms296 KB296 KB200text/cssStylesheet
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/messages.min.css
116 ms156 ms3 KB3 KB200text/cssStylesheet
http://publications.gc.ca/boew-wet/wet4.0ca/img/splash/sp-bg-2.jpg
116 ms224 ms36 KB36 KB200image/jpegImage
https://ajax.googleapis.com/ajax/libs/jquery/2.1.4/jquery.js
116 ms128 ms72 KB242 KB200text/javascriptScript
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/js/wet-boew.min.js
131 ms313 ms128 KB127 KB200application/javascriptScript
http://www.googletagmanager.com/gtm.js?id=GTM-TLGQ9K
360 ms381 ms22 KB61 KB200application/javascriptScript
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/fonts/glyphicons-halflings-regular.woff
373 ms414 ms23 KB23 KB200font/woffFont
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/assets/sig-spl.svg
396 ms474 ms11 KB10 KB200image/svg+xmlDocument
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/assets/wmms-spl.svg
399 ms490 ms5 KB5 KB200image/svg+xmlDocument
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/js/i18n/en.min.js
485 ms495 ms0 KB0 KB-1Image
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/js/i18n/en.min.js
514 ms518 ms0 KB0 KB-1Script
Serve static assets with an efficient cache policy - 5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css
0 ms296 KB
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/js/wet-boew.min.js
0 ms128 KB
http://publications.gc.ca/boew-wet/wet4.0ca/img/splash/sp-bg-2.jpg
0 ms36 KB
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/fonts/glyphicons-halflings-regular.woff
0 ms23 KB
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/messages.min.css
0 ms3 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
72 KB0 ms
22 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
133 ms
7 ms
370 ms
15 ms
388 ms
28 ms
424 ms
6 ms
430 ms
25 ms
462 ms
52 ms
516 ms
5 ms
525 ms
6 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/fonts/glyphicons-halflings-regular.woff
41 ms
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests - 5 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 110 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

84
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

First Meaningful Paint 2.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 2.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
First Contentful Paint (3G) 5955 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 5.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 2.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Keep request counts low and transfer sizes small - 11 requests • 413 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
11413 KB
Stylesheet
2296 KB
Font
241 KB
Image
136 KB
Script
322 KB
Document
317 KB
Media
00 KB
Other
00 KB
Third-party
222 KB
Eliminate render-blocking resources - Potential savings of 1,680 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css
296 KB1980
Enable text compression - Potential savings of 239 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css
296 KB235 KB
http://publications.gc.ca/
7 KB4 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://publications.gc.ca/
0 ms2101 ms7 KB7 KB200text/htmlDocument
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css
2112 ms2340 ms296 KB296 KB200text/cssStylesheet
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/messages.min.css
2112 ms2114 ms0 KB0 KB-1Stylesheet
http://publications.gc.ca/boew-wet/wet4.0ca/img/splash/sp-bg-2.jpg
2112 ms2293 ms36 KB36 KB200image/jpegImage
https://ajax.googleapis.com/ajax/libs/jquery/2.1.4/jquery.js
2112 ms2115 ms0 KB0 KB-1Script
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/js/wet-boew.min.js
2112 ms2116 ms0 KB0 KB-1Script
http://www.googletagmanager.com/gtm.js?id=GTM-TLGQ9K
2357 ms2376 ms22 KB61 KB200application/javascriptScript
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/fonts/glyphicons-halflings-regular.woff
2365 ms2380 ms0 KB0 KB-1Font
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/fonts/glyphicons-halflings-regular.ttf
2380 ms2489 ms41 KB40 KB200font/ttfFont
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/assets/sig-spl.svg
2385 ms2496 ms11 KB10 KB200image/svg+xmlDocument
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/assets/wmms-spl.svg
2389 ms2392 ms0 KB0 KB-1Document
Serve static assets with an efficient cache policy - 3 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css
0 ms296 KB
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/fonts/glyphicons-halflings-regular.ttf
0 ms41 KB
http://publications.gc.ca/boew-wet/wet4.0ca/img/splash/sp-bg-2.jpg
0 ms36 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
22 KB0 ms
0 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
2131 ms
6 ms
2369 ms
14 ms
2385 ms
21 ms
2408 ms
8 ms
2422 ms
6 ms
2526 ms
6 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/fonts/glyphicons-halflings-regular.woff
16 ms
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/fonts/glyphicons-halflings-regular.ttf
108 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
359 ms15 ms7 ms
Remove unused CSS - Potential savings of 293 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

URL
SizePotential Savings
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css
296 KB293 KB
Avoids enormous network payloads - Total size was 413 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css
296 KB
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/fonts/glyphicons-halflings-regular.ttf
41 KB
http://publications.gc.ca/boew-wet/wet4.0ca/img/splash/sp-bg-2.jpg
36 KB
http://www.googletagmanager.com/gtm.js?id=GTM-TLGQ9K
22 KB
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/assets/sig-spl.svg
11 KB
http://publications.gc.ca/
7 KB
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/assets/wmms-spl.svg
0 KB
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/messages.min.css
0 KB
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/fonts/glyphicons-halflings-regular.woff
0 KB
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/js/wet-boew.min.js
0 KB
Minimizes main-thread work - 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Other
140 ms
Style & Layout
103 ms
Parse HTML & CSS
59 ms
Script Evaluation
49 ms
Rendering
37 ms
Script Parsing & Compilation
19 ms
Avoids an excessive DOM size - 32 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
32
Maximum DOM Depth
8
Maximum Child Elements
8
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Reduce server response times (TTFB) - Root document took 2,100 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests - 6 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 336.8KiB (74% reduction).

Compressing http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css could save 233.8KiB (79% reduction).
Compressing http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/js/wet-boew.min.js could save 82.6KiB (64% reduction).
Compressing http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/assets/sig-spl.svg could save 8.3KiB (79% reduction).
Compressing http://publications.gc.ca/ could save 4.4KiB (66% reduction).
Compressing http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/js/i18n/en.min.js could save 2.9KiB (53% reduction).
Compressing http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/assets/wmms-spl.svg could save 2.9KiB (62% reduction).
Compressing http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/messages.min.css could save 1.8KiB (68% reduction).

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/assets/sig-spl.svg (expiration not specified)
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/assets/wmms-spl.svg (expiration not specified)
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/messages.min.css (expiration not specified)
http://publications.gc.ca/boew-wet/wet4.0ca/GCWeb/css/theme.min.css (expiration not specified)
http://publications.gc.ca/boew-wet/wet4.0ca/img/splash/sp-bg-2.jpg (expiration not specified)
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/js/i18n/en.min.js (expiration not specified)
http://publications.gc.ca/boew-wet/wet4.0ca/wet-boew/js/wet-boew.min.js (expiration not specified)
http://www.googletagmanager.com/gtm.js?id=GTM-TLGQ9K (15 minutes)

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 35KiB (49% reduction).

Minifying https://ajax.googleapis.com/ajax/libs/jquery/2.1.4/jquery.js could save 35KiB (49% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Optimize images
Your images are optimized. Learn more about optimizing images.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does publications.gc.ca use compression?

publications.gc.ca does not use compression.
Original size: 6.55 KB
Compressed size: n/a
File reduced by: n/a

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  69
Vendor reliability:
  69
Privacy:
  69
Child safety:
  96

+ SSL Checker - SSL Certificate Verify

publications.gc.ca does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

publications.gc.ca does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Services/Education and Information
Ministères/Travaux publics et services gouvernementaux

+ Http Header

Date: Wed, 30 Oct 2019 15:00:48 GMT
Server: Apache
Accept-Ranges: bytes
Content-Length: 6708
Content-Type: text/html

+ DNS Lookup

Type Ip Target TTL
A 205.193.152.59 600
SOA 900
Mname xns-kedc.pwgsc.gc.ca
Rname root.xns-kedc.pwgsc.gc.ca
Serial Number 2019081601
Refresh 10800
Retry 1800
Expire 604800
Minimum TTL 0
NS xns-kedc-1.ssc-spc.gc.ca 900
NS gocns-kedc.gc.ca 900
NS xns-apdc.ssc-spc.gc.ca 900
NS xns-kedc.ssc-spc.gc.ca 900
NS gocns-pdp.gc.ca 900

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

Currently Not Available
Last update was 14 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with publications.gc.ca in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

kn.f1l.cc
15 secs
teenilove.com
18 secs
beshine.com
21 secs
webmail.ghdc.be
33 secs
km.f1l.cc
39 secs
paperless.com.co
48 secs
kl.f1l.cc
1 min
vim.cx
1 min
tropicbets.com
1 min
webmail.gemiva-svg.nl
1 min

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
publications.gc.ca widget