Tools & Wizards About Us
afonsopacifer.github.io screenshot

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

afonsopacifer.github.io

Linkedin

Page Load Speed

172 ms in total

First Response

15 ms

Resources Loaded

157 ms

Page Rendered

0 ms

afonsopacifer.github.io screenshot

About Website

Click here to check amazing Afonsopacifer Github content for China. Otherwise, check out these important facts you probably never knew about afonsopacifer.github.io

Visit afonsopacifer.github.io

Key Findings

We analyzed Afonsopacifer.github.io page load time and found that the first response time was 15 ms and then it took 157 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

afonsopacifer.github.io performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

afonsopacifer.github.io

15 ms

afonsopacifer.github.io

47 ms

css2

37 ms

css2

53 ms

js

79 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 70% of them (7 requests) were addressed to the original Afonsopacifer.github.io, 20% (2 requests) were made to Fonts.googleapis.com and 10% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (79 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 66.3 kB (7%)

Content Size

956.3 kB

After Optimization

890.0 kB

  • HTML
  • Images

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

HTML Optimization

-77%

Potential reduce by 36.8 kB

  • Original 48.0 kB
  • After minification 48.0 kB
  • After compression 11.2 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 36.8 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 29.5 kB

  • Original 908.3 kB
  • After minification 878.9 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. Afonsopacifer Github images are well optimized though.

Requests Breakdown

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

Requests Now

8

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

afonsopacifer.github.io

afonsopacifer.github.io

15 ms

afonsopacifer.github.io

afonsopacifer.github.io

47 ms

css2

css2

37 ms

css2

css2

53 ms

js

js

79 ms

polyfill-0b195e62fe7c324a988b.js

polyfill-0b195e62fe7c324a988b.js

32 ms

app-9fd978cbd6fff0ac1b7c.js

app-9fd978cbd6fff0ac1b7c.js

30 ms

framework-20f0105bd291af0656e5.js

framework-20f0105bd291af0656e5.js

28 ms

webpack-runtime-dedfc11c7d21773ec868.js

webpack-runtime-dedfc11c7d21773ec868.js

29 ms

afonso_pacifer_logo_white.svg

afonso_pacifer_logo_white.svg

18 ms

Accessibility Review

afonsopacifer.github.io accessibility score

100

Accessibility Issues

Best Practices

afonsopacifer.github.io best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

afonsopacifer.github.io SEO score

100

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

afonsopacifer.github.io

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