Pcmuseum.Ca - Info pcmuseum.ca

pcmuseum.ca receives about 85 unique visitors and 170 (2.00 per visitor) page views per day which should earn about $0.69/day from advertising revenue. Estimated site value is $310.36. According to Alexa Traffic Rank pcmuseum.ca is ranked number 4,788,516 in the world and 5.0E-6% of global Internet users visit it. Site is hosted in Ann Arbor, Michigan, 48106, United States and links to network IP address 70.32.28.69. This server supports HTTPS and doesn't support HTTP/2.

About - pcmuseum.ca


pcmuseum.ca Profile

Title: The Personal Computer Museum, Brantford, Ontario, CANADA - Recycle, donate, and browse your old computers, electronics, video games, and software
Description: Contains over 40 interactive computer displays and over 250 machines. Features a listing, gallery, resources, and hours. Located in Brantford, Ontario.
The Personal Computer Museum is located in Brantford, Ontario, Canada and is open to the public to visit its interactive displays on the history of personal computers with thousands of artifacts. The museum takes donations of old electronic equipment, software, and video games and also gives away free computers in the community to those that otherwise can't afford them.
Keywords: computer museum, brantford, ontario, canada, old computers, donate computers, recycle computers, vintage computers, classic computers, Atari, Apple, Commodore, Amiga, Commodore Amiga, TRS-80, Timex Sinclair, Macintosh
Last update was 9 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is pcmuseum.ca?

85 daily visitors
Daily Unique Visitors:
85
Monthly Unique Visitors:
2,550
Pages per Visit:
2.00
Daily Pageviews:
170
Alexa Rank:
4,788,516 visit alexa
Alexa Reach:
5.0E-6%   (of global internet users)
Avg. visit duration:
00:08
Bounce rate:
59.63%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
59.64%
Referral:
0%
Search:
40.36%
Social:
0%
Paid:
0%

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  pcmuseum.ca
Rank:
(Rank based on keywords, cost and organic traffic)
  7,242,473
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.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

Data

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

How socially engaged is pcmuseum.ca?

Facebook:
  42
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:
pcmuseum.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:
pcmuseum.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 pcmuseum.ca can earn?

Daily Revenue:
$0.69
Monthly Revenue:
$20.70
Yearly Revenue:
$251.85
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do pcmuseum.ca lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is pcmuseum.ca worth?

Website Value:
$310.36

Where is pcmuseum.ca hosted?

Server IP:
70.32.28.69
ASN:
AS55293 
ISP:
A2 Hosting, Inc. 
Server Location:
Ann Arbor
Michigan, MI
48106
United States, US
 

Other sites hosted on 70.32.28.69

How fast does pcmuseum.ca load?

Average Load Time:
n/a ms n/a % 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

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.7 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.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
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.
Tasks
Lists the toplevel main thread tasks that executed during page load.
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.
JavaScript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
Minimizes main-thread work
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Diagnostics
Collection of useful page vitals.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 101 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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
101
Maximum DOM Depth
11
Maximum Child Elements
23
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://pcmuseum.ca/)
0
https://pcmuseum.ca/
190
Keep request counts low and transfer sizes small - 29 requests • 647 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
29647 KB
Image
10286 KB
Script
9262 KB
Document
689 KB
Stylesheet
28 KB
Other
21 KB
Media
00 KB
Font
00 KB
Third-party
20354 KB
Eliminate render-blocking resources - Potential savings of 0 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
https://pcmuseum.ca/stylesheet.css
1 KB70
Efficiently encode images - Potential savings of 144 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
https://pcmuseum.ca/images/header2.jpg
143 KB93 KB
https://pcmuseum.ca/misc/iPhoneAppBanner.jpg
46 KB26 KB
https://pcmuseum.ca/misc/virtualreality-cancled.jpg
59 KB25 KB
Enable text compression - Potential savings of 108 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
https://platform.twitter.com/widgets.js
93 KB66 KB
https://platform.twitter.com/widgets/follow_button.0639d67d95b7680840758b6833f06d87.en.html
36 KB23 KB
https://platform.twitter.com/widgets/widget_iframe.0639d67d95b7680840758b6833f06d87.html?origin=https%3A%2F%2Fpcmuseum.ca
15 KB9 KB
https://pcmuseum.ca/
9 KB6 KB
https://platform.twitter.com/js/button.509719336ca39171c37a321231ccaf83.js
7 KB5 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://pcmuseum.ca/
0 ms43 ms0 KB0 KB301text/html
https://pcmuseum.ca/
43 ms94 ms10 KB9 KB200text/htmlDocument
https://pcmuseum.ca/stylesheet.css
120 ms168 ms1 KB5 KB200text/cssStylesheet
https://pcmuseum.ca/images/header2.jpg
121 ms241 ms143 KB143 KB200image/jpegImage
https://pcmuseum.ca/misc/iPhoneAppBanner.jpg
121 ms168 ms46 KB46 KB200image/jpegImage
https://pcmuseum.ca/misc/pickupbutton.gif
122 ms169 ms11 KB11 KB200image/gifImage
https://pcmuseum.ca/front/5.jpg
122 ms312 ms17 KB17 KB200image/jpegImage
https://pcmuseum.ca/misc/virtualreality-cancled.jpg
122 ms171 ms59 KB59 KB200image/jpegImage
https://connect.facebook.net/en_US/all.js
172 ms189 ms3 KB3 KB200application/x-javascriptScript
http://www.statcounter.com/counter/counter.js
173 ms173 ms0 KB0 KB-1Script
https://pcmuseum.ca/images/circuit.gif
175 ms211 ms4 KB4 KB200image/gifImage
https://platform.twitter.com/widgets.js
182 ms202 ms93 KB93 KB200application/javascriptScript
http://pagead2.googlesyndication.com/pagead/show_ads.js
182 ms182 ms0 KB0 KB-1Script
https://connect.facebook.net/en_US/all.js?hash=451a870890541a9e5e246ccf24309147&ua=modern_es6
192 ms216 ms57 KB191 KB200application/x-javascriptScript
https://platform.twitter.com/widgets/widget_iframe.0639d67d95b7680840758b6833f06d87.html?origin=https%3A%2F%2Fpcmuseum.ca
262 ms283 ms15 KB15 KB200text/htmlDocument
https://platform.twitter.com/js/button.509719336ca39171c37a321231ccaf83.js
267 ms285 ms7 KB7 KB200application/javascriptScript
https://staticxx.facebook.com/connect/xd_arbiter.php?version=44
317 ms339 ms12 KB37 KB200text/htmlDocument
https://syndication.twitter.com/settings
352 ms379 ms1 KB0 KB200application/jsonFetch
https://platform.twitter.com/widgets/follow_button.0639d67d95b7680840758b6833f06d87.en.html
375 ms397 ms37 KB36 KB200text/htmlDocument
data:image/svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%22%20viewBox%3D%220%200%
439 ms439 ms0 KB1 KB200image/svg+xmlImage
https://www.facebook.com/connect/ping?client_id=10092896629&domain=pcmuseum.ca&origin=1&redirect_uri=https%3A%2F%2Fstaticxx.facebook.com%2Fconnect%2Fxd_arbiter.php%3Fversion%3D44%23cb%3Df1f546aee738304%26domain%3Dpcmuseum.ca%26origin%3Dhttps%253A%252F%252Fpcmuseum.ca%252Ff26d5779aa1dbf8%26relation%3Dparent&response_type=token%2Csigned_request&sdk=joey
457 ms549 ms1 KB0 KB200text/htmlDocument
https://www.facebook.com/plugins/like_box.php?app_id=10092896629&channel=https%3A%2F%2Fstaticxx.facebook.com%2Fconnect%2Fxd_arbiter.php%3Fversion%3D44%23cb%3Df3b75e03a69b93c%26domain%3Dpcmuseum.ca%26origin%3Dhttps%253A%252F%252Fpcmuseum.ca%252Ff26d5779aa1dbf8%26relation%3Dparent.parent&container_width=775&header=false&href=http%3A%2F%2Fwww.facebook.com%2Fpersonalcomputermuseum&locale=en_US&sdk=joey&show_faces=false&stream=false&width=292
478 ms592 ms14 KB52 KB200text/htmlDocument
https://syndication.twitter.com/i/jot?l=%7B%22widget_origin%22%3A%22https%3A%2F%2Fpcmuseum.ca%2F%22%2C%22widget_frame%22%3Afalse%2C%22language%22%3A%22en%22%2C%22message%22%3A%22l%3Awithcount%3A%22%2C%22_category_%22%3A%22tfw_client_event%22%2C%22triggered_on%22%3A1565829147653%2C%22dnt%22%3Afalse%2C%22client_version%22%3A%22bbec9cd%3A1564009982483%22%2C%22format_version%22%3A1%2C%22event_namespace%22%3A%7B%22client%22%3A%22tfw%22%2C%22page%22%3A%22button%22%2C%22section%22%3A%22follow%22%2C%22action%22%3A%22impression%22%7D%7D
582 ms623 ms1 KB0 KB200image/gifImage
https://static.xx.fbcdn.net/rsrc.php/v3/yv/l/0,cross/jZUF3cXeA8k.css?_nc_x=Ij3Wp8lg5Kz
602 ms618 ms7 KB31 KB200text/cssStylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yB/r/VhSdAhZiRzw.js?_nc_x=Ij3Wp8lg5Kz
602 ms643 ms72 KB299 KB200application/x-javascriptScript
https://static.xx.fbcdn.net/rsrc.php/v3/yG/r/4zN9Y_HAUR4.js?_nc_x=Ij3Wp8lg5Kz
603 ms748 ms23 KB83 KB200application/x-javascriptScript
https://static.xx.fbcdn.net/rsrc.php/v3/y-/r/tZIm25moYfy.js?_nc_x=Ij3Wp8lg5Kz
603 ms644 ms7 KB24 KB200application/x-javascriptScript
https://scontent-atl3-1.xx.fbcdn.net/v/t1.0-1/p50x50/26992099_10156128171113777_6420102153049297396_n.jpg?_nc_cat=107&_nc_oc=AQmkaBTUmG6dbbX9vNf-AsoeYkdxoNS257-VYQhtpr-3fviOPHg02_TN8_mWklxoSpc&_nc_ht=scontent-atl3-1.xx&oh=37d2fad03bd95a2ee99340a976a47397&oe=5DC7EDEC
603 ms621 ms2 KB2 KB200image/jpegImage
https://static.xx.fbcdn.net/rsrc.php/v3/yG/r/wrCiWd_JmQD.png
794 ms811 ms2 KB1 KB200image/pngImage
Serve static assets with an efficient cache policy - 10 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://pcmuseum.ca/images/header2.jpg
0 ms143 KB
https://pcmuseum.ca/misc/virtualreality-cancled.jpg
0 ms59 KB
https://pcmuseum.ca/misc/iPhoneAppBanner.jpg
0 ms46 KB
https://pcmuseum.ca/front/5.jpg
0 ms17 KB
https://pcmuseum.ca/misc/pickupbutton.gif
0 ms11 KB
https://pcmuseum.ca/images/circuit.gif
0 ms4 KB
https://pcmuseum.ca/stylesheet.css
0 ms1 KB
https://connect.facebook.net/en_US/all.js
1200000 ms3 KB
https://platform.twitter.com/widgets.js
1800000 ms93 KB
https://scontent-atl3-1.xx.fbcdn.net/v/t1.0-1/p50x50/26992099_10156128171113777_6420102153049297396_n.jpg?_nc_cat=107&_nc_oc=AQmkaBTUmG6dbbX9vNf-AsoeYkdxoNS257-VYQhtpr-3fviOPHg02_TN8_mWklxoSpc&_nc_ht=scontent-atl3-1.xx&oh=37d2fad03bd95a2ee99340a976a47397&oe=5DC7EDEC
1209600000 ms2 KB
Remove unused CSS - Potential savings of 7 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
https://static.xx.fbcdn.net/rsrc.php/v3/yv/l/0,cross/jZUF3cXeA8k.css?_nc_x=Ij3Wp8lg5Kz
7 KB7 KB
Avoids enormous network payloads - Total size was 647 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://pcmuseum.ca/images/header2.jpg
143 KB
https://platform.twitter.com/widgets.js
93 KB
https://static.xx.fbcdn.net/rsrc.php/v3/yB/r/VhSdAhZiRzw.js?_nc_x=Ij3Wp8lg5Kz
72 KB
https://pcmuseum.ca/misc/virtualreality-cancled.jpg
59 KB
https://connect.facebook.net/en_US/all.js?hash=451a870890541a9e5e246ccf24309147&ua=modern_es6
57 KB
https://pcmuseum.ca/misc/iPhoneAppBanner.jpg
46 KB
https://platform.twitter.com/widgets/follow_button.0639d67d95b7680840758b6833f06d87.en.html
37 KB
https://static.xx.fbcdn.net/rsrc.php/v3/yG/r/4zN9Y_HAUR4.js?_nc_x=Ij3Wp8lg5Kz
23 KB
https://pcmuseum.ca/front/5.jpg
17 KB
https://platform.twitter.com/widgets/widget_iframe.0639d67d95b7680840758b6833f06d87.html?origin=https%3A%2F%2Fpcmuseum.ca
15 KB
Serve images in next-gen formats - Potential savings of 186 KB
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.

URL
SizePotential Savings
https://pcmuseum.ca/images/header2.jpg
143 KB117 KB
https://pcmuseum.ca/misc/virtualreality-cancled.jpg
59 KB36 KB
https://pcmuseum.ca/misc/iPhoneAppBanner.jpg
46 KB34 KB
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.

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 50 ms
Time To First Byte identifies the time at which your server sends a response. 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.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. 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.

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.

Minimize Critical Requests Depth - 3 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.


Page Speed (Google PageSpeed Insights) - Mobile

76
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.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 140 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 6.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 190 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 30 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) 5328 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 3.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 5.5 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.6 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 - 29 requests • 652 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
29652 KB
Image
10291 KB
Script
9262 KB
Document
689 KB
Stylesheet
28 KB
Other
21 KB
Media
00 KB
Font
00 KB
Third-party
20354 KB
Eliminate render-blocking resources - Potential savings of 0 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
https://pcmuseum.ca/stylesheet.css
1 KB180
Efficiently encode images - Potential savings of 144 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
https://pcmuseum.ca/images/header2.jpg
143 KB93 KB
https://pcmuseum.ca/misc/iPhoneAppBanner.jpg
46 KB26 KB
https://pcmuseum.ca/misc/virtualreality-cancled.jpg
59 KB25 KB
Enable text compression - Potential savings of 108 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
https://platform.twitter.com/widgets.js
93 KB66 KB
https://platform.twitter.com/widgets/follow_button.0639d67d95b7680840758b6833f06d87.en.html
36 KB23 KB
https://platform.twitter.com/widgets/widget_iframe.0639d67d95b7680840758b6833f06d87.html?origin=https%3A%2F%2Fpcmuseum.ca
15 KB9 KB
https://pcmuseum.ca/
9 KB6 KB
https://platform.twitter.com/js/button.509719336ca39171c37a321231ccaf83.js
7 KB5 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://pcmuseum.ca/
0 ms181 ms0 KB0 KB301text/html
https://pcmuseum.ca/
182 ms369 ms10 KB9 KB200text/htmlDocument
https://pcmuseum.ca/stylesheet.css
398 ms444 ms1 KB5 KB200text/cssStylesheet
https://pcmuseum.ca/images/header2.jpg
398 ms480 ms143 KB143 KB200image/jpegImage
https://pcmuseum.ca/misc/iPhoneAppBanner.jpg
398 ms580 ms46 KB46 KB200image/jpegImage
https://pcmuseum.ca/misc/pickupbutton.gif
399 ms436 ms11 KB11 KB200image/gifImage
https://pcmuseum.ca/front/9.jpg
399 ms558 ms22 KB22 KB200image/jpegImage
https://pcmuseum.ca/misc/virtualreality-cancled.jpg
399 ms475 ms59 KB59 KB200image/jpegImage
https://connect.facebook.net/en_US/all.js
447 ms463 ms3 KB3 KB200application/x-javascriptScript
http://www.statcounter.com/counter/counter.js
447 ms447 ms0 KB0 KB-1Script
https://pcmuseum.ca/images/circuit.gif
448 ms594 ms4 KB4 KB200image/gifImage
https://platform.twitter.com/widgets.js
451 ms471 ms93 KB93 KB200application/javascriptScript
http://pagead2.googlesyndication.com/pagead/show_ads.js
451 ms451 ms0 KB0 KB-1Script
https://connect.facebook.net/en_US/all.js?hash=451a870890541a9e5e246ccf24309147&ua=modern_es6
466 ms488 ms57 KB191 KB200application/x-javascriptScript
https://platform.twitter.com/widgets/widget_iframe.0639d67d95b7680840758b6833f06d87.html?origin=https%3A%2F%2Fpcmuseum.ca
537 ms557 ms15 KB15 KB200text/htmlDocument
https://platform.twitter.com/js/button.509719336ca39171c37a321231ccaf83.js
540 ms557 ms7 KB7 KB200application/javascriptScript
https://staticxx.facebook.com/connect/xd_arbiter.php?version=44
572 ms599 ms12 KB37 KB200text/htmlDocument
https://syndication.twitter.com/settings
600 ms636 ms1 KB0 KB200application/jsonFetch
https://platform.twitter.com/widgets/follow_button.0639d67d95b7680840758b6833f06d87.en.html
616 ms640 ms37 KB36 KB200text/htmlDocument
data:image/svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%22%20viewBox%3D%220%200%
683 ms683 ms0 KB1 KB200image/svg+xmlImage
https://www.facebook.com/connect/ping?client_id=10092896629&domain=pcmuseum.ca&origin=2&redirect_uri=https%3A%2F%2Fstaticxx.facebook.com%2Fconnect%2Fxd_arbiter.php%3Fversion%3D44%23cb%3Df37c6ea08f5b078%26domain%3Dpcmuseum.ca%26origin%3Dhttps%253A%252F%252Fpcmuseum.ca%252Ff34586f47cc6a1%26relation%3Dparent&response_type=token%2Csigned_request&sdk=joey
702 ms800 ms1 KB0 KB200text/htmlDocument
https://www.facebook.com/plugins/like_box.php?app_id=10092896629&channel=https%3A%2F%2Fstaticxx.facebook.com%2Fconnect%2Fxd_arbiter.php%3Fversion%3D44%23cb%3Df154383f4825858%26domain%3Dpcmuseum.ca%26origin%3Dhttps%253A%252F%252Fpcmuseum.ca%252Ff34586f47cc6a1%26relation%3Dparent.parent&container_width=775&header=false&href=http%3A%2F%2Fwww.facebook.com%2Fpersonalcomputermuseum&locale=en_US&sdk=joey&show_faces=false&stream=false&width=292
722 ms834 ms14 KB52 KB200text/htmlDocument
https://syndication.twitter.com/i/jot?l=%7B%22widget_origin%22%3A%22https%3A%2F%2Fpcmuseum.ca%2F%22%2C%22widget_frame%22%3Afalse%2C%22language%22%3A%22en%22%2C%22message%22%3A%22l%3Awithcount%3A%22%2C%22_category_%22%3A%22tfw_client_event%22%2C%22triggered_on%22%3A1565829141331%2C%22dnt%22%3Afalse%2C%22client_version%22%3A%22bbec9cd%3A1564009982483%22%2C%22format_version%22%3A1%2C%22event_namespace%22%3A%7B%22client%22%3A%22tfw%22%2C%22page%22%3A%22button%22%2C%22section%22%3A%22follow%22%2C%22action%22%3A%22impression%22%7D%7D
826 ms861 ms1 KB0 KB200image/gifImage
https://static.xx.fbcdn.net/rsrc.php/v3/yv/l/0,cross/jZUF3cXeA8k.css?_nc_x=Ij3Wp8lg5Kz
844 ms861 ms7 KB31 KB200text/cssStylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yB/r/VhSdAhZiRzw.js?_nc_x=Ij3Wp8lg5Kz
844 ms883 ms72 KB299 KB200application/x-javascriptScript
https://static.xx.fbcdn.net/rsrc.php/v3/yG/r/4zN9Y_HAUR4.js?_nc_x=Ij3Wp8lg5Kz
845 ms884 ms23 KB83 KB200application/x-javascriptScript
https://static.xx.fbcdn.net/rsrc.php/v3/y-/r/tZIm25moYfy.js?_nc_x=Ij3Wp8lg5Kz
845 ms879 ms7 KB24 KB200application/x-javascriptScript
https://scontent-atl3-1.xx.fbcdn.net/v/t1.0-1/p50x50/26992099_10156128171113777_6420102153049297396_n.jpg?_nc_cat=107&_nc_oc=AQmkaBTUmG6dbbX9vNf-AsoeYkdxoNS257-VYQhtpr-3fviOPHg02_TN8_mWklxoSpc&_nc_ht=scontent-atl3-1.xx&oh=37d2fad03bd95a2ee99340a976a47397&oe=5DC7EDEC
845 ms861 ms2 KB2 KB200image/jpegImage
https://static.xx.fbcdn.net/rsrc.php/v3/yG/r/wrCiWd_JmQD.png
963 ms979 ms2 KB1 KB200image/pngImage
Serve static assets with an efficient cache policy - 10 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://pcmuseum.ca/images/header2.jpg
0 ms143 KB
https://pcmuseum.ca/misc/virtualreality-cancled.jpg
0 ms59 KB
https://pcmuseum.ca/misc/iPhoneAppBanner.jpg
0 ms46 KB
https://pcmuseum.ca/front/9.jpg
0 ms22 KB
https://pcmuseum.ca/misc/pickupbutton.gif
0 ms11 KB
https://pcmuseum.ca/images/circuit.gif
0 ms4 KB
https://pcmuseum.ca/stylesheet.css
0 ms1 KB
https://connect.facebook.net/en_US/all.js
1200000 ms3 KB
https://platform.twitter.com/widgets.js
1800000 ms93 KB
https://scontent-atl3-1.xx.fbcdn.net/v/t1.0-1/p50x50/26992099_10156128171113777_6420102153049297396_n.jpg?_nc_cat=107&_nc_oc=AQmkaBTUmG6dbbX9vNf-AsoeYkdxoNS257-VYQhtpr-3fviOPHg02_TN8_mWklxoSpc&_nc_ht=scontent-atl3-1.xx&oh=37d2fad03bd95a2ee99340a976a47397&oe=5DC7EDEC
1209600000 ms2 KB
Third-Party Usage - 4 Third-Parties Found
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 Time
201 KB596 ms
152 KB418 ms
0 KB0 ms
0 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
390 ms
7 ms
398 ms
17 ms
485 ms
29 ms
517 ms
6 ms
525 ms
34 ms
561 ms
14 ms
576 ms
20 ms
599 ms
6 ms
613 ms
6 ms
621 ms
14 ms
644 ms
9 ms
666 ms
47 ms
716 ms
25 ms
820 ms
6 ms
854 ms
5 ms
917 ms
18 ms
940 ms
7 ms
947 ms
57 ms
1006 ms
6 ms
JavaScript execution time - 0.8 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
724 ms63 ms14 ms
https://connect.facebook.net/en_US/all.js?hash=451a870890541a9e5e246ccf24309147&ua=modern_es6
239 ms197 ms26 ms
https://www.facebook.com/plugins/like_box.php?app_id=10092896629&channel=https%3A%2F%2Fstaticxx.facebook.com%2Fconnect%2Fxd_arbiter.php%3Fversion%3D44%23cb%3Df154383f4825858%26domain%3Dpcmuseum.ca%26origin%3Dhttps%253A%252F%252Fpcmuseum.ca%252Ff34586f47cc6a1%26relation%3Dparent.parent&container_width=775&header=false&href=http%3A%2F%2Fwww.facebook.com%2Fpersonalcomputermuseum&locale=en_US&sdk=joey&show_faces=false&stream=false&width=292
207 ms154 ms11 ms
https://platform.twitter.com/widgets.js
201 ms189 ms8 ms
https://platform.twitter.com/widgets/follow_button.0639d67d95b7680840758b6833f06d87.en.html
181 ms56 ms10 ms
https://static.xx.fbcdn.net/rsrc.php/v3/yB/r/VhSdAhZiRzw.js?_nc_x=Ij3Wp8lg5Kz
77 ms46 ms31 ms
Remove unused CSS - Potential savings of 7 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
https://static.xx.fbcdn.net/rsrc.php/v3/yv/l/0,cross/jZUF3cXeA8k.css?_nc_x=Ij3Wp8lg5Kz
7 KB7 KB
Avoids enormous network payloads - Total size was 652 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://pcmuseum.ca/images/header2.jpg
143 KB
https://platform.twitter.com/widgets.js
93 KB
https://static.xx.fbcdn.net/rsrc.php/v3/yB/r/VhSdAhZiRzw.js?_nc_x=Ij3Wp8lg5Kz
72 KB
https://pcmuseum.ca/misc/virtualreality-cancled.jpg
59 KB
https://connect.facebook.net/en_US/all.js?hash=451a870890541a9e5e246ccf24309147&ua=modern_es6
57 KB
https://pcmuseum.ca/misc/iPhoneAppBanner.jpg
46 KB
https://platform.twitter.com/widgets/follow_button.0639d67d95b7680840758b6833f06d87.en.html
37 KB
https://static.xx.fbcdn.net/rsrc.php/v3/yG/r/4zN9Y_HAUR4.js?_nc_x=Ij3Wp8lg5Kz
23 KB
https://pcmuseum.ca/front/9.jpg
22 KB
https://platform.twitter.com/widgets/widget_iframe.0639d67d95b7680840758b6833f06d87.html?origin=https%3A%2F%2Fpcmuseum.ca
15 KB
Minimizes main-thread work - 1.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Script Evaluation
776 ms
Other
364 ms
Style & Layout
322 ms
Script Parsing & Compilation
147 ms
Rendering
71 ms
Parse HTML & CSS
65 ms
Garbage Collection
2 ms
Serve images in next-gen formats - Potential savings of 186 KB
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.

URL
SizePotential Savings
https://pcmuseum.ca/images/header2.jpg
143 KB117 KB
https://pcmuseum.ca/misc/virtualreality-cancled.jpg
59 KB36 KB
https://pcmuseum.ca/misc/iPhoneAppBanner.jpg
46 KB34 KB
Avoids an excessive DOM size - 101 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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
101
Maximum DOM Depth
11
Maximum Child Elements
23
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://pcmuseum.ca/)
0
https://pcmuseum.ca/
630
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 190 ms
Time To First Byte identifies the time at which your server sends a response. 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.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. 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.

Minimize Critical Requests Depth - 3 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.

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

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Computers and 9 others render only 5 pixels tall (12 CSS pixels) .
Many children…s and 80’s. and 7 others render only 5 pixels tall (12 CSS pixels) .
Personal Compu…History Museum and 2 others render only 5 pixels tall (12 CSS pixels) .
Over 50 intera…ny given time. and 12 others render only 5 pixels tall (12 CSS pixels) .
Apple • Atari…Coleco • Dell renders only 5 pixels tall (12 CSS pixels) .
Brant News Rea…s Choice Award and 10 others render only 5 pixels tall (12 CSS pixels) .
The museum is currently CLOSED renders only 5 pixels tall (12 CSS pixels) .
recycle old computers renders only 5 pixels tall (12 CSS pixels) .
Personal Computer Museum renders only 7 pixels tall (18 CSS pixels) .
Like Page renders only 5 pixels tall (12 CSS pixels) .
2.1K likes renders only 5 pixels tall (12 CSS pixels) .
Follow renders only 5 pixels tall (13 CSS pixels) .
@vintagepc renders only 5 pixels tall (13 CSS pixels) .

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 171.4KiB (63% reduction).

Compressing https://pcmuseum.ca/images/header2.jpg could save 107KiB (74% reduction).
Compressing https://pcmuseum.ca/misc/virtualreality-cancled.jpg could save 31.6KiB (53% reduction).
Compressing https://pcmuseum.ca/misc/iPhoneAppBanner.jpg could save 29.9KiB (65% reduction).
Compressing https://pcmuseum.ca/front/5.jpg could save 2.2KiB (14% reduction).
Compressing https://scontent-atl3-1.***.fbcdn.net/v/t1.0-1/p50x50/2***92099_10156128171113777_6420102153049297396_n.jpg?_nc_cat=107&_nc_oc=AQmkaBTUmG6dbbX9vNf-AsoeYkdxoNS257-VYQhtpr-3fviOPHg02_TN8_mWklxoSpc&_nc_ht=scontent-atl3-1.***&oh=37d2fad03bd95a2ee99340a976a47397&oe=5DC7EDEC could save 400B (22% reduction).
Compressing https://static.***.fbcdn.net/rsrc.php/v3/yG/r/wrCiWd_JmQD.png could save 296B (30% reduction).

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 112.2KiB (67% reduction).

Compressing https://platform.twitter.com/widgets.js could save 65.6KiB (70% reduction).
Compressing https://platform.twitter.com/widgets/follow_button.0639d67d95b7680840758b6833f06d87.en.html could save 22.7KiB (62% reduction).
Compressing https://platform.twitter.com/widgets/widget_iframe.0639d67d95b7680840758b6833f06d87.html?origin=https%3A%2F%2Fpcmuseum.ca could save 9.2KiB (61% reduction).
Compressing https://pcmuseum.ca/ could save 6KiB (63% reduction).
Compressing https://platform.twitter.com/js/button.509719336ca39171c37a321231ccaf83.js could save 4.5KiB (66% reduction).
Compressing https://pcmuseum.ca/stylesheet.css could save 4.2KiB (83% reduction).

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="computerDetails.asp" class="menu">Computers</a> and 9 others are close to other tap targets .
The tap target <a href="collections.asp?type=Book">book</a> and 3 others are close to other tap targets .
The tap target <a href="donations.asp">recycle old computers</a> is close to 2 other tap targets .
The tap target <a href="https://m.face…pcmuseum.ca%2F" class="_3-8_ lfloat"></a> is close to 1 other tap targets .
The tap target <img src="https://sconte…97&amp;oe=5DC7EDEC" class="_1drn _-s img"> is close to 3 other tap targets .
The tap target <a href="https://m.face…pcmuseum.ca%2F" class="_1drp _5lv6">Personal Computer Museum</a> is close to 1 other tap targets .
The tap target <div id="u_0_2" class="pluginConnectButton">Like PageLiked</div> is close to 2 other tap targets .
The tap target <a href="https://m.face…pcmuseum.ca%2F" class="_42ft _4jy0 _o…y3 _517h _51sy">Like Page</a> is close to 1 other tap targets .
The tap target <a id="follow-button" href="https://twitte…p=followbutton" class="btn">Follow @vintagepc</a> is close to 1 other tap targets .

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:

https://pcmuseum.ca/front/5.jpg (expiration not specified)
https://pcmuseum.ca/images/circuit.gif (expiration not specified)
https://pcmuseum.ca/images/header2.jpg (expiration not specified)
https://pcmuseum.ca/misc/iPhoneAppBanner.jpg (expiration not specified)
https://pcmuseum.ca/misc/pickupbutton.gif (expiration not specified)
https://pcmuseum.ca/misc/virtualreality-cancled.jpg (expiration not specified)
https://pcmuseum.ca/stylesheet.css (expiration not specified)
https://syndication.twitter.com/settings (10 minutes)
https://connect.facebook.net/en_US/all.js (20 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://www.googletagservices.com/activeview/js/current/osd.js?cb=%2Fr20100101 (50 minutes)
https://www.googletagservices.com/activeview/js/current/osd_listener.js?cache=r20110914 (50 minutes)
http://pagead2.googlesyndication.com/pagead/show_ads.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

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:

https://pcmuseum.ca/stylesheet.css

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 1.8KiB (19% reduction).

Minifying https://pcmuseum.ca/ could save 1.8KiB (19% reduction).

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 1.3KiB (27% reduction).

Minifying https://pcmuseum.ca/stylesheet.css could save 1.3KiB (27% reduction).

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 673B (39% reduction).

Minifying https://connect.facebook.net/en_US/all.js could save 673B (39% reduction) after compression.
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.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Download optimized image, JavaScript, and CSS resources for this page.

Does pcmuseum.ca use compression?

pcmuseum.ca does not use compression.
Original size: 9.43 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:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

SSL Checker - SSL Certificate Verify

pcmuseum.ca supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: pcmuseum.ca
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Jul 29 08:03:45 2019 GMT
Valid until: Oct 27 08:03:45 2019 GMT
Authority:
Keysize:

Verify HTTP/2 Support

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

Http Header

Content-Type: text/html; charset=UTF-8
Location: https://pcmuseum.ca/
Server: Microsoft-IIS/10.0
X-Powered-By: ASP.NET
X-Powered-By-Plesk: PleskWin
Date: Thu, 15 Aug 2019 00:32:03 GMT
Content-Length: 143

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html
Server: Microsoft-IIS/10.0
Set-Cookie: ASPSESSIONIDCUQABSDR=AAIFDNDCHCABOLFJAFHJKGDD; secure; path=/
X-Powered-By: ASP.NET
X-Powered-By-Plesk: PleskWin
Date: Thu, 15 Aug 2019 00:32:03 GMT
Content-Length: 9656

DNS Lookup

Currently Not Available

Whois Lookup

Domain Created:
2005-09-19
Domain Age:
13 years 10 months 25 days  
WhoIs:
 

whois lookup at whois.cira.ca...
Domain Name: pcmuseum.ca
Registry Domain ID: D317897-CIRA
Registrar WHOIS Server: whois.ca.fury.ca
Registrar URL: ca.godaddy.com
Updated Date: 2019-03-16T09:04:29Z
Creation Date: 2005-09-19T18:34:26Z
Registry Expiry Date: 2019-09-19T04:00:00Z
Registrar: Go Daddy Domains Canada, Inc
Registrar IANA ID:
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: Redacted for Privacy Purposes
Registrant Name: Redacted for Privacy Purposes
Registrant Organization: Redacted for Privacy Purposes
Registrant Street: Redacted for Privacy Purposes
Registrant City: Redacted for Privacy Purposes
Registrant State/Province: Redacted for Privacy Purposes
Registrant Postal Code: Redacted for Privacy Purposes
Registrant Country: Redacted for Privacy Purposes
Registrant Phone: Redacted for Privacy Purposes
Registrant Phone Ext: Redacted for Privacy Purposes
Registrant Fax: Redacted for Privacy Purposes
Registrant Fax Ext: Redacted for Privacy Purposes
Registrant Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Registry Admin ID: Redacted for Privacy Purposes
Admin Name: Redacted for Privacy Purposes
Admin Organization: Redacted for Privacy Purposes
Admin Street: Redacted for Privacy Purposes
Admin City: Redacted for Privacy Purposes
Admin State/Province: Redacted for Privacy Purposes
Admin Postal Code: Redacted for Privacy Purposes
Admin Country: Redacted for Privacy Purposes
Admin Phone: Redacted for Privacy Purposes
Admin Phone Ext: Redacted for Privacy Purposes
Admin Fax: Redacted for Privacy Purposes
Admin Fax Ext: Redacted for Privacy Purposes
Admin Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Registry Tech ID: Redacted for Privacy Purposes
Tech Name: Redacted for Privacy Purposes
Tech Organization: Redacted for Privacy Purposes
Tech Street: Redacted for Privacy Purposes
Tech City: Redacted for Privacy Purposes
Tech State/Province: Redacted for Privacy Purposes
Tech Postal Code: Redacted for Privacy Purposes
Tech Country: Redacted for Privacy Purposes
Tech Phone: Redacted for Privacy Purposes
Tech Phone Ext: Redacted for Privacy Purposes
Tech Fax: Redacted for Privacy Purposes
Tech Fax Ext: Redacted for Privacy Purposes
Tech Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Registry Billing ID: Redacted for Privacy Purposes
Billing Name: Redacted for Privacy Purposes
Billing Organization: Redacted for Privacy Purposes
Billing Street: Redacted for Privacy Purposes
Billing City: Redacted for Privacy Purposes
Billing State/Province: Redacted for Privacy Purposes
Billing Postal Code: Redacted for Privacy Purposes
Billing Country: Redacted for Privacy Purposes
Billing Phone: Redacted for Privacy Purposes
Billing Phone Ext: Redacted for Privacy Purposes
Billing Fax: Redacted for Privacy Purposes
Billing Fax Ext: Redacted for Privacy Purposes
Billing Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Name Server: ns1.a2hosting.com
Name Server: ns2.a2hosting.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-08-15T00:30:15Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

%
% Use of CIRA's WHOIS service is governed by the Terms of Use in its Legal
% Notice, available at http://www.cira.ca/legal-notice/?lang=en
%
% (c) 2019 Canadian Internet Registration Authority, (http://www.cira.ca/)
Last update was 9 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

myzuka.ru
16 secs
marco-sk.com
17 secs
drallenlycka.com
19 secs
globalworldreviews.com
19 secs
iraqmillstone.com
26 secs
crayon-intel.com
29 secs
laxsound.com
30 secs
axsaude.com
32 secs
agongaming.net
34 secs
an***u.com
36 secs

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!
pcmuseum.ca widget