7 sec in total
185 ms
6.7 sec
104 ms
Welcome to 4epohes.com homepage info - get ready to check 4 Epohes best content right away, or after learning these important things about 4epohes.com
✅js1996官网✅持在线合法执照,信誉保证,请您放心...
Visit 4epohes.comWe analyzed 4epohes.com page load time and found that the first response time was 185 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
4epohes.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value12.5 s
0/100
25%
Value10.8 s
6/100
10%
Value130 ms
96/100
30%
Value0.001
100/100
15%
Value13.4 s
11/100
10%
185 ms
223 ms
74 ms
181 ms
201 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 32% of them (24 requests) were addressed to the original 4epohes.com, 43% (32 requests) were made to Syqqbl.com and 15% (11 requests) were made to Test.xinxiyidiantong.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Syqqbl.com.
Page size can be reduced by 37.3 kB (1%)
2.8 MB
2.8 MB
In fact, the total size of 4epohes.com main page is 2.8 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. 40% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 3.6 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 3.6 kB or 72% of the original size.
Potential reduce by 23.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. 4 Epohes images are well optimized though.
Potential reduce by 1.0 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 9.2 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. 4epohes.com needs all CSS files to be minified and compressed as it can save up to 9.2 kB or 84% of the original size.
Number of requests can be reduced by 23 (33%)
69
46
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 4 Epohes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
4epohes.com
185 ms
www.4epohes.com
223 ms
jquery.min.js
74 ms
reset.css
181 ms
webmain.css
201 ms
ddsmoothmenu.css
200 ms
style.css
182 ms
jquery-1.4.2.min.js
274 ms
cookie.js
199 ms
jquery.KinSlideshow-1.2.1.js
299 ms
webtry_roll.js
300 ms
ddsmoothmenu.js
301 ms
jquery-1.8.0.min.js
375 ms
jquery.jslides.js
299 ms
index.js
378 ms
aos.css
414 ms
jquery.min.js
490 ms
responsiveslides.min.js
415 ms
slide.js
416 ms
count.js
472 ms
jump.js
475 ms
aos.js
509 ms
sj.js
1820 ms
fcl.php
936 ms
mivisit.js
344 ms
getOnline.html
526 ms
push.js
1240 ms
1.jpg
2501 ms
logo.jpg
1168 ms
about-img.jpg
1593 ms
2.jpg
2707 ms
3.jpg
2289 ms
4.jpg
2943 ms
5e13fa597c576.jpg
1522 ms
5e13fcda97269.jpg
2171 ms
cp-nav1.png
1735 ms
cp-nav1a.png
1956 ms
5e13fc0b5cf6c.jpg
2852 ms
5e13fa19612a9.jpg
2393 ms
cp-nav2.png
2329 ms
cp-nav2a.png
2504 ms
cp-nav3a.png
2525 ms
cp-nav3.png
2534 ms
cp-nav4.png
2718 ms
cp-nav4a.png
2719 ms
ys-img1.png
2661 ms
ys-img2.png
2658 ms
xw-img.jpg
2860 ms
ys-img3.png
2843 ms
zj-jt.png
2849 ms
banquan.png
2853 ms
footer-icon1.jpg
2796 ms
footer-icon2.jpg
2785 ms
footer-icon4.jpg
2972 ms
footer-icon3.jpg
2975 ms
cp-bg.jpg
3225 ms
ys-bg.jpg
2997 ms
zj-bg.jpg
2938 ms
themes.gif
2904 ms
style1.css
976 ms
jquery.la.min.js
74 ms
js-sdk-pro.min.js
76 ms
tj.js
308 ms
collect
624 ms
collect
612 ms
2.jpg
1408 ms
logo.png
1490 ms
28_1.jpg
1011 ms
3_1.jpg
949 ms
9_1.jpg
877 ms
1_1.jpg
1156 ms
5_1.jpg
1167 ms
2_1.jpg
1228 ms
4_1.jpg
1330 ms
19_1.jpg
2164 ms
4epohes.com accessibility score
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
4epohes.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
4epohes.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 4epohes.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 4epohes.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.
4epohes.com
Open Graph description is not detected on the main page of 4 Epohes. 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: