17 sec in total
1.1 sec
15.2 sec
655 ms
Welcome to ijimo.com homepage info - get ready to check Ijimo best content right away, or after learning these important things about ijimo.com
千寻墨问
Visit ijimo.comWe analyzed Ijimo.com page load time and found that the first response time was 1.1 sec and then it took 15.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ijimo.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value7.0 s
6/100
25%
Value9.8 s
10/100
10%
Value90 ms
99/100
30%
Value0.151
76/100
15%
Value7.9 s
43/100
10%
1139 ms
1380 ms
838 ms
909 ms
700 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 97% of them (104 requests) were addressed to the original Ijimo.com, 1% (1 request) were made to Js.users.51.la and 1% (1 request) were made to Discuz.gtimg.cn. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Ijimo.com.
Page size can be reduced by 426.6 kB (23%)
1.8 MB
1.4 MB
In fact, the total size of Ijimo.com main page is 1.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. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 86.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 86.8 kB or 83% of the original size.
Potential reduce by 129.7 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. Ijimo images are well optimized though.
Potential reduce by 128.2 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 128.2 kB or 68% of the original size.
Potential reduce by 82.0 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. Ijimo.com needs all CSS files to be minified and compressed as it can save up to 82.0 kB or 80% of the original size.
Number of requests can be reduced by 24 (23%)
105
81
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ijimo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
ijimo.com
1139 ms
www.ijimo.com
1380 ms
style_8_common.css
838 ms
common.js
909 ms
portal.js
700 ms
focus.js
708 ms
jquery.min.js
1011 ms
jquery.SuperSlide.js
701 ms
index.css
1068 ms
4577760.js
678 ms
discuz_tips.js
1313 ms
topnav_bg.png
301 ms
mintip.gif
297 ms
n5_gzwm.png
296 ms
weixinewm.jpg
1872 ms
bgimg.jpg
1655 ms
logo.png
571 ms
n5_ssxz.png
569 ms
n5_dhgl.png
570 ms
ad4.png
855 ms
ad3.png
1654 ms
ad1.png
2409 ms
39863b9187cd08bee7e1f91b473b10a7.jpg
2352 ms
3933776e344ac2cdf74e0159170fc1f6.jpg
2019 ms
a8067da7ab924d080473e7a678c16701.jpg
2459 ms
36c99f492f2383a1930cc1234aa66d61.jpg
3270 ms
cc3eefde1d6ec16fe249c35894e2ea09.jpg
3591 ms
e62d5a380f0789cf6ab4874ecc33c846.jpg
2298 ms
0aa34f035a6ad2179536f79c3d16fa82.jpg
2574 ms
a46a75dd71f027bc915bafcf72391429.jpg
2619 ms
efe9a09a47e9f02a3315ea5592fff985.jpg
2678 ms
4105a5900ab0b374c74d6b4ac49de580.jpg
3689 ms
765a190d03c1bdd16bd5a0c8ed332b86.jpg
2854 ms
ad2.png
4284 ms
ad7.png
3499 ms
ad5.png
6227 ms
icon_0.gif
1677 ms
85d9aa040f2c472cb5fedea0880dd539.jpg
3427 ms
06e3f1ef7ff8bc80ecea9b048e2134eb.jpg
3320 ms
485e863b55f1b93057013a7925600407.jpg
2841 ms
bbcbfcd3e2adc7207c52ba1bb3c891c5.jpg
2951 ms
9d06064a4429ae99abbf00a97cb700f6.jpg
2922 ms
eb456304ca6fb1fc90f4e70cba45f435.jpg
2959 ms
84dc0c23b47fa5e67d5bdbc6a96682ea.jpg
3266 ms
af0b23dbf2f000f63eb5e5a36184f81c.jpg
2964 ms
6245d03818d4ad935699238036647690.jpg
2935 ms
ad8ab6ad38369053f83820a8ecff8d9f.jpg
3070 ms
26_120_120.jpg
2512 ms
76952552e2b5de88e639d5b3529a6a77.jpg
3140 ms
6977780c40795c12831aa89844766189.jpg
2386 ms
28_120_120.jpg
2431 ms
3d2723936a83513e57f906db3b7c1488.jpg
4275 ms
27_120_120.jpg
2584 ms
c1bf750a80097f5182571c971dd831a2.jpg
4054 ms
25_120_120.jpg
2449 ms
24_120_120.jpg
2541 ms
22_120_120.jpg
2828 ms
23_120_120.jpg
2572 ms
21_120_120.jpg
2659 ms
20_120_120.jpg
2603 ms
63874847988c6386c47b0e90954e4db9.jpg
4029 ms
19_120_120.jpg
2639 ms
12_120_120.jpg
2690 ms
15_120_120.jpg
3603 ms
06_120_120.jpg
2746 ms
01_120_120.jpg
2751 ms
97_120_120.jpg
2904 ms
91_120_120.jpg
2977 ms
87_120_120.jpg
3110 ms
83_120_120.jpg
3152 ms
79_120_120.jpg
3342 ms
75_120_120.jpg
3120 ms
5157504834329b88ba65e49db64e7395.jpg
4496 ms
c9329b213d89173f70699d147fc9a0aa.jpg
4539 ms
20d8c197f26ef998abeb88d14a249597.jpg
4049 ms
a667abb657b47268b4b78388e16c054d.jpg
4555 ms
7cf608b0ad9904941ae173f12783c0e7.jpg
4457 ms
eaf4083d6a7487fa5d0bd8ff718b0b9c.jpg
5686 ms
ad6.png
6070 ms
footer_ico_01.jpg
4288 ms
footer_ico_02.jpg
4353 ms
footer_ico_03.jpg
4272 ms
footer_ico_04.jpg
4277 ms
footer_ico_05.jpg
4249 ms
n5_dhbg.png
4344 ms
n5_ejdhbg.jpg
4203 ms
mu_portal.png
4199 ms
shadow.png
4171 ms
n5_btbg1.gif
4199 ms
n5_n1.gif
4175 ms
n5_n2.gif
4153 ms
n5_n3.gif
4056 ms
n5_n4.gif
4106 ms
n5_n5.gif
4154 ms
n5_n6.gif
4020 ms
n5_n7.gif
3951 ms
n5_n8.gif
3890 ms
n5_csico.png
3859 ms
n5_csli.png
4233 ms
n5_kjdl.png
3627 ms
n5_hdfq.png
3674 ms
loading.gif
4055 ms
btns.png
3673 ms
n5_dzyh.png
3624 ms
n5_dzyhli.gif
3741 ms
n5_flglbg.gif
3682 ms
scrolltop.png
3609 ms
ijimo.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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.
ijimo.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ijimo.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
ZH
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ijimo.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 Ijimo.com main page’s claimed encoding is gbk. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
ijimo.com
Open Graph description is not detected on the main page of Ijimo. 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: