6.3 sec in total
1.9 sec
3.8 sec
607 ms
Welcome to wecng.com homepage info - get ready to check We Cn G best content right away, or after learning these important things about wecng.com
Visit wecng.comWe analyzed Wecng.com page load time and found that the first response time was 1.9 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster. This domain responded with an error, which can significantly jeopardize Wecng.com rating and web reputation
wecng.com performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value20.6 s
0/100
25%
Value6.0 s
47/100
10%
Value100 ms
98/100
30%
Value0.185
66/100
15%
Value15.8 s
6/100
10%
1874 ms
26 ms
24 ms
57 ms
63 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 59% of them (60 requests) were addressed to the original Wecng.com, 28% (28 requests) were made to Fonts.gstatic.com and 8% (8 requests) were made to Businessdummy.wpengine.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Wecng.com.
Page size can be reduced by 1.7 MB (80%)
2.1 MB
427.3 kB
In fact, the total size of Wecng.com main page is 2.1 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. 85% 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. CSS take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 108.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 108.8 kB or 83% of the original size.
Potential reduce by 3.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. Obviously, We Cn G needs image optimization as it can save up to 3.4 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 596.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 596.9 kB or 71% of the original size.
Potential reduce by 1.0 MB
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. Wecng.com needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 87% of the original size.
Number of requests can be reduced by 51 (93%)
55
4
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of We Cn G. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
www.wecng.com
1874 ms
html5.js
26 ms
css3-mediaqueries.js
24 ms
dashicons.min.css
57 ms
jquery-ui-dialog.min.css
63 ms
layerslider.css
21 ms
css
53 ms
styles.css
71 ms
settings.css
57 ms
style.css
73 ms
style_end.css
132 ms
css
68 ms
media-queries_wide.css
61 ms
rgs.css
69 ms
animations.css
107 ms
flexslider.css
112 ms
font-awesome.css
101 ms
moon.css
206 ms
elegant.css
126 ms
prettyPhoto.css
113 ms
thefox_js_composer.css
178 ms
zilla-likes.css
173 ms
jquery.js
202 ms
jquery-migrate.min.js
174 ms
greensock.js
175 ms
layerslider.kreaturamedia.jquery.js
199 ms
layerslider.transitions.js
199 ms
jquery.themepunch.tools.min.js
202 ms
jquery.themepunch.revolution.min.js
200 ms
wp-emoji-release.min.js
220 ms
css
150 ms
icon-styles.css
147 ms
css
151 ms
css
153 ms
core.min.js
151 ms
widget.min.js
144 ms
mouse.min.js
143 ms
resizable.min.js
144 ms
draggable.min.js
147 ms
button.min.js
147 ms
position.min.js
147 ms
dialog.min.js
146 ms
wpdialog.min.js
148 ms
customjs.js
155 ms
custom_woo_js.js
149 ms
smoothscroll.js
149 ms
jquery.form.min.js
149 ms
scripts.js
150 ms
wp-embed.min.js
149 ms
js_composer_front.js
152 ms
script-ck.js
151 ms
jquery.isotope.min.js
150 ms
sorting_bp.js
150 ms
refresh_bp.js
149 ms
w_n_e.png
60 ms
s_box.jpg
53 ms
bg2.jpg
47 ms
twitter.jpg
21 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
21 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
127 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
127 ms
BTu4SsVveqk58cdYjlaM9g.ttf
126 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
124 ms
vDvcuXwZxUMLuTfuLrSLpA.ttf
124 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
126 ms
zpv3sOKAbMf4wff105oLjw.ttf
128 ms
4cKlrioa77J2iqTqBgkRWg.ttf
129 ms
5pEc4QKTMA2oB4Hi9NkS4w.ttf
127 ms
fontawesome-webfont.woff
126 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
127 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
128 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
127 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
128 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
126 ms
ion.woff
123 ms
en.woff
119 ms
ty2.woff
122 ms
draw.woff
127 ms
imf.woff
129 ms
moon.woff
127 ms
zm.woff
125 ms
contact_bg.jpg
71 ms
ElegantIcons.woff
79 ms
1ImRNPx4870-D9a1EBUdPC3USBnSvpkopQaUR-2r7iU.ttf
22 ms
PKCRbVvRfd5n7BTjtGiFZC3USBnSvpkopQaUR-2r7iU.ttf
25 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
22 ms
xkvoNo9fC8O2RDydKj12by3USBnSvpkopQaUR-2r7iU.ttf
24 ms
CcKI4k9un7TZVWzRVT-T8y3USBnSvpkopQaUR-2r7iU.ttf
21 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
23 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
24 ms
8KhZd3VQBtXTAznvKjw-ky3USBnSvpkopQaUR-2r7iU.ttf
23 ms
RJMlAoFXXQEzZoMSUteGWKCWcynf_cDxXwCLxiixG1c.ttf
24 ms
2NBgzUtEeyB-Xtpr9bm1Cczai8e7xzqnKiVb1EwOy0E.ttf
23 ms
UC3ZEjagJi85gF9qFaBgIETamuWRjOQSPxoOXgdYd7c.ttf
25 ms
UC3ZEjagJi85gF9qFaBgIA0DQt4XpTxu2mZR8niJHm4.ttf
24 ms
s_box.jpg
117 ms
ajax-loader.gif
23 ms
bg2.jpg
28 ms
twitter.jpg
29 ms
contact_bg.jpg
30 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
9 ms
wecng.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
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.
wecng.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
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
wecng.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wecng.com 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 Wecng.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.
wecng.com
Open Graph description is not detected on the main page of We Cn G. 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: