11.9 sec in total
1.8 sec
7.5 sec
2.6 sec
Welcome to zekela.com homepage info - get ready to check Zekela best content right away, or after learning these important things about zekela.com
Visit zekela.comWe analyzed Zekela.com page load time and found that the first response time was 1.8 sec and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
zekela.com performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value26.8 s
0/100
25%
Value10.0 s
9/100
10%
Value290 ms
80/100
30%
Value0.168
71/100
15%
Value9.3 s
31/100
10%
1761 ms
480 ms
749 ms
507 ms
508 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 83% of them (49 requests) were addressed to the original Zekela.com, 7% (4 requests) were made to 0 and 5% (3 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Zekela.com.
Page size can be reduced by 402.5 kB (4%)
9.4 MB
9.0 MB
In fact, the total size of Zekela.com main page is 9.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. 50% of websites need less resources to load. Images take 9.3 MB which makes up the majority of the site volume.
Potential reduce by 37.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. This page needs HTML code to be minified as it can gain 7.8 kB, which is 14% 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 37.8 kB or 69% of the original size.
Potential reduce by 350.4 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. Zekela images are well optimized though.
Potential reduce by 14.3 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 14.3 kB or 11% of the original size.
Number of requests can be reduced by 13 (23%)
56
43
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zekela. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
zekela.com
1761 ms
nvoice.js
480 ms
bootstrap.min.css
749 ms
comm.css
507 ms
index.css
508 ms
jquery-3.6.0.min.js
769 ms
bootstrap.min.js
522 ms
wow.min.js
521 ms
js-sdk-pro.min.js
1144 ms
velocity.js
744 ms
shutter.js
514 ms
Lunbo.js
562 ms
logo1.png
241 ms
%E5%AE%98%E7%BD%91banner1.png
1483 ms
%E5%AE%98%E7%BD%91banner2.png
1733 ms
%E5%AE%98%E7%BD%91banner3.png
4180 ms
about.jpg
1198 ms
yw1.jpg
677 ms
yw2.jpeg
1675 ms
yw3.jpeg
920 ms
yw4.jpeg
1401 ms
bf.png
1438 ms
close.png
1643 ms
rong1.jpg
1918 ms
rong2.jpg
1734 ms
rong3.jpg
2127 ms
rong4.jpg
2639 ms
rong5.jpg
1987 ms
rong6.jpg
1989 ms
rong8.jpg
2400 ms
rong9.jpg
2239 ms
rong10.jpg
2244 ms
rong11.png
2377 ms
rong12.jpg
5206 ms
indx.png
4673 ms
address.png
2617 ms
tell.png
2640 ms
cz.png
2858 ms
yx.png
2879 ms
wb.webp
2882 ms
wx.webp
3100 ms
gongan.png
3119 ms
shutter_prevBtn.png
3100 ms
shutter_nextBtn.png
3318 ms
2000000636.png
3581 ms
zoujin.png
3582 ms
jtl02.png
3558 ms
push.js
712 ms
jtr02.png
3630 ms
xinbg1.png
4089 ms
collect
1260 ms
matomo.js
229 ms
matomo.js
493 ms
hm.js
862 ms
animate.css
3174 ms
matomo.php
874 ms
hm.js
1438 ms
matomo.php
655 ms
hm.gif
335 ms
zekela.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Definition list items are not wrapped in <dl> elements
List items (<li>) are not contained within <ul> or <ol> parent elements.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
zekela.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
zekela.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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zekela.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Zekela.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.
zekela.com
Open Graph description is not detected on the main page of Zekela. 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: