9.9 sec in total
523 ms
8.3 sec
1.1 sec
Visit weddingeye.in now to see the best up-to-date Wedding Eye content for India and also check out these interesting facts you probably never knew about weddingeye.in
Delhi Based Famous Destination Wedding Organisers & Decorators Company Provides all type of Wedding Related Services. We are Top Wedding Planners in Delhi. We have 500+ of decoration and Entertainment...
Visit weddingeye.inWe analyzed Weddingeye.in page load time and found that the first response time was 523 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
weddingeye.in performance score
name
value
score
weighting
Value16.0 s
0/100
10%
Value42.2 s
0/100
25%
Value46.6 s
0/100
10%
Value22,500 ms
0/100
30%
Value0.23
54/100
15%
Value59.7 s
0/100
10%
523 ms
1848 ms
1652 ms
1221 ms
783 ms
Our browser made a total of 167 requests to load all elements on the main page. We found that 49% of them (81 requests) were addressed to the original Weddingeye.in, 17% (28 requests) were made to Google.com and 14% (23 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Weddingeye.in.
Page size can be reduced by 1.6 MB (25%)
6.4 MB
4.8 MB
In fact, the total size of Weddingeye.in main page is 6.4 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. 80% 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 4.3 MB which makes up the majority of the site volume.
Potential reduce by 71.5 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 28.0 kB, which is 35% 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 71.5 kB or 88% of the original size.
Potential reduce by 20.7 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. Wedding Eye images are well optimized though.
Potential reduce by 953.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 953.2 kB or 69% of the original size.
Potential reduce by 553.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. Weddingeye.in needs all CSS files to be minified and compressed as it can save up to 553.6 kB or 85% of the original size.
Number of requests can be reduced by 67 (48%)
140
73
The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wedding Eye. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
weddingeye.in
523 ms
weddingeye.in
1848 ms
bootstrap.css
1652 ms
animate.css
1221 ms
plugin.css
783 ms
owl.carousel.css
787 ms
owl.theme.css
791 ms
owl.transitions.css
794 ms
magnific-popup.css
1040 ms
style.css
1782 ms
demo.css
1049 ms
bg.css
1057 ms
color.css
1285 ms
font-awesome.css
1309 ms
style.css
1574 ms
style.css
1461 ms
settings.css
2045 ms
rev-settings.css
1570 ms
logo.png
1709 ms
wide1.jpg
2846 ms
wide5.jpg
3372 ms
wide6.jpg
3053 ms
wide2.jpg
2680 ms
4.jpg
3267 ms
68.jpg
3066 ms
pic_1.jpg
2933 ms
2.jpg
3100 ms
4.jpg
3178 ms
5.jpg
3284 ms
67.jpg
3827 ms
tf1ithjvgBk
85 ms
team_pic_1.jpg
3122 ms
team_pic_2.jpg
3186 ms
team_pic_3.jpg
3286 ms
team_pic_4.jpg
3283 ms
10.jpg
3376 ms
4.jpg
3649 ms
embed
224 ms
www-embed-player-vflfNyN_r.css
28 ms
www-embed-player.js
52 ms
base.js
72 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
18 ms
ad_status.js
74 ms
js
79 ms
init_embed.js
63 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
62 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
65 ms
js
69 ms
switcher.html
3155 ms
jquery.min.js
3000 ms
jpreLoader.js
3004 ms
bootstrap.min.js
3099 ms
jquery.isotope.min.js
3121 ms
easing.js
2983 ms
jquery.flexslider-min.js
2986 ms
jquery.scrollto.js
3039 ms
owl.carousel.js
3170 ms
yellow.css
2875 ms
jquery.countTo.js
2844 ms
classie.js
2793 ms
css
25 ms
css
36 ms
css
45 ms
video.resize.js
2709 ms
validation.js
2766 ms
map.js
2749 ms
wow.min.js
2702 ms
css
22 ms
css
55 ms
jquery.magnific-popup.min.js
2701 ms
enquire.min.js
2484 ms
designesia.js
2286 ms
demo.js
1955 ms
jquery.themepunch.plugins.min.js
2022 ms
jquery.themepunch.revolution.min.js
1730 ms
3.jpg
2093 ms
2.jpg
2079 ms
5.jpg
2043 ms
jp1.jpg
2236 ms
jp2.jpg
1953 ms
jp3.jpg
2086 ms
j94.jpg
2136 ms
jp6.jpg
2168 ms
jp5.jpg
2411 ms
6.jpg
1977 ms
7.jpg
2073 ms
8.jpg
2306 ms
9.jpg
2076 ms
11.jpg
1996 ms
counter.js
33 ms
t.php
400 ms
font-style-2.css
855 ms
bg-2.jpg
990 ms
bg-3.jpg
871 ms
CcKI4k9un7TZVWzRVT-T88DdSZkkecOE1hvV7ZHvhyU.ttf
30 ms
UAnF6lSK1JNc1tqTiG8pNALUuEpTyoUstqEm5AMlJo4.ttf
31 ms
-_Ctzj9b56b8RgXW8FAricDdSZkkecOE1hvV7ZHvhyU.ttf
31 ms
xkvoNo9fC8O2RDydKj12b8DdSZkkecOE1hvV7ZHvhyU.ttf
31 ms
JbtMzqLaYbbbCL9X6EvaI8DdSZkkecOE1hvV7ZHvhyU.ttf
30 ms
PKCRbVvRfd5n7BTjtGiFZMDdSZkkecOE1hvV7ZHvhyU.ttf
31 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
30 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
31 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
31 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
31 ms
0b3R8ORT0i9mlMGM3BxXF3YhjbSpvc47ee6xR_80Hnw.ttf
95 ms
05xr33FHwecUTIADg28rEXYhjbSpvc47ee6xR_80Hnw.ttf
95 ms
zNeyWiUm5Xx9k2OXf-SMp6CWcynf_cDxXwCLxiixG1c.ttf
95 ms
obisuY-MenYRAFwd-r2NhXYhjbSpvc47ee6xR_80Hnw.ttf
95 ms
URSgP3aplSko3CQAzdXHwHYhjbSpvc47ee6xR_80Hnw.ttf
96 ms
Luunk03-uSz9LnB7oNEUunYhjbSpvc47ee6xR_80Hnw.ttf
95 ms
T4JvHtpMHbjlr73o1YLMo3YhjbSpvc47ee6xR_80Hnw.ttf
95 ms
fontawesome-webfont862f.woff
930 ms
et-line.woff
971 ms
common.js
36 ms
map.js
37 ms
google4.png
113 ms
overlay.js
112 ms
util.js
58 ms
onion.js
57 ms
search_impl.js
59 ms
stats.js
32 ms
openhand_8_8.cur
47 ms
ViewportInfoService.GetViewportInfo
68 ms
ViewportInfoService.GetViewportInfo
30 ms
kh
58 ms
transparent.png
33 ms
controls.js
22 ms
transparent.png
75 ms
css
74 ms
entity11.png
77 ms
vt
140 ms
vt
112 ms
vt
144 ms
vt
147 ms
vt
106 ms
vt
120 ms
vt
167 ms
vt
184 ms
vt
169 ms
vt
180 ms
vt
175 ms
vt
213 ms
vt
233 ms
vt
232 ms
vt
210 ms
vt
241 ms
vt
217 ms
vt
255 ms
vt
271 ms
vt
277 ms
vt
260 ms
vt
292 ms
vt
288 ms
vt
286 ms
vt
345 ms
vt
346 ms
mapcnt6.png
40 ms
tmapctrl.png
34 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
5 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
9 ms
AuthenticationService.Authenticate
14 ms
zhcz-_WihjSQC0oHJ9TCYMDdSZkkecOE1hvV7ZHvhyU.ttf
5 ms
IQHow_FEYlDC4Gzy_m8fcsBaWKZ57bY3RXgXH6dOjZ0.ttf
5 ms
loader.gif
253 ms
timer.png
256 ms
large_left.png
244 ms
large_right.png
250 ms
weddingeye.in accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
weddingeye.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
weddingeye.in SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weddingeye.in 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 Weddingeye.in 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.
weddingeye.in
Open Graph description is not detected on the main page of Wedding Eye. 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: