Tools & Wizards About Us
aguiamweddingphotography.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

aguiamweddingphotography.com

Wedding Photography in Portugal - Aguiam Wedding Photographers

Page Load Speed

5.3 sec in total

First Response

388 ms

Resources Loaded

4.4 sec

Page Rendered

427 ms

aguiamweddingphotography.com screenshot

About Website

Welcome to aguiamweddingphotography.com homepage info - get ready to check Aguiam Wedding Photography best content right away, or after learning these important things about aguiamweddingphotography.com

Wedding Photography in Portugal - We aim to eternalize the memories of happiest day of your live. Let us be a part of your story

Visit aguiamweddingphotography.com

Key Findings

We analyzed Aguiamweddingphotography.com page load time and found that the first response time was 388 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

aguiamweddingphotography.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value14.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value36.3 s

0/100

25%

SI (Speed Index)

Value22.9 s

0/100

10%

TBT (Total Blocking Time)

Value1,380 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value30.7 s

0/100

10%

Network Requests Diagram

aguiamweddingphotography.com

388 ms

aguiamweddingphotography.com

1609 ms

style.min.css

594 ms

styles.css

301 ms

cf7-extension-front-style.css

303 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 81% of them (81 requests) were addressed to the original Aguiamweddingphotography.com, 12% (12 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Aguiamweddingphotography.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.6 MB (49%)

Content Size

5.2 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aguiamweddingphotography.com main page is 5.2 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 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 159.6 kB

  • Original 189.5 kB
  • After minification 186.2 kB
  • After compression 29.9 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 159.6 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 12.6 kB

  • Original 1.9 MB
  • After minification 1.8 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. Aguiam Wedding Photography images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 844.6 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 537.0 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 844.6 kB or 61% of the original size.

CSS Optimization

-88%

Potential reduce by 1.5 MB

  • Original 1.8 MB
  • After minification 1.7 MB
  • After compression 218.3 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. Aguiamweddingphotography.com needs all CSS files to be minified and compressed as it can save up to 1.5 MB or 88% of the original size.

Requests Breakdown

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

Requests Now

84

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aguiamweddingphotography.com

aguiamweddingphotography.com

388 ms

aguiamweddingphotography.com

aguiamweddingphotography.com

1609 ms

style.min.css

style.min.css

594 ms

styles.css

styles.css

301 ms

cf7-extension-front-style.css

cf7-extension-front-style.css

303 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

305 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

306 ms

style.css

style.css

395 ms

font-awesome.min.css

font-awesome.min.css

502 ms

stylesheet.min.css

stylesheet.min.css

1003 ms

print.css

print.css

408 ms

style_dynamic_callback.php

style_dynamic_callback.php

1303 ms

responsive.min.css

responsive.min.css

696 ms

style_dynamic_responsive_callback.php

style_dynamic_responsive_callback.php

1131 ms

js_composer.min.css

js_composer.min.css

1035 ms

css

css

30 ms

core-dashboard.min.css

core-dashboard.min.css

694 ms

joinchat-btn.min.css

joinchat-btn.min.css

799 ms

style.css

style.css

801 ms

jquery.lazyloadxt.spinner.css

jquery.lazyloadxt.spinner.css

907 ms

a3_lazy_load.min.css

a3_lazy_load.min.css

905 ms

smartslider.min.css

smartslider.min.css

1048 ms

jquery.min.js

jquery.min.js

959 ms

jquery-migrate.min.js

jquery-migrate.min.js

1014 ms

sbi-scripts.min.js

sbi-scripts.min.js

1019 ms

js

js

73 ms

n2.min.js

n2.min.js

1028 ms

smartslider-frontend.min.js

smartslider-frontend.min.js

1124 ms

ss-simple.min.js

ss-simple.min.js

1117 ms

w-arrow-image.min.js

w-arrow-image.min.js

1122 ms

w-bullet.min.js

w-bullet.min.js

1132 ms

animate.min.css

animate.min.css

1154 ms

css

css

16 ms

sbi-styles.min.css

sbi-styles.min.css

1136 ms

hooks.min.js

hooks.min.js

1139 ms

i18n.min.js

i18n.min.js

1140 ms

index.js

index.js

1141 ms

index.js

index.js

1153 ms

conditional-field.js

conditional-field.js

1154 ms

redirect.js

redirect.js

1153 ms

api.js

api.js

33 ms

frontend.js

frontend.js

1152 ms

doubletaptogo.js

doubletaptogo.js

1146 ms

modernizr.min.js

modernizr.min.js

1287 ms

jquery.appear.js

jquery.appear.js

1282 ms

hoverIntent.min.js

hoverIntent.min.js

1282 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

1193 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

1182 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

1084 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

1085 ms

jquery.waitforimages.js

jquery.waitforimages.js

980 ms

jquery.form.min.js

jquery.form.min.js

980 ms

waypoints.min.js

waypoints.min.js

879 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

880 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

771 ms

jquery.isotope.min.js

jquery.isotope.min.js

882 ms

skrollr.js

skrollr.js

755 ms

TweenLite.min.js

TweenLite.min.js

743 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

743 ms

smoothPageScroll.min.js

smoothPageScroll.min.js

741 ms

default_dynamic_callback.php

default_dynamic_callback.php

1245 ms

default.min.js

default.min.js

785 ms

comment-reply.min.js

comment-reply.min.js

774 ms

js_composer_front.min.js

js_composer_front.min.js

767 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

687 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

680 ms

jquery.fitvids.js

jquery.fitvids.js

778 ms

joinchat.min.js

joinchat.min.js

769 ms

gtm.js

gtm.js

110 ms

gtm.js

gtm.js

255 ms

jquery.lazyloadxt.extra.min.js

jquery.lazyloadxt.extra.min.js

571 ms

jquery.lazyloadxt.srcset.min.js

jquery.lazyloadxt.srcset.min.js

568 ms

jquery.lazyloadxt.extend.js

jquery.lazyloadxt.extend.js

578 ms

wp-polyfill.min.js

wp-polyfill.min.js

668 ms

index.js

index.js

668 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

71 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

72 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

146 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

150 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

152 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

154 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUhiYA.ttf

154 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYA.ttf

155 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYA.ttf

154 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUhiYA.ttf

152 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYA.ttf

155 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYA.ttf

155 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

655 ms

underscore.min.js

underscore.min.js

656 ms

vc-waypoints.min.js

vc-waypoints.min.js

675 ms

vc_grid.min.js

vc_grid.min.js

765 ms

portugal-wedding-photography-v4-2021.png

portugal-wedding-photography-v4-2021.png

764 ms

portugal-wedding-photography-v4-2021-light.png

portugal-wedding-photography-v4-2021-light.png

758 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

624 ms

aguiamweddingphotography-1000-min-1.jpg

aguiamweddingphotography-1000-min-1.jpg

1121 ms

aguiamweddingphotography-10-min-1.jpg

aguiamweddingphotography-10-min-1.jpg

734 ms

lazy_placeholder.gif

lazy_placeholder.gif

724 ms

loading.gif

loading.gif

724 ms

sbi-sprite.png

sbi-sprite.png

733 ms

recaptcha__en.js

recaptcha__en.js

113 ms

Accessibility Review

aguiamweddingphotography.com accessibility score

86

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.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

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

aguiamweddingphotography.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

aguiamweddingphotography.com SEO score

85

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

High

Tap targets are not sized appropriately

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 Aguiamweddingphotography.com 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 Aguiamweddingphotography.com 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

aguiamweddingphotography.com

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