Tools & Wizards About Us
majesticfloats.co.nz screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    28% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 90% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    61% of websites

majesticfloats.co.nz

Home | Horse Transport NZ Wide | Majestic Horse Floats

Page Load Speed

8.9 sec in total

First Response

720 ms

Resources Loaded

7.2 sec

Page Rendered

980 ms

majesticfloats.co.nz screenshot

About Website

Visit majesticfloats.co.nz now to see the best up-to-date Majestic Floats content for New Zealand and also check out these interesting facts you probably never knew about majesticfloats.co.nz

Only the very best in horse transport. Call on Majestic for a first class trip, by our fully experienced team, in our fully equipped facilities.

Visit majesticfloats.co.nz

Key Findings

We analyzed Majesticfloats.co.nz page load time and found that the first response time was 720 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

majesticfloats.co.nz performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value20.0 s

0/100

10%

TBT (Total Blocking Time)

Value8,530 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value23.1 s

1/100

10%

Network Requests Diagram

majesticfloats.co.nz

720 ms

www.majesticfloats.co.nz

1896 ms

js

155 ms

js

219 ms

wp-emoji-release.min.js

328 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 68% of them (43 requests) were addressed to the original Majesticfloats.co.nz, 5% (3 requests) were made to Googletagmanager.com and 5% (3 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Majesticfloats.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.4 kB (14%)

Content Size

1.0 MB

After Optimization

887.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Majesticfloats.co.nz main page is 1.0 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. 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 762.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 50.7 kB

  • Original 66.0 kB
  • After minification 60.6 kB
  • After compression 15.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 50.7 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 47.9 kB

  • Original 762.9 kB
  • After minification 715.1 kB

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

JavaScript Optimization

-2%

Potential reduce by 1.6 kB

  • Original 89.3 kB
  • After minification 89.1 kB
  • After compression 87.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. This website has mostly compressed JavaScripts.

CSS Optimization

-38%

Potential reduce by 42.3 kB

  • Original 112.0 kB
  • After minification 107.6 kB
  • After compression 69.8 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. Majesticfloats.co.nz needs all CSS files to be minified and compressed as it can save up to 42.3 kB or 38% of the original size.

Requests Breakdown

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

Requests Now

57

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

majesticfloats.co.nz

majesticfloats.co.nz

720 ms

www.majesticfloats.co.nz

www.majesticfloats.co.nz

1896 ms

js

js

155 ms

js

js

219 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

328 ms

style.min.css

style.min.css

585 ms

style-wpzoom-social-icons.css

style-wpzoom-social-icons.css

683 ms

simple-banner.css

simple-banner.css

710 ms

bundle.css

bundle.css

915 ms

wpzoom-socicon.css

wpzoom-socicon.css

690 ms

genericons.css

genericons.css

687 ms

academicons.min.css

academicons.min.css

807 ms

font-awesome-3.min.css

font-awesome-3.min.css

880 ms

dashicons.min.css

dashicons.min.css

1090 ms

wpzoom-social-icons-styles.css

wpzoom-social-icons-styles.css

893 ms

frontend-gtag.min.js

frontend-gtag.min.js

914 ms

jquery.min.js

jquery.min.js

1221 ms

jquery-migrate.min.js

jquery-migrate.min.js

1072 ms

simple-banner.js

simple-banner.js

1100 ms

conversion_async.js

conversion_async.js

112 ms

js

js

83 ms

content.css

content.css

1030 ms

js

js

168 ms

custom.js

custom.js

1004 ms

js

js

302 ms

6879965.js

6879965.js

287 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

200 ms

bundle.js

bundle.js

1448 ms

social-icons-widget-frontend.js

social-icons-widget-frontend.js

1448 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

1449 ms

jquery-actual.min.js

jquery-actual.min.js

1479 ms

imagesloaded.min.js

imagesloaded.min.js

1478 ms

underscore.min.js

underscore.min.js

1502 ms

verge.min.js

verge.min.js

1502 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1501 ms

wp-polyfill.min.js

wp-polyfill.min.js

1501 ms

hooks.min.js

hooks.min.js

2121 ms

i18n.min.js

i18n.min.js

2119 ms

jquery-strongslider.min.js

jquery-strongslider.min.js

2187 ms

controller.min.js

controller.min.js

2183 ms

analytics.js

analytics.js

140 ms

160 ms

linkid.js

linkid.js

72 ms

collect

collect

51 ms

123 ms

collect

collect

120 ms

hotjar-1615302.js

hotjar-1615302.js

947 ms

fbevents.js

fbevents.js

936 ms

majestic-logo.svg

majestic-logo.svg

938 ms

burger.svg

burger.svg

942 ms

Majestic-DEC-2018-_082_Retouched.jpg

Majestic-DEC-2018-_082_Retouched.jpg

1762 ms

Majestic-DEC-2018-_086.jpg

Majestic-DEC-2018-_086.jpg

1218 ms

Majestic-DEC-2018-_106.jpg

Majestic-DEC-2018-_106.jpg

1319 ms

Majestic-DEC-2018-_061-e1553206774498.jpg

Majestic-DEC-2018-_061-e1553206774498.jpg

1428 ms

play.svg

play.svg

951 ms

close.svg

close.svg

953 ms

PlayfairDisplay-Bold.ttf

PlayfairDisplay-Bold.ttf

934 ms

Montserrat-Bold.ttf

Montserrat-Bold.ttf

1191 ms

Montserrat-Regular.ttf

Montserrat-Regular.ttf

1518 ms

gen_204

gen_204

445 ms

identity.js

identity.js

43 ms

2628569464038948

2628569464038948

183 ms

modules.61e17720cf639c3e96a7.js

modules.61e17720cf639c3e96a7.js

182 ms

Accessibility Review

majesticfloats.co.nz accessibility score

96

Accessibility Issues

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

High

button, link, and menuitem elements do not have accessible names.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

majesticfloats.co.nz best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

majesticfloats.co.nz SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Majesticfloats.co.nz 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 Majesticfloats.co.nz 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

majesticfloats.co.nz

Open Graph data is detected on the main page of Majestic Floats. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: