Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

phlnet.com.br

PHL © Elysio: Nome da Instituio

Page Load Speed

3 sec in total

First Response

398 ms

Resources Loaded

2.1 sec

Page Rendered

519 ms

phlnet.com.br screenshot

About Website

Click here to check amazing PHL Net content for Brazil. Otherwise, check out these important facts you probably never knew about phlnet.com.br

Biblioteca 24 horas na Web

Visit phlnet.com.br

Key Findings

We analyzed Phlnet.com.br page load time and found that the first response time was 398 ms and then it took 2.6 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

phlnet.com.br performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

phlnet.com.br

398 ms

phl.css

109 ms

phlnet_cabecalho.html

902 ms

phlnet_search.html

905 ms

phlnet_integrantes.html

1676 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 20% of them (2 requests) were addressed to the original Phlnet.com.br, 80% (8 requests) were made to Elysio.com.br. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Elysio.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.9 kB (67%)

Content Size

5.8 kB

After Optimization

1.9 kB

In fact, the total size of Phlnet.com.br main page is 5.8 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. CSS take 2.6 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 1.0 kB

  • Original 1.7 kB
  • After minification 1.7 kB
  • After compression 699 B

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 1.0 kB or 60% of the original size.

JavaScript Optimization

-58%

Potential reduce by 884 B

  • Original 1.5 kB
  • After minification 1.1 kB
  • After compression 637 B

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 884 B or 58% of the original size.

CSS Optimization

-78%

Potential reduce by 2.0 kB

  • Original 2.6 kB
  • After minification 2.2 kB
  • After compression 570 B

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. Phlnet.com.br needs all CSS files to be minified and compressed as it can save up to 2.0 kB or 78% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

The browser has sent 8 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PHL Net. According to our analytics all requests are already optimized.

Accessibility Review

phlnet.com.br accessibility score

60

Accessibility Issues

Names and labels

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.

Impact

Issue

High

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

phlnet.com.br best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

phlnet.com.br 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

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phlnet.com.br 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 Phlnet.com.br main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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