Tools & Wizards About Us
ngrok.cc screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

ngrok.cc

Sunny-Ngrok内网转发内网穿透 - 国内内网映射服务器

Page Load Speed

6.2 sec in total

First Response

493 ms

Resources Loaded

5.5 sec

Page Rendered

299 ms

ngrok.cc screenshot

About Website

Visit ngrok.cc now to see the best up-to-date Ngrok content for China and also check out these interesting facts you probably never knew about ngrok.cc

一条命令解决的外网访问内网问题，无需任何配置，下载客户端之后直接一条命令让外网访问您的内网不再是距离

Visit ngrok.cc

Key Findings

We analyzed Ngrok.cc page load time and found that the first response time was 493 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

ngrok.cc performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

ngrok.cc

493 ms

www.ngrok.cc

1176 ms

style.css

234 ms

jquery.min.js

682 ms

jquery.jslides.js

750 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 82% of them (14 requests) were addressed to the original Ngrok.cc, 12% (2 requests) were made to Hm.baidu.com and 6% (1 request) were made to Pub.idqqimg.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Ngrok.cc.

Page Optimization Overview & Recommendations

Page size can be reduced by 90.7 kB (13%)

Content Size

678.2 kB

After Optimization

587.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ngrok.cc main page is 678.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. Only 10% of websites need less resources to load. Images take 591.0 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 26.6 kB

  • Original 30.8 kB
  • After minification 20.1 kB
  • After compression 4.2 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 10.7 kB, which is 35% 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 26.6 kB or 86% of the original size.

Image Optimization

-9%

Potential reduce by 52.6 kB

  • Original 591.0 kB
  • After minification 538.4 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. Ngrok images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 7.2 kB

  • Original 47.9 kB
  • After minification 47.3 kB
  • After compression 40.6 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 7.2 kB or 15% of the original size.

CSS Optimization

-50%

Potential reduce by 4.2 kB

  • Original 8.5 kB
  • After minification 5.9 kB
  • After compression 4.3 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. Ngrok.cc needs all CSS files to be minified and compressed as it can save up to 4.2 kB or 50% of the original size.

Requests Breakdown

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

Requests Now

15

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ngrok.cc

ngrok.cc

493 ms

www.ngrok.cc

www.ngrok.cc

1176 ms

style.css

style.css

234 ms

jquery.min.js

jquery.min.js

682 ms

jquery.jslides.js

jquery.jslides.js

750 ms

jquery.SuperSlide.js

jquery.SuperSlide.js

751 ms

layer.min.js

layer.min.js

255 ms

layer.css

layer.css

285 ms

hm.js

hm.js

1210 ms

group.png

group.png

1772 ms

banner.png

banner.png

885 ms

join-box1.png

join-box1.png

228 ms

service.jpg

service.jpg

872 ms

product-tit-line.png

product-tit-line.png

373 ms

probox-img2.png

probox-img2.png

372 ms

sold-out.png

sold-out.png

2358 ms

hm.gif

hm.gif

290 ms

Accessibility Review

ngrok.cc accessibility score

58

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.

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

Best Practices

ngrok.cc best practices score

58

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

SEO Factors

ngrok.cc SEO score

76

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

robots.txt is not valid

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

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

    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 Ngrok.cc 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 Ngrok.cc 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

ngrok.cc

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