Tools & Wizards About Us
123.net screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

123.net

123NET - Official Site

Page Load Speed

2.2 sec in total

First Response

68 ms

Resources Loaded

1.5 sec

Page Rendered

630 ms

123.net screenshot

About Website

Click here to check amazing 123 content for United States. Otherwise, check out these important facts you probably never knew about 123.net

123NET: Michigan's trusted provider of data center, network, and voice services, dedicated to empowering Michigan with innovative solutions

Visit 123.net

Key Findings

We analyzed 123.net page load time and found that the first response time was 68 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

123.net performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value1,720 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

123.net

68 ms

www.123.net

572 ms

eea31b6f-1712343788.min.css

84 ms

all.css

48 ms

v4-shims.css

60 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 75% of them (51 requests) were addressed to the original 123.net, 4% (3 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (572 ms) belongs to the original domain 123.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.6 kB (24%)

Content Size

277.4 kB

After Optimization

211.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 123.net main page is 277.4 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. 55% of websites need less resources to load. Javascripts take 80.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 58.2 kB

  • Original 72.3 kB
  • After minification 63.4 kB
  • After compression 14.1 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 8.9 kB, which is 12% 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 58.2 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 28 B

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

JavaScript Optimization

-9%

Potential reduce by 7.2 kB

  • Original 80.3 kB
  • After minification 80.3 kB
  • After compression 73.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 148 B

  • Original 46.7 kB
  • After minification 46.7 kB
  • After compression 46.6 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.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (22%)

Requests Now

63

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 63 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 15 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

123.net

123.net

68 ms

www.123.net

www.123.net

572 ms

eea31b6f-1712343788.min.css

eea31b6f-1712343788.min.css

84 ms

all.css

all.css

48 ms

v4-shims.css

v4-shims.css

60 ms

js

js

59 ms

widget.js

widget.js

116 ms

080b01f7-1703026125.min.js

080b01f7-1703026125.min.js

115 ms

3a4c05c8-1703026125.min.js

3a4c05c8-1703026125.min.js

118 ms

6121234.js

6121234.js

55 ms

lazyload.min.js

lazyload.min.js

121 ms

gtm.js

gtm.js

59 ms

michigan-city-detroit.webp

michigan-city-detroit.webp

357 ms

montserrat-light.woff2

montserrat-light.woff2

205 ms

montserrat-semibold.woff2

montserrat-semibold.woff2

227 ms

montserrat-bold.woff2

montserrat-bold.woff2

205 ms

js

js

73 ms

analytics.js

analytics.js

156 ms

tracking.js

tracking.js

176 ms

banner.js

banner.js

223 ms

collectedforms.js

collectedforms.js

190 ms

fb.js

fb.js

188 ms

6121234.js

6121234.js

231 ms

conversations-embed.js

conversations-embed.js

206 ms

123net-logo.svg

123net-logo.svg

175 ms

icon-data-center.svg

icon-data-center.svg

176 ms

fiber-icon.svg

fiber-icon.svg

188 ms

wireless-icon.svg

wireless-icon.svg

208 ms

icon-voice.svg

icon-voice.svg

203 ms

logo_ford.svg

logo_ford.svg

206 ms

um-flint-logo.svg

um-flint-logo.svg

204 ms

henry-ford-health-systems-logo.svg

henry-ford-health-systems-logo.svg

213 ms

logo_gm.svg

logo_gm.svg

230 ms

aaa.svg

aaa.svg

231 ms

dte-logo.svg

dte-logo.svg

231 ms

logo_stellantis.svg

logo_stellantis.svg

227 ms

twitter-logo.svg

twitter-logo.svg

238 ms

united-wholesale-mortgage.png

united-wholesale-mortgage.png

252 ms

henderson-glass-logo.svg

henderson-glass-logo.svg

253 ms

motorcity-casino-logo.svg

motorcity-casino-logo.svg

255 ms

plummarket-logo.svg

plummarket-logo.svg

255 ms

internet-iconw.svg

internet-iconw.svg

264 ms

office-iconw.svg

office-iconw.svg

277 ms

wireless-iconw.svg

wireless-iconw.svg

283 ms

fiber-iconw.svg

fiber-iconw.svg

285 ms

substation-iconw.svg

substation-iconw.svg

286 ms

quality-iconw.svg

quality-iconw.svg

288 ms

upstream-iconw.svg

upstream-iconw.svg

290 ms

handshake-iconw.svg

handshake-iconw.svg

301 ms

icon-user-experience.svg

icon-user-experience.svg

303 ms

icon-modern-technology.svg

icon-modern-technology.svg

304 ms

icon-quote.svg

icon-quote.svg

307 ms

michigan-community.jpg

michigan-community.jpg

339 ms

grace-action.png

grace-action.png

315 ms

detroit-internet-exchange.png

detroit-internet-exchange.png

325 ms

dctplogo.png

dctplogo.png

328 ms

collect

collect

34 ms

DALL%C2%B7E-2024-05-10-13.28.57-Create-a-wide-image-representing-the-concept-of-Fiber-to-the-Curb-FTTC-technology.-The-image-should-feature-a-vibrant-abstract-depiction-of-fiber-o.webp

DALL%C2%B7E-2024-05-10-13.28.57-Create-a-wide-image-representing-the-concept-of-Fiber-to-the-Curb-FTTC-technology.-The-image-should-feature-a-vibrant-abstract-depiction-of-fiber-o.webp

454 ms

DALL%C2%B7E-2024-05-10-13.07.43-Image-representing-the-materials-used-in-microduct-conduits-focusing-on-the-variety-of-plastics-like-polyethylene.-Highlight-the-durability-against-e.webp

DALL%C2%B7E-2024-05-10-13.07.43-Image-representing-the-materials-used-in-microduct-conduits-focusing-on-the-variety-of-plastics-like-polyethylene.-Highlight-the-durability-against-e.webp

492 ms

DALL%C2%B7E-2024-05-10-10.49.01-Create-an-abstract-image-representing-the-concept-of-dynamic-voice-and-data-technologies.-The-image-should-depict-a-fusion-of-voice-and-digital-elemen.webp

DALL%C2%B7E-2024-05-10-10.49.01-Create-an-abstract-image-representing-the-concept-of-dynamic-voice-and-data-technologies.-The-image-should-depict-a-fusion-of-voice-and-digital-elemen.webp

233 ms

collect

collect

21 ms

DALL%C2%B7E-2024-05-09-15.47.00-A-series-of-three-wide-images-on-a-white-background-each-representing-different-network-configurations.-The-first-image-symbolizes-IP-Passthrough-sh.webp

DALL%C2%B7E-2024-05-09-15.47.00-A-series-of-three-wide-images-on-a-white-background-each-representing-different-network-configurations.-The-first-image-symbolizes-IP-Passthrough-sh.webp

408 ms

facebook.svg

facebook.svg

185 ms

twitter.svg

twitter.svg

182 ms

ga-audiences

ga-audiences

80 ms

linkedin.svg

linkedin.svg

182 ms

youtube.svg

youtube.svg

190 ms

instagram.svg

instagram.svg

205 ms

Accessibility Review

123.net accessibility score

95

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.

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.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

123.net SEO score

93

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

123.net

Open Graph data is detected on the main page of 123. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: