4 sec in total
351 ms
2.8 sec
789 ms
Visit gordonpennycook.net now to see the best up-to-date Gordon Pennycook content and also check out these interesting facts you probably never knew about gordonpennycook.net
grpennycook@gmail.com / gordon.pennycook@uregina.ca Google Scholar / Twitter / OSF / Faculty Profile / CV / List of misinformation-related papers Background and Education I am an Associate Professor o...
Visit gordonpennycook.netWe analyzed Gordonpennycook.net page load time and found that the first response time was 351 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
gordonpennycook.net performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value4.2 s
44/100
25%
Value4.6 s
70/100
10%
Value1,570 ms
13/100
30%
Value0.301
39/100
15%
Value11.2 s
20/100
10%
351 ms
107 ms
140 ms
158 ms
175 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Gordonpennycook.net, 17% (6 requests) were made to Youtube.com and 14% (5 requests) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (699 ms) relates to the external source Gordonpennycook.files.wordpress.com.
Page size can be reduced by 377.4 kB (63%)
597.0 kB
219.5 kB
In fact, the total size of Gordonpennycook.net main page is 597.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 376.2 kB which makes up the majority of the site volume.
Potential reduce by 39.9 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 39.9 kB or 72% of the original size.
Potential reduce by 0 B
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. Gordon Pennycook images are well optimized though.
Potential reduce by 25.9 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 25.9 kB or 33% of the original size.
Potential reduce by 311.6 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. Gordonpennycook.net needs all CSS files to be minified and compressed as it can save up to 311.6 kB or 83% of the original size.
Number of requests can be reduced by 23 (68%)
34
11
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gordon Pennycook. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
gordonpennycook.net
351 ms
webfont.js
107 ms
wp-emoji-release.min.js
140 ms
158 ms
175 ms
171 ms
201 ms
global-print.css
219 ms
gprofiles.js
91 ms
wpgroho.js
240 ms
responsive-videos.css
229 ms
230 ms
w.js
109 ms
bilmur.min.js
65 ms
css
103 ms
ignobel_bs21.jpg
89 ms
bXCYtClPUSM
170 ms
gord.jpg
699 ms
ignobel_bs21.jpg
54 ms
g.gif
43 ms
hovercard.min.css
11 ms
services.min.css
7 ms
remote-login.php
166 ms
g.gif
31 ms
g.gif
31 ms
www-player.css
15 ms
www-embed-player.js
100 ms
base.js
161 ms
fetch-polyfill.js
97 ms
ad_status.js
651 ms
iKtgsnIEnramb_phg3pCdiFWxTNl0zmfFT58AYYWou0.js
552 ms
embed.js
82 ms
id
58 ms
Create
636 ms
actionbar.css
25 ms
actionbar.js
65 ms
gordonpennycook.net 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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
gordonpennycook.net 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
Page has valid source maps
gordonpennycook.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gordonpennycook.net 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 Gordonpennycook.net 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.
gordonpennycook.net
Open Graph data is detected on the main page of Gordon Pennycook. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: