Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 0

    Best Practices

  • 92

    SEO

    Google-friendlier than
    79% of websites

Page Load Speed

2.9 sec in total

First Response

297 ms

Resources Loaded

2.3 sec

Page Rendered

345 ms

1622.psee.io screenshot

About Website

Visit 1622.psee.io now to see the best up-to-date 1622 Psee content for Taiwan and also check out these interesting facts you probably never knew about 1622.psee.io

PicSee URL Shortener

Visit 1622.psee.io

Key Findings

We analyzed 1622.psee.io page load time and found that the first response time was 297 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

1622.psee.io performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value7.7 s

46/100

10%

Network Requests Diagram

picsee.soci.vip

297 ms

bootstrap.min.css

16 ms

font-awesome.min.css

24 ms

picsee.css

6 ms

jquery-1.11.1.min.js

43 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original 1622.psee.io, 20% (4 requests) were made to Wcdn.pse.im and 10% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Dmp.tenmax.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 103.6 kB (29%)

Content Size

354.6 kB

After Optimization

251.0 kB

In fact, the total size of 1622.psee.io main page is 354.6 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. 20% of websites need less resources to load. Images take 181.1 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 8.1 kB

  • Original 12.6 kB
  • After minification 12.3 kB
  • After compression 4.5 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 8.1 kB or 64% of the original size.

Image Optimization

-0%

Potential reduce by 324 B

  • Original 181.1 kB
  • After minification 180.7 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. 1622 Psee images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 92.8 kB

  • Original 156.9 kB
  • After minification 155.9 kB
  • After compression 64.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 92.8 kB or 59% of the original size.

CSS Optimization

-59%

Potential reduce by 2.3 kB

  • Original 4.0 kB
  • After minification 3.3 kB
  • After compression 1.6 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. 1622.psee.io needs all CSS files to be minified and compressed as it can save up to 2.3 kB or 59% of the original size.

Requests Breakdown

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

Requests Now

17

After Optimization

13

The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1622 Psee. 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.

Accessibility Review

1622.psee.io accessibility score

94

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

SEO Factors

1622.psee.io SEO score

92

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

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1622.psee.io can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that 1622.psee.io 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

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