Access blog.miniasp.com. 記載著 Will 在網路世界的學習心得與技術分享

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value1,580 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.052

98/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

blog.miniasp.com

1508 ms

Global.css

444 ms

bootstrap.min.css

671 ms

main.css

449 ms

responsive.css

455 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 30% of them (36 requests) were addressed to the original Blog.miniasp.com, 25% (30 requests) were made to Static.xx.fbcdn.net and 14% (17 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Blog.miniasp.com.

Content Size

933.3 kB

After Optimization

440.3 kB

In fact, the total size of Blog.miniasp.com main page is 933.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 464.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 87.4 kB

Original 112.7 kB
After minification 108.1 kB
After compression 25.3 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 87.4 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 13.6 kB

Original 220.8 kB
After minification 207.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. Blog Miniasp images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 279.9 kB

Original 464.0 kB
After minification 407.6 kB
After compression 184.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 279.9 kB or 60% of the original size.

CSS Optimization

-82%

Potential reduce by 112.1 kB

Original 135.9 kB
After minification 128.1 kB
After compression 23.8 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. Blog.miniasp.com needs all CSS files to be minified and compressed as it can save up to 112.1 kB or 82% of the original size.

Requests Now

115

After Optimization

The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Miniasp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 13 to 1 for CSS 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

Image elements do not have [alt] attributes

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

Serves images with low resolution

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

High

robots.txt is not valid

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

EN
Encoding

UTF-8

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

blog.miniasp.com

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

記載著 Will 在網路世界的學習心得與技術分享 | The Will Will Web

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

blog.miniasp.com

Global.css

bootstrap.min.css

main.css

responsive.css

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

blog.miniasp.com

Global.css

bootstrap.min.css

main.css

responsive.css

shCore.css

shThemeDefault.css

zh-tw.res.axd

01-jquery-1.9.1.min.js

02-jquery.cookie.js

04-jquery-jtemplates.js

05-json2.min.js

blog.js

XRegExp.js

shCore.js

shAutoloader.js

shActivator.js

jquery.lazyload.mini.js

plusone.js

jquery.fancybox.css

res--804142268.js.axd

jquery-2.1.4.min.js

adsbygoogle.js

bootstrap.min.js

TheWillWillWeb

cb=gapi.loaded_0

ai.0.js

logo.png

facebook.png

twitter.png

googleplus.png

plurk.png

weibo.png

rss.png

rssButton.png

MCPD_1372.png

MCTS_1370.png

MVP_FullColor_ForBlog.jpg

opml.png

sdk.js

xd_arbiter.php

xd_arbiter.php

glyphicons-halflings-regular.woff