9 sec in total
419 ms
7.6 sec
888 ms
Welcome to jfp.ie homepage info - get ready to check Jfp best content for Ireland right away, or after learning these important things about jfp.ie
Famed as Ireland's 'highest' pub, traditional Irish music nightly, famous Irish dancing 'Hooley Show' and an amazing sea food restaurant
Visit jfp.ieWe analyzed Jfp.ie page load time and found that the first response time was 419 ms and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
jfp.ie performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value16.0 s
0/100
25%
Value16.2 s
0/100
10%
Value1,020 ms
26/100
30%
Value0.004
100/100
15%
Value17.3 s
4/100
10%
419 ms
3110 ms
163 ms
229 ms
226 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Jfp.ie, 84% (92 requests) were made to Johnniefoxs.com and 5% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Johnniefoxs.com.
Page size can be reduced by 189.4 kB (20%)
949.5 kB
760.1 kB
In fact, the total size of Jfp.ie main page is 949.5 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. Images take 291.9 kB which makes up the majority of the site volume.
Potential reduce by 179.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 179.9 kB or 83% of the original size.
Potential reduce by 916 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. Jfp images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 7.3 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. Jfp.ie has all CSS files already compressed.
Number of requests can be reduced by 89 (89%)
100
11
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jfp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 43 to 1 for CSS and as a result speed up the page load time.
jfp.ie
419 ms
johnniefoxs.com
3110 ms
gtranslate-style24.css
163 ms
sbi-styles.min.css
229 ms
cookie-law-info-public.css
226 ms
cookie-law-info-gdpr.css
230 ms
woocommerce-layout.css
232 ms
woocommerce.css
234 ms
grid-system.css
239 ms
style.css
380 ms
header-secondary-nav.css
301 ms
element-fancy-box.css
302 ms
element-wpb-column-border.css
307 ms
css
32 ms
responsive.css
316 ms
product-style-classic.css
313 ms
woocommerce.css
387 ms
select2.css
377 ms
skin-material.css
391 ms
menu-dynamic.css
394 ms
default.css
395 ms
js_composer.min.css
452 ms
salient-dynamic-styles.css
499 ms
style.css
452 ms
css
33 ms
jquery.min.js
512 ms
jquery-migrate.min.js
461 ms
wp-polyfill-inert.min.js
464 ms
regenerator-runtime.min.js
524 ms
wp-polyfill.min.js
531 ms
hooks.min.js
537 ms
w.js
25 ms
cookie-law-info-public.js
540 ms
jquery.blockUI.min.js
573 ms
add-to-cart.min.js
574 ms
js.cookie.min.js
598 ms
woocommerce.min.js
605 ms
script.js
611 ms
qfv8rzd.css
117 ms
js
78 ms
css2
34 ms
gravity-forms-theme-reset.min.css
582 ms
gravity-forms-theme-foundation.min.css
584 ms
api.js
39 ms
gravity-forms-theme-framework.min.css
676 ms
wc-blocks.css
538 ms
animate.min.css
537 ms
formreset.min.css
535 ms
formsmain.min.css
543 ms
readyclass.min.css
539 ms
browsers.min.css
537 ms
cookie-law-info-table.css
475 ms
style-non-critical.css
481 ms
font-awesome.min.css
492 ms
woocommerce-non-critical.css
539 ms
jquery.fancybox.css
534 ms
core.css
475 ms
fullscreen-legacy.css
467 ms
sourcebuster.min.js
515 ms
order-attribution.min.js
594 ms
jquery.easing.min.js
595 ms
jquery.mousewheel.min.js
595 ms
priority.js
535 ms
transit.min.js
534 ms
waypoints.js
524 ms
imagesLoaded.min.js
563 ms
hoverintent.min.js
516 ms
jquery.fancybox.min.js
506 ms
anime.min.js
504 ms
superfish.js
494 ms
g.gif
13 ms
init.js
907 ms
touchswipe.min.js
902 ms
select2.full.min.js
871 ms
smush-lazy-load.min.js
870 ms
cart-fragments.min.js
847 ms
js_composer_front.min.js
840 ms
p.css
47 ms
dom-ready.min.js
794 ms
i18n.min.js
792 ms
a11y.min.js
792 ms
jquery.json.min.js
697 ms
gravityforms.min.js
697 ms
jquery.maskedinput.min.js
696 ms
utils.min.js
696 ms
vendor-theme.min.js
696 ms
element.js
80 ms
scripts-theme.min.js
687 ms
frontend.min.js
687 ms
akismet-frontend.js
687 ms
0ybgGDoxxrvAnPhYGzMlQLzuMasz6Df2MHGeHmmZ.ttf
75 ms
0ybgGDoxxrvAnPhYGzMlQLzuMasz6Df213aeHmmZ.ttf
76 ms
sbi-scripts.min.js
687 ms
placeholders.jquery.min.js
665 ms
sbi-sprite.png
664 ms
icomoon.woff
611 ms
Asset-11.svg
611 ms
Asset-23.svg
615 ms
If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BMSoHTQ.ttf
55 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnfY3lCA.ttf
135 ms
0ybuGDoxxrvAnPhYGxksckM2WMCpRjDj-DJGWlmeObE.ttf
135 ms
recaptcha__de.js
167 ms
woocommerce-smallscreen.css
108 ms
fontawesome-webfont.svg
251 ms
442435591_18337886539143928_6671025985360340140_nfull.jpg
181 ms
445614774_1112219186743435_5351318948410301540_nfull.jpg
181 ms
444931214_475086725047168_7918944489365630224_nfull.jpg
225 ms
443875919_1809015429592094_8321399984126919624_nfull.jpg
209 ms
fontawesome-webfont.woff
173 ms
jfp.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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
jfp.ie 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
jfp.ie 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 Jfp.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 Jfp.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.
jfp.ie
Open Graph data is detected on the main page of Jfp. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: