5.9 sec in total
405 ms
4.6 sec
876 ms
Welcome to fancypoint.lk homepage info - get ready to check Fancypoint best content right away, or after learning these important things about fancypoint.lk
One stop cosmetics & accessories store. Islandwide delivery available, purchase from your trusted cosmetics partner
Visit fancypoint.lkWe analyzed Fancypoint.lk page load time and found that the first response time was 405 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fancypoint.lk performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value7.7 s
3/100
25%
Value5.7 s
51/100
10%
Value2,360 ms
5/100
30%
Value0.01
100/100
15%
Value19.2 s
2/100
10%
405 ms
723 ms
330 ms
267 ms
278 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 40% of them (49 requests) were addressed to the original Fancypoint.lk, 34% (42 requests) were made to Backoffice.fancypoint.lk and 14% (17 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Backoffice.fancypoint.lk.
Page size can be reduced by 953.2 kB (18%)
5.3 MB
4.4 MB
In fact, the total size of Fancypoint.lk main page is 5.3 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. Only a small number of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 228.3 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 90.3 kB, which is 37% 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 228.3 kB or 94% of the original size.
Potential reduce by 391.6 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. Fancypoint images are well optimized though.
Potential reduce by 7.8 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.
Potential reduce by 325.5 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. Fancypoint.lk needs all CSS files to be minified and compressed as it can save up to 325.5 kB or 70% of the original size.
Number of requests can be reduced by 41 (40%)
102
61
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fancypoint. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
fancypoint.lk
405 ms
www.fancypoint.lk
723 ms
bootstrap.min.css
330 ms
slick.css
267 ms
swiper.min.css
278 ms
magnific-popup.css
268 ms
nouislider.css
275 ms
darktooltip.css
316 ms
animate.css
541 ms
toastr.min.css
33 ms
style.css
517 ms
megamenu.css
539 ms
bootstrap-select.min.css
540 ms
jquery-3.3.1.min.js
647 ms
floating-wpp.min.css
649 ms
floating-wpp.min.js
855 ms
font-awesome.min.css
51 ms
style.css
773 ms
css
40 ms
email-decode.min.js
542 ms
jquery.js
1012 ms
bootstrap.min.js
843 ms
swiper.min.js
1020 ms
slick.min.js
1017 ms
parallax.js
1017 ms
isotope.pkgd.min.js
1252 ms
jquery.magnific-popup.js
1173 ms
jquery.countdown.min.js
1173 ms
nouislider.min.js
1282 ms
jquery.ez-plus.js
1282 ms
tocca.min.js
1281 ms
bootstrap-tabcollapse.js
1609 ms
jquery-scrollLock.min.js
1283 ms
jquery.darktooltip.js
1611 ms
imagesloaded.pkgd.min.js
1630 ms
instafeed.min.js
1608 ms
megamenu.min.js
1628 ms
app.js
1629 ms
toastr.min.js
38 ms
waitMe.js
1630 ms
validator.js
1641 ms
bootstrap-select.min.js
1799 ms
dd52e085fbe33d6569ce7a46ea2725ab-org.jpg
298 ms
bRsHG5WVxTs
297 ms
7e9a02d4681b3b434a24a19f59aa7042-std.jpg
702 ms
12d8724f0a36dc14feb060daee3cf8d5-std.jpg
705 ms
755b9181d94b3ed14cc0dd42497d34fe-std.jpg
700 ms
69397f91702b36a4e361e1e057913ab3-std.jpg
377 ms
780b24a45bab13cee54742238fd436c9-std.jpg
703 ms
c276fa1a45dd4f490a9ba9bba71459fc-std.jpg
706 ms
aa266c2e89ea74a6d4f62224c496e9e8-std.jpg
726 ms
f94895678350e2220d5aa1918fa0f81b-std.jpg
767 ms
581577a3f74c1613c2d489110c6d141a-std.jpg
770 ms
69e3c2c59df2fb1c689dfc4ee821bfbe-std.jpg
723 ms
604ff46ea67ca563c1140d75a1c77d0e-std.jpg
990 ms
cb91b0b8e4df7fdf3837ff0f4538c279-std.jpg
898 ms
b485b66d0fe0889d02468d60aa406225-std.jpg
991 ms
6c9a2098b38023ed4fa7332fb2cd00f3-std.jpg
1280 ms
91c6ff2c546059c8c7db853355b5c0b3-std.jpg
1281 ms
f91d3ed4df89ac8ccc66d0a27bde1917-std.jpg
1278 ms
bbb74b406d1d151aa7c5859837388506-std.jpg
1282 ms
019490ad8ec8b17eb8e1a836f166ad2c-std.jpg
1282 ms
00137ed5d5226311548eb021ef36ba2a-std.jpg
1314 ms
a866116637661c2c1a1bc355597a82cf-std.jpg
1316 ms
01fcb53831d62fbdd6881782fdbe890a-std.jpg
1395 ms
3b3dbd4dff7076d91088cabae4c52bff-std.jpg
1476 ms
1df83b7809f48aa67ddddefa404b1fb0-std.jpg
1476 ms
a7f2c9419b2024c7c61d7ec6bad6019d-std.jpg
1477 ms
1432621b65244e88144f3c44d163acae-std.jpg
1510 ms
4f3e3973e76703aadcfac35c97d923ce-std.jpg
1499 ms
b83084a353a5ab67397fc66da956b6d3-std.jpg
1671 ms
deef2e7bc2a6c477ca449f6cd780cad1-std.jpg
1737 ms
6d4b81a34bd728f4e71d588d440f45de-std.jpg
1686 ms
1d21e5a1ae0e5976afbe87d2b7b247b9-std.jpg
1837 ms
363e784359b00a55d75c898cbfbef82a-org.jpg
1645 ms
58086369d121e32dbc6ce6875567b230-org.jpg
1681 ms
e124af086d05fa37c22d1741870bdac6-org.jpg
1880 ms
eee2ff610a567ef1a899946f873a8f00-org.jpg
2225 ms
668c3ae89057d2b78360439925b52b12-org.jpg
2009 ms
fancypoint1.gif
735 ms
loader.gif
988 ms
insta.jpg
1276 ms
offerImage.jpg
1277 ms
logoBottom.png
766 ms
bottom-image.jpg
760 ms
icon-pay-1.png
1275 ms
icon-pay-2.png
1261 ms
icon-pay-3.png
1277 ms
icon-pay-4.png
1280 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
56 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
126 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
161 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
163 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
161 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf
164 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf
164 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
162 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf
164 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf
167 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
165 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
165 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
165 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf
166 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf
166 ms
icomoon-reg.ttf
1286 ms
fontawesome-webfont.woff
25 ms
www-player.css
86 ms
www-embed-player.js
116 ms
base.js
145 ms
b39b12bf96d7a8e215ce1af76304f2eb-org.jpg
1673 ms
b53a2866a5fa9b13934027626c4bf672-org.jpg
1528 ms
ad_status.js
177 ms
6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js
136 ms
embed.js
48 ms
dccec8475fb5ae9f40b7d20f329e96b1-org.jpg
1453 ms
e41b1fef83140a5ece5ef9ef106179a8-org.jpg
1506 ms
0239b70d695af4b28f6abe2e85a9ca96-org.jpg
1607 ms
30feefeac93597c09833735c6349a806-org.jpg
1876 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
28 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
28 ms
id
27 ms
Create
119 ms
GenerateIT
130 ms
fancypoint.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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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.
fancypoint.lk 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
fancypoint.lk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Fancypoint.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 Fancypoint.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.
fancypoint.lk
Open Graph description is not detected on the main page of Fancypoint. 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: