Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

123.io

The domain name 123.io is for sale

Page Load Speed

58.2 sec in total

First Response

10 sec

Resources Loaded

47.8 sec

Page Rendered

342 ms

123.io screenshot

About Website

Visit 123.io now to see the best up-to-date 123 content and also check out these interesting facts you probably never knew about 123.io

The domain name 123.io is for sale. Make an offer or buy it now at a set price.

Visit 123.io

Key Findings

We analyzed 123.io page load time and found that the first response time was 10 sec and then it took 48.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 18 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

123.io performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value2,770 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value20.7 s

2/100

10%

Network Requests Diagram

123.io

10020 ms

hao_20120104.js

1264 ms

xw.js

857 ms

clock.js

4374 ms

opensug.js

515 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 30% of them (20 requests) were addressed to the original 123.io, 26% (17 requests) were made to S0.hao123img.com and 9% (6 requests) were made to Img.tianqi.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Gss1.bdstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 385.0 kB (46%)

Content Size

843.9 kB

After Optimization

458.9 kB

In fact, the total size of 123.io main page is 843.9 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. 20% of websites need less resources to load. Images take 370.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 53.8 kB

  • Original 71.7 kB
  • After minification 70.4 kB
  • After compression 17.9 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 53.8 kB or 75% of the original size.

Image Optimization

-10%

Potential reduce by 36.5 kB

  • Original 370.2 kB
  • After minification 333.8 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. 123 images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 109.2 kB

  • Original 175.5 kB
  • After minification 175.5 kB
  • After compression 66.3 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 109.2 kB or 62% of the original size.

CSS Optimization

-82%

Potential reduce by 185.4 kB

  • Original 226.4 kB
  • After minification 225.1 kB
  • After compression 41.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. 123.io needs all CSS files to be minified and compressed as it can save up to 185.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (43%)

Requests Now

42

After Optimization

24

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

Accessibility Review

123.io accessibility score

88

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

123.io best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

123.io SEO score

85

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 123.io can be misinterpreted by Google and other search engines. Our service has detected that English 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 123.io 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.

Social Sharing Optimization

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