3.1 sec in total
309 ms
2.2 sec
527 ms
Welcome to pigeonhole.com homepage info - get ready to check Pigeonhole best content for Australia right away, or after learning these important things about pigeonhole.com
Curators of beautiful things
Visit pigeonhole.comWe analyzed Pigeonhole.com page load time and found that the first response time was 309 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
pigeonhole.com performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value4.2 s
43/100
25%
Value1.2 s
100/100
10%
Value140 ms
95/100
30%
Value0.003
100/100
15%
Value3.5 s
92/100
10%
309 ms
117 ms
103 ms
102 ms
135 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Pigeonhole.com, 43% (26 requests) were made to Cdn.shopify.com and 20% (12 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (561 ms) relates to the external source Api.instagram.com.
Page size can be reduced by 622.7 kB (25%)
2.5 MB
1.9 MB
In fact, the total size of Pigeonhole.com main page is 2.5 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. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 51.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 14.2 kB, which is 23% 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 51.0 kB or 84% of the original size.
Potential reduce by 3.9 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. Pigeonhole images are well optimized though.
Potential reduce by 252.3 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 252.3 kB or 56% of the original size.
Potential reduce by 315.4 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. Pigeonhole.com needs all CSS files to be minified and compressed as it can save up to 315.4 kB or 84% of the original size.
Number of requests can be reduced by 17 (33%)
52
35
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pigeonhole. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
pigeonhole.com
309 ms
district.scss.css
117 ms
css
103 ms
ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js
102 ms
jquery.min.js
135 ms
modernizr.min.js
133 ms
vendor.js
134 ms
district.js
210 ms
shopify_stats.js
191 ms
trekkie.storefront.min.js
190 ms
shop_events_listener-dabe00038c134ebede3c66ef50bfdcedb847ac379226dfb9a22bbf438ac8dbef.js
191 ms
logo.png
227 ms
ico-dropdown.svg
142 ms
homepage_hero_image_1.jpg
257 ms
homepage_hero_image_2.jpg
257 ms
homepage_hero_image_3.jpg
318 ms
homepage_hero_image_4.jpg
297 ms
homepage_hero_image_5.jpg
376 ms
IP-2785-2_bb8a5828-ac4f-4267-ba9d-a3b4961f2cd7_large.jpeg
294 ms
IP-2785_52d5cb11-2124-4b54-9cba-80378a13a438_large.jpeg
293 ms
OL-SUONEOLC-2_3fbe5bef-3156-480f-b153-4244c0855435_large.jpeg
293 ms
OL-SUONEOLC_39016370-3ac5-43bf-9bee-f896336b0bfe_large.jpeg
379 ms
OL-SULTOUXL-2_dbda73b2-414b-4639-aa79-e1c5e90e781d_large.jpeg
375 ms
OL-SULTOUXL_638780b8-9d24-4665-9e4a-444ca9994b84_large.jpeg
382 ms
OL-SFWGLAXX_7d3d2473-095e-4f0d-81b3-7449bfa1b8ed_large.jpeg
378 ms
creditcards_american_express-54be4e6bfc1dbd42f93af603e102fde2356dfe2372a7dd851074964337533296.svg
375 ms
creditcards_master-94df290d56a3c6424296953282e18e46895ba94bdef368640eb52f8349915610.svg
401 ms
creditcards_visa-e9f829d15f5ec3b1953ba8b9bc59b448ddb1ec9235ae70c7936178744cb31489.svg
404 ms
oxl6trkJQKs
204 ms
561 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
189 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
222 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
269 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
268 ms
gk5FxslNkTTHtojXrkp-xD1GzwQ5qF9DNzkQQVRhJ4g.ttf
268 ms
ficon.woff
272 ms
identify
285 ms
analytics.js
167 ms
record.gif
265 ms
www-embed-player-vflfNyN_r.css
141 ms
www-embed-player.js
187 ms
base.js
217 ms
collect
36 ms
collect
274 ms
page
230 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
94 ms
ad_status.js
87 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
65 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
64 ms
10731592_1701318443486864_413885225_n.jpg
75 ms
12797603_510444665802006_572840106_n.jpg
107 ms
10448987_958832864234499_481448548_n.jpg
107 ms
12545492_1025877554124641_1001680668_n.jpg
119 ms
12816971_834151630029732_1216888294_n.jpg
120 ms
12783995_1512752829032027_1184478997_n.jpg
141 ms
12751371_1642499522680391_474427446_n.jpg
117 ms
12751192_195877177438739_1718053430_n.jpg
118 ms
12749944_188133771551482_1410579456_n.jpg
108 ms
12568770_1718805915022296_1056584209_n.jpg
121 ms
12479157_178586125849687_323824485_n.jpg
120 ms
12558932_1549717422009759_47735994_n.jpg
121 ms
pigeonhole.com accessibility score
pigeonhole.com 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
pigeonhole.com SEO score
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 Pigeonhole.com 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 Pigeonhole.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
pigeonhole.com
Open Graph data is detected on the main page of Pigeonhole. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: