29.3 sec in total
11.1 sec
18 sec
223 ms
Click here to check amazing Crihq content. Otherwise, check out these important facts you probably never knew about crihq.com
CRI后勤超市网
Visit crihq.comWe analyzed Crihq.com page load time and found that the first response time was 11.1 sec and then it took 18.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
crihq.com performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value15.5 s
0/100
25%
Value14.4 s
1/100
10%
Value1,120 ms
23/100
30%
Value0.17
70/100
15%
Value9.9 s
28/100
10%
11095 ms
1484 ms
1492 ms
478 ms
474 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that all of those requests were addressed to Crihq.com and no external sources were called. The less responsive or slowest element that took the longest time to load (11.1 sec) belongs to the original domain Crihq.com.
Page size can be reduced by 100.5 kB (46%)
219.2 kB
118.6 kB
In fact, the total size of Crihq.com main page is 219.2 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. 25% of websites need less resources to load. Images take 107.4 kB which makes up the majority of the site volume.
Potential reduce by 23.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 4.5 kB, which is 15% 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 23.8 kB or 79% of the original size.
Potential reduce by 10.1 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. Crihq images are well optimized though.
Potential reduce by 47.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 47.2 kB or 81% of the original size.
Potential reduce by 19.5 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. Crihq.com needs all CSS files to be minified and compressed as it can save up to 19.5 kB or 82% of the original size.
Number of requests can be reduced by 17 (28%)
61
44
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Crihq. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
crihq.com
11095 ms
style.css
1484 ms
common.js
1492 ms
index.js
478 ms
transport.js
474 ms
utils.js
1480 ms
cycle_image.js
1517 ms
logo.gif
446 ms
bnt_log.gif
480 ms
bnt_reg.gif
462 ms
more.gif
442 ms
5170_thumb_G_1363217873991.jpg
450 ms
1267737883549119560.gif
481 ms
1267737782704315214.jpg
664 ms
1267738615900131993.jpg
955 ms
moreBrands.gif
931 ms
cri1.gif
1979 ms
5265_thumb_G_1407360850044.jpg
1578 ms
5230_thumb_G_1384214175718.jpg
1929 ms
5217_thumb_G_1374541446678.jpg
1792 ms
4960_thumb_G_1331165509315.jpg
1384 ms
5138_thumb_G_1361299439563.jpg
1429 ms
5106_thumb_G_1351718651996.jpg
2561 ms
5275_thumb_G_1414624059873.jpg
1887 ms
5276_thumb_G_1414624089174.jpg
2055 ms
5277_thumb_G_1414624117369.jpg
2242 ms
5278_thumb_G_1414624142775.jpg
2382 ms
5531_thumb_G_1430084775328.jpg
2388 ms
5532_thumb_G_1430084833490.jpg
3068 ms
4828_thumb_G_1301705518416.jpg
2525 ms
5165_thumb_G_1363217628514.jpg
2690 ms
5574_thumb_G_1455477951356.jpg
2851 ms
5575_thumb_G_1455478219966.jpg
2835 ms
5585_thumb_G_1456966163419.jpg
2990 ms
5584_thumb_G_1456966025933.jpg
3027 ms
5590_thumb_G_1457308842920.jpg
3163 ms
5591_thumb_G_1457308904134.jpg
3327 ms
5589_thumb_G_1457308789222.jpg
3339 ms
5596_thumb_G_1457309157402.jpg
3495 ms
5604_thumb_G_1457309673003.jpg
3507 ms
5594_thumb_G_1457309061630.jpg
3522 ms
bnt_top.gif
3708 ms
data.js
4057 ms
bnt_home.gif
3485 ms
topNavBg.gif
3641 ms
topNavR.gif
3748 ms
NavBg.gif
3760 ms
searchBg.gif
3820 ms
bg.gif
4080 ms
bnt_search.gif
3906 ms
h3title.gif
3810 ms
catBg.gif
3763 ms
lineBg.gif
3340 ms
foucsBg.gif
3088 ms
salesBg.gif
3392 ms
salesTitBg.gif
3283 ms
salesGoodBg.gif
3366 ms
box_2Bg.gif
3380 ms
itemH2Bg.gif
2969 ms
helpTitBg.gif
3256 ms
logo1.gif
3153 ms
footerLine.gif
3036 ms
crihq.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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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
Image elements do not have [alt] attributes
Links do not have a discernible name
crihq.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
Serves images with low resolution
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
crihq.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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Crihq.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 Crihq.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.
crihq.com
Open Graph description is not detected on the main page of Crihq. 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: