4.7 sec in total
1 sec
2.8 sec
809 ms
Visit prestigeproperty.lk now to see the best up-to-date Prestige Property content and also check out these interesting facts you probably never knew about prestigeproperty.lk
Visit prestigeproperty.lkWe analyzed Prestigeproperty.lk page load time and found that the first response time was 1 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
prestigeproperty.lk performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value21.3 s
0/100
25%
Value14.3 s
1/100
10%
Value6,010 ms
0/100
30%
Value0
100/100
15%
Value34.6 s
0/100
10%
1044 ms
191 ms
125 ms
137 ms
141 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 77% of them (63 requests) were addressed to the original Prestigeproperty.lk, 20% (16 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Prestigeproperty.lk.
Page size can be reduced by 520.1 kB (16%)
3.2 MB
2.7 MB
In fact, the total size of Prestigeproperty.lk main page is 3.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. 70% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 201.2 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 201.2 kB or 86% of the original size.
Potential reduce by 14.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. Prestige Property images are well optimized though.
Potential reduce by 128.9 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 128.9 kB or 34% of the original size.
Potential reduce by 175.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. Prestigeproperty.lk needs all CSS files to be minified and compressed as it can save up to 175.8 kB or 47% of the original size.
Number of requests can be reduced by 57 (89%)
64
7
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prestige Property. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
prestigeproperty.lk
1044 ms
bdt-uikit.css
191 ms
prime-slider-site.css
125 ms
extendify-utilities.css
137 ms
style.css
141 ms
all-css.css
374 ms
all.min.css
174 ms
style.css
186 ms
frontend.min.css
203 ms
swiper.min.css
207 ms
e-swiper.min.css
235 ms
post-14.css
244 ms
frontend.min.css
319 ms
zoomInRight.min.css
265 ms
bounceInUp.min.css
269 ms
slideInLeft.min.css
297 ms
widget-heading.min.css
304 ms
widget-text-editor.min.css
337 ms
widget-image.min.css
336 ms
slideInRight.min.css
359 ms
prime-slider-font.css
400 ms
ps-tango.css
402 ms
widget-icon-box.min.css
403 ms
slideInUp.min.css
402 ms
widget-video.min.css
418 ms
post-24.css
436 ms
post-16.css
437 ms
post-51.css
447 ms
general.min.css
482 ms
css
44 ms
jquery.min.js
538 ms
jquery-migrate.min.js
497 ms
css
21 ms
slideInDown.min.css
399 ms
widget-icon-list.min.css
404 ms
all-scripts.js
589 ms
houzez-instant-page.js
477 ms
core.min.js
476 ms
menu.min.js
479 ms
dom-ready.min.js
461 ms
hooks.min.js
635 ms
i18n.min.js
632 ms
a11y.min.js
598 ms
autocomplete.min.js
589 ms
mouse.min.js
581 ms
slider.min.js
567 ms
custom.min.js
566 ms
bdt-uikit.min.js
541 ms
webpack.runtime.min.js
530 ms
frontend-modules.min.js
512 ms
frontend.min.js
505 ms
ps-tango.min.js
477 ms
imagesloaded.min.js
471 ms
general.min.js
439 ms
jquery.smartmenus.min.js
445 ms
prime-slider-site.min.js
446 ms
webpack-pro.runtime.min.js
993 ms
frontend.min.js
952 ms
elements-handlers.min.js
950 ms
css2
28 ms
Component-1-1-1.png
829 ms
Component-2.png
828 ms
Line-1-2.png
828 ms
Untitled-design-2-min-1.png
1199 ms
lazyloader-1.gif
733 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo18E.ttf
688 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo58a-xw.ttf
691 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o18E.ttf
693 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xw.ttf
691 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o18E.ttf
691 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o58a-xw.ttf
691 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkCEv18E.ttf
691 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkCEv58a-xw.ttf
693 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv18E.ttf
694 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58a-xw.ttf
692 ms
houzez-iconfont.ttf
643 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
693 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
694 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
694 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
694 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
695 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
694 ms
prestigeproperty.lk accessibility score
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
[aria-*] attributes do not match their roles
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
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
prestigeproperty.lk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
prestigeproperty.lk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prestigeproperty.lk 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 Prestigeproperty.lk 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.
prestigeproperty.lk
Open Graph description is not detected on the main page of Prestige Property. 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: