Tools & Wizards About Us
nappertandys.ie screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nappertandys.ie

Napper Tandy's Dublin | Gastropub Dublin | Live Music Dublin

Page Load Speed

3.2 sec in total

First Response

1.2 sec

Resources Loaded

1.7 sec

Page Rendered

332 ms

nappertandys.ie screenshot

About Website

Welcome to nappertandys.ie homepage info - get ready to check Napper Tandy S best content right away, or after learning these important things about nappertandys.ie

Welcome to the homepage of Napper Tandy's Dublin.

Visit nappertandys.ie

Key Findings

We analyzed Nappertandys.ie page load time and found that the first response time was 1.2 sec and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

nappertandys.ie performance score

0

Network Requests Diagram

www.nappertandys.ie

1162 ms

minified.js

35 ms

focus-within-polyfill.js

29 ms

polyfill.min.js

31 ms

bootstrap-features.fce93483.chunk.min.js

28 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Nappertandys.ie, 78% (46 requests) were made to Static.parastorage.com and 8% (5 requests) were made to Sentry.wixpress.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Nappertandys.ie.

Page Optimization Overview & Recommendations

Page size can be reduced by 380.7 kB (70%)

Content Size

545.9 kB

After Optimization

165.2 kB

  • HTML
  • JavaScript

In fact, the total size of Nappertandys.ie main page is 545.9 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. 45% of websites need less resources to load. HTML takes 476.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 364.7 kB

  • Original 476.4 kB
  • After minification 474.7 kB
  • After compression 111.7 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 364.7 kB or 77% of the original size.

JavaScript Optimization

-23%

Potential reduce by 16.0 kB

  • Original 69.5 kB
  • After minification 67.8 kB
  • After compression 53.5 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 16.0 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (81%)

Requests Now

53

After Optimization

10

  • AJAX
  • Images
  • JavaScript

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Napper Tandy S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.nappertandys.ie

www.nappertandys.ie

1162 ms

minified.js

minified.js

35 ms

focus-within-polyfill.js

focus-within-polyfill.js

29 ms

polyfill.min.js

polyfill.min.js

31 ms

bootstrap-features.fce93483.chunk.min.js

bootstrap-features.fce93483.chunk.min.js

28 ms

main.d29849b1.chunk.min.js

main.d29849b1.chunk.min.js

121 ms

lodash.min.js

lodash.min.js

97 ms

wix-code-sdk-providers.517c667e.chunk.min.js

wix-code-sdk-providers.517c667e.chunk.min.js

97 ms

ooi.626bddc0.chunk.min.js

ooi.626bddc0.chunk.min.js

97 ms

siteMembers.c128a7fc.chunk.min.js

siteMembers.c128a7fc.chunk.min.js

119 ms

siteScrollBlocker.2d85e389.chunk.min.js

siteScrollBlocker.2d85e389.chunk.min.js

121 ms

tpaCommons.8ac98d67.chunk.min.js

tpaCommons.8ac98d67.chunk.min.js

122 ms

windowMessageRegistrar.e23bfeb8.chunk.min.js

windowMessageRegistrar.e23bfeb8.chunk.min.js

121 ms

platform.aa32d5f7.chunk.min.js

platform.aa32d5f7.chunk.min.js

123 ms

vendors~vendor-react-dom.f9bf9bd1.chunk.min.js

vendors~vendor-react-dom.f9bf9bd1.chunk.min.js

124 ms

vendor-react-dom.5a11925f.chunk.min.js

vendor-react-dom.5a11925f.chunk.min.js

122 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

123 ms

bolt-performance

bolt-performance

151 ms

dynamicmodel

dynamicmodel

98 ms

clientWorker.b6f2820a.bundle.min.js

clientWorker.b6f2820a.bundle.min.js

138 ms

bt

bt

134 ms

bundle.min.js

bundle.min.js

14 ms

99 ms

106 ms

lodash.min.js

lodash.min.js

3 ms

72 ms

custom-elements-polyfill.31a2b69b.chunk.min.js

custom-elements-polyfill.31a2b69b.chunk.min.js

19 ms

intersection-observer-polyfill.abdecffa.chunk.min.js

intersection-observer-polyfill.abdecffa.chunk.min.js

19 ms

thunderboltElements.b0a5c862.bundle.min.js

thunderboltElements.b0a5c862.bundle.min.js

21 ms

wix-perf-measure.bundle.min.js

wix-perf-measure.bundle.min.js

19 ms

activePopup.fc31c19e.chunk.min.js

activePopup.fc31c19e.chunk.min.js

19 ms

dropdownMenu.1c9b4960.chunk.min.js

dropdownMenu.1c9b4960.chunk.min.js

21 ms

navigation.c30741b8.chunk.min.js

navigation.c30741b8.chunk.min.js

20 ms

ooiTpaSharedConfig.e70ff4f5.chunk.min.js

ooiTpaSharedConfig.e70ff4f5.chunk.min.js

21 ms

pageScroll.245d2303.chunk.min.js

pageScroll.245d2303.chunk.min.js

21 ms

platformPubsub.96b30d03.chunk.min.js

platformPubsub.96b30d03.chunk.min.js

22 ms

scrollRestoration.2df380cd.chunk.min.js

scrollRestoration.2df380cd.chunk.min.js

25 ms

scrollToAnchor.57f65596.chunk.min.js

scrollToAnchor.57f65596.chunk.min.js

21 ms

tpa.6141c7ad.chunk.min.js

tpa.6141c7ad.chunk.min.js

22 ms

windowScroll.bbc645de.chunk.min.js

windowScroll.bbc645de.chunk.min.js

22 ms

landingPage.663351c5.chunk.min.js

landingPage.663351c5.chunk.min.js

23 ms

reducedMotion.895cf3c1.chunk.min.js

reducedMotion.895cf3c1.chunk.min.js

23 ms

bootstrap-components.0ae59aa1.chunk.min.js

bootstrap-components.0ae59aa1.chunk.min.js

24 ms

vendors~SlideShowContainer~SlideShowGallery_BlogSlideShow~SlideShowGallery_SlideShowCleanAndSimple~S~9112e461.43ee5e83.chunk.min.js

vendors~SlideShowContainer~SlideShowGallery_BlogSlideShow~SlideShowGallery_SlideShowCleanAndSimple~S~9112e461.43ee5e83.chunk.min.js

25 ms

SlideShowContainer~StateBox.6214b343.chunk.min.js

SlideShowContainer~StateBox.6214b343.chunk.min.js

27 ms

SlideShowContainer.5e0ed070.chunk.min.js

SlideShowContainer.5e0ed070.chunk.min.js

25 ms

FiveGridLine.d1611c63.chunk.min.js

FiveGridLine.d1611c63.chunk.min.js

25 ms

GoogleMap.d2b6132d.chunk.min.js

GoogleMap.d2b6132d.chunk.min.js

25 ms

SlideShowSlide.37629711.chunk.min.js

SlideShowSlide.37629711.chunk.min.js

27 ms

DropDownMenu_TextOnlyMenuButtonSkin.e4b71792.chunk.min.js

DropDownMenu_TextOnlyMenuButtonSkin.e4b71792.chunk.min.js

28 ms

tpa-components.0399e5b8.chunk.min.js

tpa-components.0399e5b8.chunk.min.js

26 ms

109 ms

105 ms

bt

bt

20 ms

4021a3b9-f782-438b-aeb4-c008109a8b64.woff

4021a3b9-f782-438b-aeb4-c008109a8b64.woff

12 ms

b56b944e-bbe0-4450-a241-de2125d3e682.woff

b56b944e-bbe0-4450-a241-de2125d3e682.woff

12 ms

6f8d1983-4d34-4fa4-9110-988f6c495757.woff

6f8d1983-4d34-4fa4-9110-988f6c495757.woff

12 ms

03805817-4611-4dbc-8c65-0f73031c3973.woff

03805817-4611-4dbc-8c65-0f73031c3973.woff

6 ms

80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff

80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff

11 ms

SEO Factors

nappertandys.ie SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nappertandys.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 Nappertandys.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.

Social Sharing Optimization

nappertandys.ie

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: