3.9 sec in total
222 ms
3.6 sec
56 ms
Visit puca.ie now to see the best up-to-date Puca content and also check out these interesting facts you probably never knew about puca.ie
The business messaging experts. Simple, powerful consoles and APIs.
Visit puca.ieWe analyzed Puca.ie page load time and found that the first response time was 222 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
puca.ie performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value6.5 s
9/100
25%
Value11.4 s
5/100
10%
Value140 ms
95/100
30%
Value0.002
100/100
15%
Value8.4 s
38/100
10%
222 ms
173 ms
2116 ms
20 ms
138 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Puca.ie, 72% (39 requests) were made to Kb.puca.com and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Kb.puca.com.
Page size can be reduced by 137.6 kB (32%)
431.0 kB
293.4 kB
In fact, the total size of Puca.ie main page is 431.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. 30% of websites need less resources to load. Javascripts take 191.9 kB which makes up the majority of the site volume.
Potential reduce by 111.4 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 111.4 kB or 88% of the original size.
Potential reduce by 18 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. Puca images are well optimized though.
Potential reduce by 21.2 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 21.2 kB or 11% of the original size.
Potential reduce by 5.0 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. Puca.ie has all CSS files already compressed.
Number of requests can be reduced by 37 (76%)
49
12
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Puca. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
puca.ie
222 ms
kb.puca.com
173 ms
kb.puca.com
2116 ms
uc.js
20 ms
widget.css
138 ms
front.min.css
205 ms
mashsb.min.css
308 ms
mashnet.min.css
219 ms
dashicons.min.css
287 ms
style.css
220 ms
main.css
329 ms
owl.css
274 ms
selectbox.css
286 ms
animate.css
288 ms
frontend.min.js
343 ms
jquery.js
435 ms
jquery-migrate.min.js
363 ms
front.min.js
362 ms
mashsb.min.js
382 ms
mashnet.min.js
398 ms
modernizr.js
414 ms
bootstrap.min.js
436 ms
owl.js
504 ms
smooth.js
450 ms
selectbox.js
470 ms
jquery.appear.js
490 ms
main.js
510 ms
ajax-tags.js
509 ms
analytics.js
47 ms
wp-emoji-release.min.js
471 ms
2555982.js
347 ms
hoverIntent.min.js
484 ms
maxmegamenu.js
501 ms
wp-embed.min.js
555 ms
conversion.js
102 ms
linkid.js
7 ms
collect
12 ms
collect
25 ms
style.css
366 ms
w.js
43 ms
fbevents.js
50 ms
hotjar-299017.js
116 ms
menu.png
95 ms
menu-open.png
72 ms
imp-1.png
95 ms
imp-2.png
95 ms
imp-3.png
71 ms
imp-4.png
94 ms
30F812_1_0.woff
129 ms
30F812_0_0.woff
128 ms
69 ms
insight.min.js
53 ms
insight_tag_errors.gif
86 ms
28 ms
puca.ie 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
Links do not have a discernible name
puca.ie 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
puca.ie SEO score
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 Puca.ie 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 Puca.ie 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.
puca.ie
Open Graph data is detected on the main page of Puca. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: