Access 121soho.com. 合肥治疗皮肤病医院「收费」看皮肤科哪家医院好-合肥肤康皮肤医院

121soho.com screenshot

36

Performance

Renders faster than
56% of other websites
36

Accessibility

Visual factors better than
that of 18% of websites
54

Best Practices

More advanced features
available than in
19% of websites
69

SEO

Google-friendlier than
28% of websites

First Response

9.7 sec

Resources Loaded

128.8 sec

Page Rendered

1.2 sec

121soho.com screenshot

About Website

Welcome to 121soho.com homepage info - get ready to check 121 Soho best content right away, or after learning these important things about 121soho.com

合肥肤康皮肤病医院「口碑不错」是安徽合肥治疗皮肤病较好的专科医院,擅长治疗痘痘,痤疮,脱发,腋臭,牛皮癣,白癜风,过敏,皮炎,湿疹,灰指甲,荨麻疹等皮肤疑难杂症.

Visit 121soho.com

Key Findings

We analyzed 121soho.com page load time and found that the first response time was 9.7 sec and then it took 129.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 48 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

1/100

25%

SI (Speed Index)

Value11.3 s

6/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.417

24/100

15%

TTI (Time to Interactive)

Value11.1 s

21/100

10%

121soho.com

9694 ms

www.121soho.com

6077 ms

sjtz.js

2093 ms

style.css

4467 ms

jquery.js

10099 ms

Our browser made a total of 281 requests to load all elements on the main page. We found that 77% of them (215 requests) were addressed to the original 121soho.com, 10% (27 requests) were made to Dht.zoosnet.net and 4% (11 requests) were made to R.mapbar.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain 121soho.com.

Content Size

2.2 MB

After Optimization

1.7 MB

In fact, the total size of 121soho.com main page is 2.2 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.6 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 75.7 kB

Original 96.2 kB
After minification 80.0 kB
After compression 20.5 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 16.1 kB, which is 17% 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 75.7 kB or 79% of the original size.

Image Optimization

-9%

Potential reduce by 144.8 kB

Original 1.6 MB
After minification 1.5 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. 121 Soho images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 327.1 kB

Original 478.9 kB
After minification 439.0 kB
After compression 151.8 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 327.1 kB or 68% of the original size.

Requests Now

217

After Optimization

162

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the interpretation of your content by users in different locales.

High

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

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.

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Uses deprecated APIs

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document doesn't use legible font sizes

Language and Encoding

Language Detected

ZH
Language Claimed

N/A
Encoding

GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 121soho.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 121soho.com main page’s claimed encoding is gb2312. 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.

Social Sharing Optimization

121soho.com

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