Tools & Wizards About Us
disco.wedding screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

disco.wedding

PM Mobile Disco Services: Wedding Entertainment Specialist N.Ireland

Page Load Speed

6 sec in total

First Response

315 ms

Resources Loaded

5.4 sec

Page Rendered

250 ms

disco.wedding screenshot

About Website

Visit disco.wedding now to see the best up-to-date Disco content and also check out these interesting facts you probably never knew about disco.wedding

PM Mobile Disco Services specialises in providing Wedding Entertainment across Ireland North and South. The perfect end to your perfect wedding day. Est. 1992

Visit disco.wedding

Key Findings

We analyzed Disco.wedding page load time and found that the first response time was 315 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

disco.wedding performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.185

66/100

15%

TTI (Time to Interactive)

Value6.7 s

57/100

10%

Network Requests Diagram

disco.wedding

315 ms

css

15 ms

css

29 ms

css

29 ms

style.css

1096 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 80% of them (73 requests) were addressed to the original Disco.wedding, 7% (6 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Disco.wedding.

Page Optimization Overview & Recommendations

Page size can be reduced by 174.2 kB (6%)

Content Size

2.8 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Disco.wedding main page is 2.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 51.0 kB

  • Original 61.8 kB
  • After minification 48.1 kB
  • After compression 10.8 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. This page needs HTML code to be minified as it can gain 13.7 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 51.0 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 71.0 kB

  • Original 2.4 MB
  • After minification 2.3 MB

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. Disco images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 41.0 kB

  • Original 320.7 kB
  • After minification 318.8 kB
  • After compression 279.7 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 41.0 kB or 13% of the original size.

CSS Optimization

-35%

Potential reduce by 11.2 kB

  • Original 32.1 kB
  • After minification 32.1 kB
  • After compression 21.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. Disco.wedding needs all CSS files to be minified and compressed as it can save up to 11.2 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (49%)

Requests Now

51

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

disco.wedding

disco.wedding

315 ms

css

css

15 ms

css

css

29 ms

css

css

29 ms

style.css

style.css

1096 ms

colors.php

colors.php

404 ms

tipsy.css

tipsy.css

248 ms

jquery.fancybox.css

jquery.fancybox.css

261 ms

responsive.css

responsive.css

250 ms

jquery.js

jquery.js

328 ms

jquery.easing.js

jquery.easing.js

1112 ms

superfish.js

superfish.js

1114 ms

jquery.isotope.js

jquery.isotope.js

1112 ms

jquery.flexslider.js

jquery.flexslider.js

1112 ms

jquery.fitvids.js

jquery.fitvids.js

1117 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

1350 ms

jquery.tipsy.js

jquery.tipsy.js

1359 ms

jquery.carouFredSel.js

jquery.carouFredSel.js

1438 ms

jquery.touchwipe.js

jquery.touchwipe.js

1348 ms

jquery.fancybox.js

jquery.fancybox.js

1366 ms

jquery.form.js

jquery.form.js

1359 ms

jquery.uniform.js

jquery.uniform.js

1597 ms

api.js

api.js

38 ms

custom.js

custom.js

1620 ms

jquery.validate.min.js

jquery.validate.min.js

17 ms

recaptcha__en.js

recaptcha__en.js

83 ms

plivalidator_blue.gif

plivalidator_blue.gif

479 ms

cs-gy-3d-234x16.gif

cs-gy-3d-234x16.gif

165 ms

body.png

body.png

251 ms

PMLogo.jpg

PMLogo.jpg

328 ms

slider7.jpg

slider7.jpg

506 ms

slider.jpg

slider.jpg

521 ms

slider0.jpg

slider0.jpg

508 ms

equipment-ml.jpg

equipment-ml.jpg

1077 ms

equipment-vid.jpg

equipment-vid.jpg

665 ms

slider1.jpg

slider1.jpg

841 ms

slider1a.jpg

slider1a.jpg

936 ms

slider2.jpg

slider2.jpg

925 ms

slider3.jpg

slider3.jpg

986 ms

slider4.jpg

slider4.jpg

1069 ms

slider6.jpg

slider6.jpg

1323 ms

slider5.jpg

slider5.jpg

1566 ms

user.png

user.png

1170 ms

equalizer.png

equalizer.png

1229 ms

map.png

map.png

1319 ms

calendar.png

calendar.png

1325 ms

headphone.png

headphone.png

1414 ms

gkey.png

gkey.png

1464 ms

lougherne.jpg

lougherne.jpg

1724 ms

galgorm.jpg

galgorm.jpg

1648 ms

nuremore.jpg

nuremore.jpg

1644 ms

roepark.jpg

roepark.jpg

1745 ms

ballydugan.jpg

ballydugan.jpg

1716 ms

ramada.jpg

ramada.jpg

1816 ms

darver.jpg

darver.jpg

1903 ms

culloden.jpg

culloden.jpg

1896 ms

ballygally.jpg

ballygally.jpg

1968 ms

lustybeg.jpg

lustybeg.jpg

1966 ms

nomadic.jpg

nomadic.jpg

1994 ms

laragh.jpg

laragh.jpg

2057 ms

redcastle.jpg

redcastle.jpg

2147 ms

glenavon.jpg

glenavon.jpg

2142 ms

montalto.jpg

montalto.jpg

2201 ms

jizaRExUiTo99u79D0KEwA.ttf

jizaRExUiTo99u79D0KEwA.ttf

18 ms

jizfRExUiTo99u79B_mh0O6tKA.ttf

jizfRExUiTo99u79B_mh0O6tKA.ttf

60 ms

crover.jpg

crover.jpg

2183 ms

sdk.js

sdk.js

107 ms

tDbK2oqRg1oM3QBjjcaDkOr4nAfcGw.ttf

tDbK2oqRg1oM3QBjjcaDkOr4nAfcGw.ttf

105 ms

tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf

tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf

105 ms

SlGVmQWMvZQIdix7AFxXkHNSaA.ttf

SlGVmQWMvZQIdix7AFxXkHNSaA.ttf

55 ms

SlGWmQWMvZQIdix7AFxXmMh3eDs1Yg.ttf

SlGWmQWMvZQIdix7AFxXmMh3eDs1Yg.ttf

55 ms

sdk.js

sdk.js

28 ms

burrendale.jpg

burrendale.jpg

1986 ms

lodge.jpg

lodge.jpg

1977 ms

ballymac.jpg

ballymac.jpg

1900 ms

corick.jpg

corick.jpg

1884 ms

PMLogoSmall.jpg

PMLogoSmall.jpg

1938 ms

signpost.png

signpost.png

1797 ms

telephone4.png

telephone4.png

1648 ms

facebook.png

facebook.png

1619 ms

home.png

home.png

1705 ms

dots.png

dots.png

1660 ms

portfolio-navigation-icons.png

portfolio-navigation-icons.png

1634 ms

mail.png

mail.png

1625 ms

portfolio-widget.png

portfolio-widget.png

1578 ms

go-to-top.png

go-to-top.png

1557 ms

preloader.gif

preloader.gif

1609 ms

slider-prev.png

slider-prev.png

242 ms

slider-next.png

slider-next.png

252 ms

144 ms

107 ms

Accessibility Review

disco.wedding accessibility score

79

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

disco.wedding best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

disco.wedding SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

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 Disco.wedding 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 Disco.wedding 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

disco.wedding

Open Graph description is not detected on the main page of Disco. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: