Access pulilife.com. 大埔里報埔里魚池國姓仁愛社區報新聞生活資訊觀光旅遊美食特產文教藝術社會福利文化求職求才不動產工商服務鄉親臉譜醫療飯店民宿

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value18.5 s

0/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value1,090 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

pulilife.com

1811 ms

analytics.js

38 ms

wp-emoji-release.min.js

502 ms

style.css

674 ms

styles.css

688 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 65% of them (81 requests) were addressed to the original Pulilife.com, 18% (22 requests) were made to Static.xx.fbcdn.net and 4% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Pulilife.com.

Content Size

9.4 MB

After Optimization

7.9 MB

In fact, the total size of Pulilife.com main page is 9.4 MB. 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. Images take 8.8 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 192.6 kB

Original 240.0 kB
After minification 219.4 kB
After compression 47.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 192.6 kB or 80% of the original size.

Image Optimization

-15%

Potential reduce by 1.3 MB

Original 8.8 MB
After minification 7.5 MB

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, Pulilife needs image optimization as it can save up to 1.3 MB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-18%

Potential reduce by 38.9 kB

Original 220.9 kB
After minification 220.9 kB
After compression 182.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 38.9 kB or 18% of the original size.

CSS Optimization

-1%

Potential reduce by 1.1 kB

Original 79.8 kB
After minification 79.6 kB
After compression 78.7 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. Pulilife.com has all CSS files already compressed.

Requests Now

117

After Optimization

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

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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 keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

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

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

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

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

ZH
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pulilife.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 Chinese language. Our system also found out that Pulilife.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

pulilife.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

大埔里報埔里魚池國姓仁愛社區報新聞生活資訊觀光旅遊美食特產文教藝術社會福利文化求職求才不動產工商服務鄉親臉譜醫療飯店民宿

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

pulilife.com

analytics.js

wp-emoji-release.min.js

style.css

styles.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

pulilife.com

analytics.js

wp-emoji-release.min.js

style.css

styles.css

foobox.free.min.css

polls-css.css

fl-icons.css

default.min.css

flatsome.css

style.css

jquery.js

jquery-migrate.min.js

frontend.min.js

no-right-click.js

jquery.lazyload.min.js

foobox.free.min.js

linkid.js

collect

collect

js

effects.css

dashicons.min.css

front.css

rps.js

scripts.js

underscore.min.js

front.min.js

polls-js.js

flatsome-live-search.js

hoverIntent.min.js

flatsome.js

wp-embed.min.js

forms-api.min.js

webfont.js

1060720-pulilifelogo-1.png

20180519-Ecological-town-adv.jpg

20190507-1adv.jpg

20230323-1loho-1067x800.jpg

20230320-3edu-600x800.jpg

20210910-10loho.jpg

20210329-6pub.jpg

20210324-5edu.jpg