5.4 sec in total
1.3 sec
3.3 sec
822 ms
Welcome to pauldonnelly.net homepage info - get ready to check Paul Donnelly best content for India right away, or after learning these important things about pauldonnelly.net
Magento Certified Web Developer based in Belfast, Northern Ireland with over 11 years eCommerce experience in Magento 2 & Magento 1
Visit pauldonnelly.netWe analyzed Pauldonnelly.net page load time and found that the first response time was 1.3 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
pauldonnelly.net performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value10.2 s
0/100
25%
Value9.1 s
14/100
10%
Value120 ms
97/100
30%
Value0.201
62/100
15%
Value10.2 s
25/100
10%
1305 ms
382 ms
259 ms
26 ms
317 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 68% of them (21 requests) were addressed to the original Pauldonnelly.net, 16% (5 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Pauldonnelly.net.
Page size can be reduced by 261.1 kB (48%)
539.1 kB
278.0 kB
In fact, the total size of Pauldonnelly.net main page is 539.1 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. 30% of websites need less resources to load. Images take 209.1 kB which makes up the majority of the site volume.
Potential reduce by 44.5 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 44.5 kB or 80% of the original size.
Potential reduce by 24.2 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. Obviously, Paul Donnelly needs image optimization as it can save up to 24.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 118.4 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 118.4 kB or 68% of the original size.
Potential reduce by 73.9 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. Pauldonnelly.net needs all CSS files to be minified and compressed as it can save up to 73.9 kB or 73% of the original size.
Number of requests can be reduced by 13 (54%)
24
11
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Paul Donnelly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.pauldonnelly.net
1305 ms
wp-emoji-release.min.js
382 ms
styles.css
259 ms
css
26 ms
wp-syntax.css
317 ms
css
61 ms
genericons.css
534 ms
style.css
768 ms
jquery.js
473 ms
jquery-migrate.min.js
346 ms
jquery.form.min.js
337 ms
scripts.js
280 ms
ssba.min.js
302 ms
skip-link-focus-fix.js
368 ms
functions.js
386 ms
wp-embed.min.js
409 ms
e6c8601289a7372bfbce3fd70b61359b
77 ms
Screen-Shot-2015-01-21-at-16.00.50.png
240 ms
Screen-Shot-2015-01-21-at-16.20.23.png
241 ms
Screen-Shot-2015-01-21-at-16.28.18.png
242 ms
angularjs.png
240 ms
simple-smile.png
239 ms
newcmspage.jpg
325 ms
RFda8w1V0eDZheqfcyQ4ENqQynqKV_9Plp7mupa0S4g.ttf
29 ms
ZvcMqxEwPfh2qDWBPxn6nqp5NA6AAOjfQM_HmvD0shQ.ttf
50 ms
ZvcMqxEwPfh2qDWBPxn6ngvr42gIYPGl20Rgir8ypAU.ttf
93 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
87 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
93 ms
Genericons.svg
282 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
2 ms
13_160x600.png
168 ms
pauldonnelly.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
pauldonnelly.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
pauldonnelly.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pauldonnelly.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 Pauldonnelly.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.
pauldonnelly.net
Open Graph data is detected on the main page of Paul Donnelly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: