27.2 sec in total
1.8 sec
24.5 sec
886 ms
Welcome to leeshingchak.com homepage info - get ready to check Leeshingchak best content right away, or after learning these important things about leeshingchak.com
李丞責中華風水文化
Visit leeshingchak.comWe analyzed Leeshingchak.com page load time and found that the first response time was 1.8 sec and then it took 25.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
leeshingchak.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value20.1 s
0/100
25%
Value12.8 s
2/100
10%
Value1,090 ms
24/100
30%
Value0.386
27/100
15%
Value18.4 s
3/100
10%
1841 ms
657 ms
443 ms
291 ms
630 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 96% of them (109 requests) were addressed to the original Leeshingchak.com, 2% (2 requests) were made to Fonts.googleapis.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (10.9 sec) belongs to the original domain Leeshingchak.com.
Page size can be reduced by 440.8 kB (9%)
4.7 MB
4.2 MB
In fact, the total size of Leeshingchak.com main page is 4.7 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 4.2 MB which makes up the majority of the site volume.
Potential reduce by 96.8 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 96.8 kB or 87% of the original size.
Potential reduce by 205.0 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. Leeshingchak images are well optimized though.
Potential reduce by 57.5 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 57.5 kB or 28% of the original size.
Potential reduce by 81.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. Leeshingchak.com needs all CSS files to be minified and compressed as it can save up to 81.5 kB or 61% of the original size.
Number of requests can be reduced by 35 (32%)
110
75
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Leeshingchak. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
leeshingchak.com
1841 ms
jquery-2.1.1.min.js
657 ms
jquery-ui.min.js
443 ms
jquery-ui.min.css
291 ms
owl.carousel.min.js
630 ms
owl.carousel.min.css
259 ms
owl.theme.green.min.css
232 ms
bootstrap.min.css
245 ms
bootstrap.min.js
254 ms
jquery.plugin.min.js
493 ms
jquery.countdown.min.js
2120 ms
jquery.countdown.css
540 ms
menu.js
732 ms
menu.css
507 ms
icon-font.min.css
520 ms
animate.css
1699 ms
layoutproducts.css
3579 ms
ocsearchcategory.css
1204 ms
font-awesome.min.css
692 ms
css
33 ms
css
45 ms
stylesheet.css
3089 ms
slick.css
978 ms
slick.min.js
1914 ms
ocslideshow.css
1767 ms
flexslider.css
2641 ms
ocpagebuilder.css
3894 ms
photoswipe.min.css
2382 ms
default-skin.min.css
4830 ms
jquery.nivo.slider.js
2677 ms
jquery.flexslider.js
3329 ms
common.js
6645 ms
js
55 ms
gallery.css
3101 ms
gallery.js
4135 ms
email-decode.min.js
3330 ms
fbevents.js
95 ms
bg.jpg
669 ms
logo.png
429 ms
fb-20x20.png
276 ms
IG-20x20.png
516 ms
weibo-20x20.png
549 ms
AjaxLoader.gif
2087 ms
en-gb.png
513 ms
zh-HK.png
961 ms
zh-cn.png
1040 ms
slideshow1-2-1920x896.jpg
944 ms
slideshow1-1-1920x896.jpg
2802 ms
slideshow1-3-1920x896.jpg
931 ms
img_lee.png
1492 ms
Screenshot_20231026_105536_Adobe%20Acrobat-350x350.jpg
3122 ms
2023-rabbit-sq-350x350.jpg
1635 ms
2023-boxset-sq-350x350.jpg
1349 ms
New2-sq-350x350.jpg
3306 ms
2022-boxset-350x350.jpg
1868 ms
2022-tiger-sq-350x350.jpg
2712 ms
news8-sq-350x350.jpg
4463 ms
news7-sq-350x350.jpg
2866 ms
news6-sq-350x350.jpg
5928 ms
news5-sq-350x350.jpg
3464 ms
banner3-1.jpg
3146 ms
banner3-2.jpg
8419 ms
banner3-3.jpg
3665 ms
banner1-1.jpg
4615 ms
banner1-2.jpg
4155 ms
banner1-3.jpg
4272 ms
banner1-4.jpg
7239 ms
banner1-5.jpg
4915 ms
3337248785f84167004a86-500x500.jpg
4790 ms
placeholder-500x500.png
5218 ms
74887707155474807d406d-500x500.JPG
5362 ms
20872182805f84220471c9c-500x500.jpg
5237 ms
19731590745f84174bc3c75-500x500.jpg
7384 ms
fontawesome-webfont.woff
6267 ms
Linearicons-Free.woff
7051 ms
14413841825beba1b60daf5-500x500.jpg
7574 ms
692935453603c81471a610-500x500.jpg
7106 ms
banner9-1.jpg
7612 ms
banner9-2.jpg
9656 ms
2022.jpg
7518 ms
2021.jpg
7007 ms
2020.jpg
7533 ms
2019.jpg
7309 ms
2018.jpg
7309 ms
BOOKA_COVER_S.jpg
9243 ms
2015.jpg
6853 ms
b12.jpg
6959 ms
b11.jpg
7088 ms
img1.png
7732 ms
img2.png
6274 ms
img3.png
8117 ms
b7.jpg
10856 ms
img4.png
7676 ms
b10.jpg
7650 ms
b3.jpg
7403 ms
b9.jpg
9320 ms
img5.png
7420 ms
img6.png
6877 ms
b8.jpg
9099 ms
b6.jpg
6998 ms
img7.png
7054 ms
img8.png
7184 ms
img9.png
7200 ms
b5.jpg
7140 ms
img10.png
6725 ms
main.js
6510 ms
b4.jpg
6208 ms
img11.png
5906 ms
b1.jpg
5547 ms
img12.png
5881 ms
b2.jpg
8006 ms
bg_btn_prev.png
535 ms
bg_btn_next.png
514 ms
leeshingchak.com 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
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
leeshingchak.com 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
Page has valid source maps
leeshingchak.com 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
JA
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leeshingchak.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Leeshingchak.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.
leeshingchak.com
Open Graph description is not detected on the main page of Leeshingchak. 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: