Tools & Wizards About Us
agapeweddings.co.za screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

agapeweddings.co.za

Page Load Speed

4.7 sec in total

First Response

1.3 sec

Resources Loaded

3.1 sec

Page Rendered

276 ms

agapeweddings.co.za screenshot

About Website

Visit agapeweddings.co.za now to see the best up-to-date Agapeweddings content and also check out these interesting facts you probably never knew about agapeweddings.co.za

AGAPE (Ancient Greek) represents divine, unconditional, self-sacrificing, active, volitional, and thoughtful love. Thank you for visiting the AGAPE website! We

Visit agapeweddings.co.za

Key Findings

We analyzed Agapeweddings.co.za page load time and found that the first response time was 1.3 sec and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

agapeweddings.co.za performance score

0

Network Requests Diagram

agapeweddings.co.za

1334 ms

analytics.js

36 ms

wp-emoji-release.min.js

261 ms

testimonials.css

295 ms

style.css

260 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 77% of them (44 requests) were addressed to the original Agapeweddings.co.za, 11% (6 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Agapeweddings.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 396.6 kB (13%)

Content Size

3.0 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Agapeweddings.co.za main page is 3.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. 55% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 30.2 kB

  • Original 38.2 kB
  • After minification 35.6 kB
  • After compression 8.0 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 30.2 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 68.6 kB

  • Original 2.6 MB
  • After minification 2.5 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. Agapeweddings images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 118.6 kB

  • Original 200.8 kB
  • After minification 197.4 kB
  • After compression 82.2 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 118.6 kB or 59% of the original size.

CSS Optimization

-85%

Potential reduce by 179.2 kB

  • Original 211.8 kB
  • After minification 174.5 kB
  • After compression 32.6 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. Agapeweddings.co.za needs all CSS files to be minified and compressed as it can save up to 179.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (36%)

Requests Now

50

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

agapeweddings.co.za

agapeweddings.co.za

1334 ms

analytics.js

analytics.js

36 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

261 ms

testimonials.css

testimonials.css

295 ms

style.css

style.css

260 ms

style.css

style.css

337 ms

layout.css

layout.css

263 ms

jetpack.css

jetpack.css

268 ms

jquery.js

jquery.js

502 ms

jquery-migrate.min.js

jquery-migrate.min.js

414 ms

third-party.js

third-party.js

410 ms

modernizr.js

modernizr.js

406 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

397 ms

general.js

general.js

429 ms

shortcodes.css

shortcodes.css

520 ms

custom.css

custom.css

522 ms

css

css

33 ms

comment-reply.min.js

comment-reply.min.js

560 ms

devicepx-jetpack.js

devicepx-jetpack.js

29 ms

wp-embed.min.js

wp-embed.min.js

534 ms

e-201611.js

e-201611.js

29 ms

collect

collect

11 ms

FINAL-3.png

FINAL-3.png

150 ms

facebook.gif

facebook.gif

117 ms

pinterest.gif

pinterest.gif

126 ms

instagram.gif

instagram.gif

125 ms

email.gif

email.gif

130 ms

home11.jpg

home11.jpg

408 ms

home5.jpg

home5.jpg

705 ms

home4.jpg

home4.jpg

799 ms

home6.jpg

home6.jpg

624 ms

home2.jpg

home2.jpg

746 ms

home3.jpg

home3.jpg

732 ms

home6.jpg

home6.jpg

707 ms

home5.jpg

home5.jpg

916 ms

home4.jpg

home4.jpg

998 ms

home10.jpg

home10.jpg

1001 ms

home11.jpg

home11.jpg

1020 ms

about5.jpg

about5.jpg

948 ms

services6.jpg

services6.jpg

1102 ms

portfolio1.jpg

portfolio1.jpg

1021 ms

recent-weddings.gif

recent-weddings.gif

1047 ms

1_0341-214x143.jpg

1_0341-214x143.jpg

1120 ms

ReneDirk_sml-577-214x143.jpg

ReneDirk_sml-577-214x143.jpg

1135 ms

Smaller-size-343-214x143.jpg

Smaller-size-343-214x143.jpg

1202 ms

TM-283-214x142.jpg

TM-283-214x142.jpg

1153 ms

As-featured-in.gif

As-featured-in.gif

1209 ms

agape-light.png

agape-light.png

1209 ms

collect

collect

63 ms

b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf

b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf

60 ms

Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf

Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf

60 ms

b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf

b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf

61 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

60 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

61 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

61 ms

g.gif

g.gif

5 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1135 ms

SEO Factors

agapeweddings.co.za SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Agapeweddings.co.za can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Agapeweddings.co.za 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

agapeweddings.co.za

Open Graph description is not detected on the main page of Agapeweddings. 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: