Tools & Wizards About Us
disco.wedding screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% 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.2 sec in total

First Response

346 ms

Resources Loaded

5.6 sec

Page Rendered

239 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 346 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

disco.wedding performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value5.4 s

57/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.106

88/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

disco.wedding

346 ms

css

21 ms

css

36 ms

css

39 ms

style.css

399 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 77% of them (73 requests) were addressed to the original Disco.wedding, 6% (6 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Disco.wedding.

Page Optimization Overview & Recommendations

Page size can be reduced by 160.3 kB (5%)

Content Size

3.1 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Disco.wedding main page is 3.1 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.6 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 48.0 kB

  • Original 58.3 kB
  • After minification 44.6 kB
  • After compression 10.3 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 23% 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 48.0 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 78.2 kB

  • Original 2.6 MB
  • After minification 2.6 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

-7%

Potential reduce by 22.8 kB

  • Original 323.4 kB
  • After minification 323.4 kB
  • After compression 300.6 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.

CSS Optimization

-35%

Potential reduce by 11.4 kB

  • Original 32.4 kB
  • After minification 32.4 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.4 kB or 35% of the original size.

Requests Breakdown

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

Requests Now

72

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 72 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

346 ms

css

css

21 ms

css

css

36 ms

css

css

39 ms

style.css

style.css

399 ms

colors.php

colors.php

450 ms

tipsy.css

tipsy.css

323 ms

jquery.fancybox.css

jquery.fancybox.css

330 ms

responsive.css

responsive.css

331 ms

jquery.js

jquery.js

416 ms

jquery.easing.js

jquery.easing.js

638 ms

superfish.js

superfish.js

641 ms

jquery.isotope.js

jquery.isotope.js

640 ms

jquery.flexslider.js

jquery.flexslider.js

715 ms

jquery.fitvids.js

jquery.fitvids.js

733 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

757 ms

jquery.tipsy.js

jquery.tipsy.js

948 ms

jquery.carouFredSel.js

jquery.carouFredSel.js

959 ms

jquery.touchwipe.js

jquery.touchwipe.js

981 ms

jquery.fancybox.js

jquery.fancybox.js

1025 ms

jquery.form.js

jquery.form.js

1044 ms

jquery.uniform.js

jquery.uniform.js

1076 ms

api.js

api.js

35 ms

custom.js

custom.js

1259 ms

jquery.validate.min.js

jquery.validate.min.js

11 ms

recaptcha__en.js

recaptcha__en.js

70 ms

plivalidator_blue.gif

plivalidator_blue.gif

439 ms

cs-gy-3d-234x16.gif

cs-gy-3d-234x16.gif

119 ms

body.png

body.png

327 ms

PMLogo.jpg

PMLogo.jpg

325 ms

slider7.jpg

slider7.jpg

603 ms

slider.jpg

slider.jpg

602 ms

slider0.jpg

slider0.jpg

603 ms

equipment-ml.jpg

equipment-ml.jpg

964 ms

equipment-vid.jpg

equipment-vid.jpg

783 ms

slider1.jpg

slider1.jpg

865 ms

slider1a.jpg

slider1a.jpg

1069 ms

slider2.jpg

slider2.jpg

1065 ms

slider3.jpg

slider3.jpg

1146 ms

slider4.jpg

slider4.jpg

1246 ms

slider6.jpg

slider6.jpg

1414 ms

slider5.jpg

slider5.jpg

1512 ms

user.png

user.png

1381 ms

equalizer.png

equalizer.png

1384 ms

map.png

map.png

1464 ms

calendar.png

calendar.png

1561 ms

headphone.png

headphone.png

1694 ms

gkey.png

gkey.png

1700 ms

lougherne.jpg

lougherne.jpg

1733 ms

galgorm.jpg

galgorm.jpg

1869 ms

nuremore.jpg

nuremore.jpg

1896 ms

roepark.jpg

roepark.jpg

1948 ms

ballydugan.jpg

ballydugan.jpg

2093 ms

ramada.jpg

ramada.jpg

2091 ms

darver.jpg

darver.jpg

2047 ms

culloden.jpg

culloden.jpg

2260 ms

ballygally.jpg

ballygally.jpg

2289 ms

lustybeg.jpg

lustybeg.jpg

2265 ms

nomadic.jpg

nomadic.jpg

2439 ms

laragh.jpg

laragh.jpg

2488 ms

redcastle.jpg

redcastle.jpg

2408 ms

glenavon.jpg

glenavon.jpg

2646 ms

montalto.jpg

montalto.jpg

2636 ms

jizaRExUiTo99u79D0KEwA.ttf

jizaRExUiTo99u79D0KEwA.ttf

49 ms

jizfRExUiTo99u79B_mh0O6tKA.ttf

jizfRExUiTo99u79B_mh0O6tKA.ttf

52 ms

sdk.js

sdk.js

93 ms

tDbK2oqRg1oM3QBjjcaDkOr4nAfcGw.ttf

tDbK2oqRg1oM3QBjjcaDkOr4nAfcGw.ttf

43 ms

tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf

tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf

43 ms

SlGVmQWMvZQIdix7AFxXkHNSaA.ttf

SlGVmQWMvZQIdix7AFxXkHNSaA.ttf

49 ms

SlGWmQWMvZQIdix7AFxXmMh3eDs1Yg.ttf

SlGWmQWMvZQIdix7AFxXmMh3eDs1Yg.ttf

49 ms

sdk.js

sdk.js

5 ms

page.php

page.php

64 ms

page.php

page.php

109 ms

crover.jpg

crover.jpg

2477 ms

MpdfZ1mwXmC.png

MpdfZ1mwXmC.png

13 ms

uvau2ZhqVkD.png

uvau2ZhqVkD.png

12 ms

hXLpopTsiHV.png

hXLpopTsiHV.png

14 ms

U-w7kFfb7fy.png

U-w7kFfb7fy.png

15 ms

burrendale.jpg

burrendale.jpg

2402 ms

lodge.jpg

lodge.jpg

2513 ms

ballymac.jpg

ballymac.jpg

2203 ms

corick.jpg

corick.jpg

2363 ms

PMLogoSmall.jpg

PMLogoSmall.jpg

2364 ms

signpost.png

signpost.png

2218 ms

telephone4.png

telephone4.png

2174 ms

facebook.png

facebook.png

2154 ms

home.png

home.png

2092 ms

dots.png

dots.png

2213 ms

portfolio-navigation-icons.png

portfolio-navigation-icons.png

2135 ms

mail.png

mail.png

2070 ms

portfolio-widget.png

portfolio-widget.png

1972 ms

go-to-top.png

go-to-top.png

2051 ms

preloader.gif

preloader.gif

2062 ms

slider-prev.png

slider-prev.png

316 ms

slider-next.png

slider-next.png

317 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: