Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 57

    SEO

    Google-friendlier than
    20% of websites

imobile.com.cn

爱科技iMobile-专业的科技资讯信息分享网站

Page Load Speed

37.4 sec in total

First Response

1.3 sec

Resources Loaded

35.2 sec

Page Rendered

961 ms

imobile.com.cn screenshot

About Website

Visit imobile.com.cn now to see the best up-to-date Imobile content for United States and also check out these interesting facts you probably never knew about imobile.com.cn

爱科技专业的科技资讯信息分享网站,为广大用户提供手机排行榜报价图片、笔记本、汽车、平板电脑、智能硬件、家电等资讯信息,帮助用户及时了解科技行业动态。

Visit imobile.com.cn

Key Findings

We analyzed Imobile.com.cn page load time and found that the first response time was 1.3 sec and then it took 36.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. Unfortunately, there were 12 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

imobile.com.cn performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

83/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value1,850 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

imobile.com.cn

1274 ms

index_2015.css

1062 ms

jquery-1.10.2.min.js

1705 ms

browser_type.js

872 ms

m.js

974 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Imobile.com.cn, 40% (38 requests) were made to Pic.imobile.com.cn and 19% (18 requests) were made to Pos.baidu.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Pic.imobile.com.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (29%)

Content Size

4.3 MB

After Optimization

3.0 MB

In fact, the total size of Imobile.com.cn main page is 4.3 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.9 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 76.1 kB

  • Original 87.9 kB
  • After minification 74.2 kB
  • After compression 11.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 13.7 kB, which is 16% 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 76.1 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 172.8 kB

  • Original 2.9 MB
  • After minification 2.8 MB

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. Imobile images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 503.5 kB

  • Original 704.9 kB
  • After minification 689.5 kB
  • After compression 201.4 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 503.5 kB or 71% of the original size.

CSS Optimization

-89%

Potential reduce by 504.8 kB

  • Original 568.4 kB
  • After minification 395.5 kB
  • After compression 63.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. Imobile.com.cn needs all CSS files to be minified and compressed as it can save up to 504.8 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (34%)

Requests Now

80

After Optimization

53

The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

imobile.com.cn accessibility score

79

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Definition list items are not wrapped in <dl> 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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

<html> element does not have a [lang] attribute

Best Practices

imobile.com.cn best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

imobile.com.cn SEO score

57

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imobile.com.cn 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 Imobile.com.cn 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Imobile. 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: