Tools & Wizards About Us
weddilove.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

weddilove.com

Wedding photographer and planner in Dubrovnik, Croatia. Only stylish photoshoots.

Page Load Speed

9.8 sec in total

First Response

3.1 sec

Resources Loaded

5.6 sec

Page Rendered

1.1 sec

weddilove.com screenshot

About Website

Click here to check amazing Weddilove content. Otherwise, check out these important facts you probably never knew about weddilove.com

Wedding photographer and planner in Dubrovnik, Croatia. A luxurious and unique wedding experience with a personalized approach, where your unique love story is captured beautifully and seamlessly

Visit weddilove.com

Key Findings

We analyzed Weddilove.com page load time and found that the first response time was 3.1 sec and then it took 6.7 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

weddilove.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value430 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.584

11/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

weddilove.com

3134 ms

wp-emoji-release.min.js

225 ms

style.min.css

256 ms

chaty-front.min.css

264 ms

frontend.css

261 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 88% of them (91 requests) were addressed to the original Weddilove.com, 4% (4 requests) were made to Googletagmanager.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Weddilove.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 121.5 kB (2%)

Content Size

5.6 MB

After Optimization

5.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weddilove.com main page is 5.6 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. 65% of websites need less resources to load. Images take 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 67.0 kB

  • Original 83.9 kB
  • After minification 77.9 kB
  • After compression 16.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 67.0 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 37.8 kB

  • Original 5.3 MB
  • After minification 5.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. Weddilove images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 8.1 kB

  • Original 144.3 kB
  • After minification 143.8 kB
  • After compression 136.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. This website has mostly compressed JavaScripts.

CSS Optimization

-13%

Potential reduce by 8.7 kB

  • Original 65.0 kB
  • After minification 64.7 kB
  • After compression 56.4 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. Weddilove.com needs all CSS files to be minified and compressed as it can save up to 8.7 kB or 13% of the original size.

Requests Breakdown

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

Requests Now

98

After Optimization

62

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weddilove.com

weddilove.com

3134 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

225 ms

style.min.css

style.min.css

256 ms

chaty-front.min.css

chaty-front.min.css

264 ms

frontend.css

frontend.css

261 ms

twenty20.css

twenty20.css

259 ms

style-front-end.min.css

style-front-end.min.css

257 ms

style-front-end-form.min.css

style-front-end-form.min.css

350 ms

styles.css

styles.css

381 ms

media.css

media.css

388 ms

bootstrap.css

bootstrap.css

519 ms

norma.css

norma.css

389 ms

main.css

main.css

389 ms

style.css

style.css

477 ms

sm-blue.css

sm-blue.css

507 ms

stylesheet.css

stylesheet.css

516 ms

jquery.js

jquery.js

644 ms

jquery-migrate.min.js

jquery-migrate.min.js

530 ms

ajaxupload.js

ajaxupload.js

603 ms

bootstrap.min.js

bootstrap.min.js

634 ms

jquery.smartmenus.js

jquery.smartmenus.js

665 ms

jquery-migrate.min.js

jquery-migrate.min.js

536 ms

jquery-1.12.4.js

jquery-1.12.4.js

49 ms

js

js

72 ms

js

js

119 ms

cht-front-script.min.js

cht-front-script.min.js

801 ms

core.min.js

core.min.js

766 ms

datepicker.min.js

datepicker.min.js

766 ms

frontend.js

frontend.js

799 ms

jquery.twenty20.js

jquery.twenty20.js

799 ms

jquery.event.move.js

jquery.event.move.js

799 ms

script-front-end.min.js

script-front-end.min.js

775 ms

wp-embed.min.js

wp-embed.min.js

820 ms

ico_menu.js

ico_menu.js

821 ms

naverx.js

naverx.js

822 ms

css

css

36 ms

ru.png

ru.png

262 ms

gb.png

gb.png

263 ms

insta.png

insta.png

301 ms

lenta.png

lenta.png

450 ms

fas.png

fas.png

332 ms

vk.png

vk.png

333 ms

Logo_Event.png

Logo_Event.png

588 ms

kvadrat-700x700.jpg

kvadrat-700x700.jpg

415 ms

mi_dubrovnik-236--700x700.jpg

mi_dubrovnik-236--700x700.jpg

808 ms

ml_dubrovnik-102-web-1-700x700.jpg

ml_dubrovnik-102-web-1-700x700.jpg

808 ms

dsc_4252-15-700x700.jpg

dsc_4252-15-700x700.jpg

808 ms

ak_dubrovnik-127-700x700.jpg

ak_dubrovnik-127-700x700.jpg

804 ms

pc_dubrovnik-119-700x700.jpg

pc_dubrovnik-119-700x700.jpg

804 ms

ve-paris-29-700x700.jpg

ve-paris-29-700x700.jpg

673 ms

uj_kapadokya-45-700x700.jpg

uj_kapadokya-45-700x700.jpg

929 ms

rh_wedday_dubrovnik-302-700x700.jpg

rh_wedday_dubrovnik-302-700x700.jpg

1193 ms

rh_wedday_dubrovnik-710-700x700.jpg

rh_wedday_dubrovnik-710-700x700.jpg

1061 ms

ag_amsterdam-53-700x700.jpg

ag_amsterdam-53-700x700.jpg

1065 ms

pt_dubrovnik-71--700x700.jpg

pt_dubrovnik-71--700x700.jpg

1068 ms

re_cappadocia-4-700x700.jpg

re_cappadocia-4-700x700.jpg

1068 ms

2_wed_day_ka-84-700x700.jpg

2_wed_day_ka-84-700x700.jpg

1067 ms

ae_london-74-1-700x700.jpg

ae_london-74-1-700x700.jpg

1319 ms

fn_copenhagen-40--700x700.jpg

fn_copenhagen-40--700x700.jpg

1204 ms

img_0831-21-700x700.jpg

img_0831-21-700x700.jpg

1207 ms

dsc_5299-700x700.jpg

dsc_5299-700x700.jpg

1328 ms

france_aa-30-700x700.jpg

france_aa-30-700x700.jpg

1384 ms

tanianaolivier_paris-47-700x700.jpg

tanianaolivier_paris-47-700x700.jpg

1385 ms

js

js

55 ms

analytics.js

analytics.js

129 ms

js

js

83 ms

montserrat-regular-webfont.woff

montserrat-regular-webfont.woff

355 ms

cassandra-webfont.woff

cassandra-webfont.woff

445 ms

nothingyoucoulddo-webfont.woff

nothingyoucoulddo-webfont.woff

488 ms

nimbusromno9l-medita-webfont.woff

nimbusromno9l-medita-webfont.woff

470 ms

dubrovnik_ir-45_1-2-700x700.jpg

dubrovnik_ir-45_1-2-700x700.jpg

1216 ms

vm_lovestory_paris-51_-700x700.jpg

vm_lovestory_paris-51_-700x700.jpg

1172 ms

av_bosnia-61-700x700.jpg

av_bosnia-61-700x700.jpg

1246 ms

budva_sm_35-700x700.jpg

budva_sm_35-700x700.jpg

1327 ms

dsc_6176-700x700.jpg

dsc_6176-700x700.jpg

1212 ms

wed_day_rg-110-700x700.jpg

wed_day_rg-110-700x700.jpg

1215 ms

collect

collect

36 ms

collect

collect

57 ms

copperplate_gothic_light_regular-webfont.woff

copperplate_gothic_light_regular-webfont.woff

291 ms

wed_pa-136-1-700x700.jpg

wed_pa-136-1-700x700.jpg

1301 ms

collect

collect

47 ms

barcelona-es-117--700x700.jpg

barcelona-es-117--700x700.jpg

1269 ms

wed_day-86-1-700x700.jpg

wed_day-86-1-700x700.jpg

1266 ms

collect

collect

35 ms

ga-audiences

ga-audiences

89 ms

ga-audiences

ga-audiences

105 ms

ia_lovestory-7-700x700.jpg

ia_lovestory-7-700x700.jpg

1185 ms

natalya_pavel_du-9-700x700.jpg

natalya_pavel_du-9-700x700.jpg

1157 ms

dsc_6753-700x700.jpg

dsc_6753-700x700.jpg

1253 ms

love_story-bk-39-700x700.jpg

love_story-bk-39-700x700.jpg

1185 ms

dsc_9224-700x700.jpg

dsc_9224-700x700.jpg

1163 ms

wedday-127-700x700.jpg

wedday-127-700x700.jpg

1152 ms

love-story-49-700x700.jpg

love-story-49-700x700.jpg

1148 ms

dubrovnik-2016-93-700x700.jpg

dubrovnik-2016-93-700x700.jpg

1140 ms

aa_love_story-46-700x700.jpg

aa_love_story-46-700x700.jpg

1176 ms

dsc6980-700x700.jpg

dsc6980-700x700.jpg

1067 ms

dsc_5745-700x700.jpg

dsc_5745-700x700.jpg

1067 ms

insta.png

insta.png

134 ms

insta_link2.png

insta_link2.png

130 ms

face.png

face.png

132 ms

m5.png

m5.png

129 ms

k.png

k.png

131 ms

m2.png

m2.png

130 ms

cd-top-arrow.svg

cd-top-arrow.svg

129 ms

Accessibility Review

weddilove.com accessibility score

90

Accessibility Issues

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

Image elements do not have [alt] attributes

Best Practices

weddilove.com best practices score

58

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

Page has valid source maps

SEO Factors

weddilove.com SEO score

76

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 doesn't use 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 Weddilove.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 Weddilove.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

weddilove.com

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