Access xingya.nidbox.com. nidBox 親子盒子

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

diary

414 ms

blog.min.css

339 ms

blog32.min.css

369 ms

jquery.min.js

34 ms

common.js

383 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Xingya.nidbox.com, 31% (24 requests) were made to Pica.nidbox.net and 8% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Pic.nidbox.net.

Content Size

535.3 kB

After Optimization

308.7 kB

In fact, the total size of Xingya.nidbox.com main page is 535.3 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. 50% of websites need less resources to load. Images take 265.3 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 25.0 kB

Original 36.1 kB
After minification 35.3 kB
After compression 11.0 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 25.0 kB or 69% of the original size.

Image Optimization

-19%

Potential reduce by 49.7 kB

Original 265.3 kB
After minification 215.6 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. Obviously, Xingya NidBox needs image optimization as it can save up to 49.7 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-57%

Potential reduce by 96.2 kB

Original 168.3 kB
After minification 165.0 kB
After compression 72.1 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 96.2 kB or 57% of the original size.

CSS Optimization

-85%

Potential reduce by 55.6 kB

Original 65.7 kB
After minification 65.7 kB
After compression 10.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. Xingya.nidbox.com needs all CSS files to be minified and compressed as it can save up to 55.6 kB or 85% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

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 semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Links are not crawlable

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 uses legible font sizes

Language and Encoding

Language Detected

JA
Language Claimed

N/A
Encoding

UTF-8

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

xingya.nidbox.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

nidBox 親子盒子

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

diary

blog.min.css

blog32.min.css

jquery.min.js

common.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

diary

blog.min.css

blog32.min.css

jquery.min.js

common.js

show_ads.js

i_popup.gif

lovedingbao2820p.jpg

21533341660925_357_m.jpg

9a4187cc-d80c-4c6d-9b71-2c76ea241682.jpg

1010330000051_S1.jpg

21530181376186_395_m.jpg

1010330000272_S1.jpg

ac8a47f9-435e-4b5f-87f6-fc430e7eba53.jpg

split_icon_blog.png

mu_bg.jpg

mu.png

title2.png

sider_title.gif

phoebe88.jpg

angel1121.jpg

ivy3411158.jpg

my45.jpg

juliachien0911.jpg

kms5960.jpg

tiffanyloveyoyo.jpg

ivy1000919.jpg

mjbox.jpg

box.jpg

asd9595.jpg

m123446501e.jpg

ashely.jpg

1010330000242_S1.jpg

21403275236375_326_m.jpg

ca-pub-1213390046296096.js

zrt_lookup.html

show_ads_impl.js

btn_bg.png

15.png

ga.js

atrk.js

scrolltopcontrol_nidbox.png

__utm.gif