Your Website Score is

Similar Ranking

7
【猎聘】招聘_找工作_精英职业发展平台
liepin.com
7
ERROR PAGE | EBAY
ebay.com.hk
7
ЗЕРКАЛО RUTOR.INFO :: СВОБОДНЫЙ ТОРРЕНТ ТРЕКЕР
rutor.is
7
֤®-VIP
burusoku-vip.com
7
FRONTPAGE - ZELYON MAGAZINE
zelyonmag.com
7
ANI24
ani24zo.com
7
CINECALIDAD - PELÍCULAS ONLINE Y DESCARGA GRATIS EN CALIDAD HD
cinecalidad.is

Latest Sites

14
PORTSTONE PARTNERS LIMITED
portstonepartnersltd.com
14
VENICTRADE.COM
venictrade.com
14
COINLUNO.COM
coinluno.com
14
SIGNCURRENCY.COM
signcurrency.com
14
ALLTRADESFX.COM
alltradesfx.com
19
MODERN KITCHENS | READIKIT | HOME PAGE
readikit.com
1
-
av4.xyz

Top Technologies

Nginx
Web Servers
PHP
Programming Languages
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
jQuery
JavaScript Frameworks
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

7 91boshi.net Last Updated: 10 months

Success 47% of passed verification steps
Warning 15% of total warning
Errors 38% of total errors, require fast action
Share

Desktop

Mobile

Performance Desktop Score 70%
Best Practices Desktop Score 54%
SEO Desktop Score 80%
Progressive Web App Desktop Score 31%
Performance Mobile Score 48%
Best Practices Mobile Score 54%
SEO Mobile Score 67%
Progressive Web App Mobile Score 30%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 17 Characters
ʿƸ,УʦƸ,У˲Ƹ-ʿ˲ٷՎЙ
Meta Description 0 Characters
NO DATA
Effective URL 22 Characters
http://www.91boshi.net
Google Preview Your look like this in google search result
ʿƸ,УʦƸ,У˲Ƹ-ʿ˲ٷՎЙ
http://www.91boshi.net
Robots.txt File Detected
http://91boshi.net/robots.txt
Sitemap.xml File No Found
http://91boshi.net/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~573 B
Code Size: ~553 B
Text Size: ~20 B Ratio: 3.49%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Desktop

Desktop Screenshot
Time to Interactive 1.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Minify CSS Potential savings of 2 KB
Minifying CSS files can reduce network payload sizes
Remove unused CSS Potential savings of 30 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 1,130 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Does not use HTTPS 129 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Reduce server response times (TTFB) Root document took 2,800 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 850 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 802 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 181 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Defer offscreen images Potential savings of 634 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 918 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 5.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.0 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 2,637 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 2.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 13 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoid an excessive DOM size 3,034 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 131 requests • 2,637 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 128 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 70 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Mobile

Mobile Screenshot
First Meaningful Paint 4.1 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 131 requests • 2,585 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 127 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 270 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 6.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
First Contentful Paint (3G) 8380 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Minify CSS Potential savings of 2 KB
Minifying CSS files can reduce network payload sizes
Remove unused CSS Potential savings of 30 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 1,099 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Does not use HTTPS 129 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Reduce server response times (TTFB) Root document took 1,960 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 3,190 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 802 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 181 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Minimize third-party usage Third-party code blocked the main thread for 30 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 120 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 3.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 781 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Properly size images Potential savings of 730 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 10.3 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 4.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 2,585 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 9.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 4.1 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 13 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoid an excessive DOM size 3,034 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/1.1 200 OK
Date: Wed, 25 Dec 2019 19:18:32 GMT
Content-Length: 45893
Content-Type: text/html
Content-Encoding: gzip
Content-Location: http://www.91boshi.net/index.html
Last-Modified: Wed, 25 Dec 2019 06:06:05 GMT
Accept-Ranges: bytes
ETag: "80c44964e9bad51:ae02"
Vary: Accept-Encoding
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A 91boshi.net 115.28.164.167 IN 549
NS 91boshi.net ns12.xincache.com IN 3549
NS 91boshi.net ns11.xincache.com IN 3549
MX 91boshi.net mxw.mxhichina.com IN 549
MX 91boshi.net mxn.mxhichina.com IN 549
MX 91boshi.net mail.bestedm.org IN 549
TXT 91boshi.net v=spf1 include:spf.bestedm.org -all IN 549

Comments

Copyright © 2019 Check.web.id | Privacy Policy | Terms and Conditions
Languages | Bahasa Deutsch English Español Français Nederlands Português Pусский
Add extension to Chrome