14.6 sec in total
5.6 sec
8.7 sec
267 ms
Welcome to jseq.com homepage info - get ready to check Jseq best content right away, or after learning these important things about jseq.com
江苏省地震工程研究院
Visit jseq.comWe analyzed Jseq.com page load time and found that the first response time was 5.6 sec and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
jseq.com performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value1.5 s
100/100
25%
Value5.0 s
64/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.4 s
100/100
10%
5629 ms
497 ms
940 ms
291 ms
781 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that all of those requests were addressed to Jseq.com and no external sources were called. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Jseq.com.
Page size can be reduced by 89.9 kB (88%)
101.7 kB
11.8 kB
In fact, the total size of Jseq.com main page is 101.7 kB. 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 5% of websites need less resources to load. HTML takes 91.8 kB which makes up the majority of the site volume.
Potential reduce by 82.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 17.8 kB, which is 19% 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 82.3 kB or 90% of the original size.
Potential reduce by 0 B
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. Jseq images are well optimized though.
Potential reduce by 6.7 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 6.7 kB or 81% of the original size.
Potential reduce by 788 B
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. Jseq.com needs all CSS files to be minified and compressed as it can save up to 788 B or 66% of the original size.
Number of requests can be reduced by 28 (45%)
62
34
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jseq. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
jseq.com
5629 ms
link.css
497 ms
AC_RunActiveContent.js
940 ms
bg.gif
291 ms
logo.gif
781 ms
t_d2.gif
915 ms
l.gif
626 ms
r_tu.gif
965 ms
r1.gif
731 ms
or.gif
860 ms
r2.gif
894 ms
r3.gif
993 ms
rd.gif
1012 ms
link.gif
1118 ms
link_1.gif
1204 ms
link_2.gif
1247 ms
link_3.gif
1296 ms
link_4.gif
1354 ms
link_5.gif
1376 ms
link_6.gif
1437 ms
tbg2.gif
1497 ms
dhl_bg.gif
1467 ms
w8_1.gif
1511 ms
r_bg.gif
1551 ms
link_bg.jpg
1562 ms
s_bg.gif
1605 ms
tt.gif
1668 ms
more.gif
1652 ms
m1.gif
1720 ms
photoshowtest.asp
1816 ms
w9.gif
1735 ms
m_bg.gif
1815 ms
m2.gif
1862 ms
photoshowtest2.asp
1802 ms
m3.gif
1850 ms
m_di.gif
1766 ms
l1.gif
1920 ms
l_bg.gif
1825 ms
or2.gif
1922 ms
l_d.gif
1696 ms
l2.gif
1769 ms
dd.gif
1631 ms
mm1.gif
1688 ms
mm1_bg.gif
1664 ms
t1.gif
1742 ms
4.gif
1727 ms
mm1d.gif
1675 ms
mm2.gif
1718 ms
mm2_bg.gif
1726 ms
t2.gif
1706 ms
mm2d.gif
1677 ms
mm3.gif
1760 ms
t3.gif
1661 ms
mm4.gif
1769 ms
t4.gif
1867 ms
s1.gif
1816 ms
s2.gif
1763 ms
s3.gif
1897 ms
s4.gif
1863 ms
s5.gif
1805 ms
s6.gif
1997 ms
bottom_bg.gif
1926 ms
logo_d.gif
1939 ms
jseq.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.
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
jseq.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
jseq.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jseq.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 Jseq.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.
jseq.com
Open Graph description is not detected on the main page of Jseq. 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: