Folha.uol.com.br - SEO Checker

Your Website Score is

Similar Ranking

AVENTURAS NA HISTÓRIA &MIDDOT;

aventurasnahistoria.uol.com.br

BOL MAIL

bmail1.uol.com.br

TELEGRAM MESSENGER

t.me

WORLD WIDE WEB CONSORTIUM (W3C)

w3.org

BOL - BRASIL ONLINE

bol.uol.com.br

BATE-PAPO UOL

batepapo.uol.com.br

UOL SAC: ATENDIMENTO ONLINE, TIRA-DÚVIDAS SOBRE SERVIÇOS E AJUDA SOBRE PRODUTOS

sac.uol.com.br

Latest Sites

BITCOINS43 | EARN FREE BITCOINS EVERY DAY

bitcoins43.com

FACEBOOK - LOG IN OR SIGN UP

facebook.com

INVESTISSEMENTVIVA

investissementviva.com

sharenow126.com

BUY STROMECTOL - IVERMECTIN ONLINE

ivermectin24h.com

EXABIT - BITCOIN CLOUD MINING

exabit.co

404 NOT FOUND

beurax.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

93 folha.uol.com.br Last Updated: 1 year

Success 70% of passed verification steps

Warning 15% of total warning

Errors 15% of total errors, require fast action

Mobile

Performance Desktop Score 48%

Best Practices Desktop Score 62%

SEO Desktop Score 100%

Progressive Web App Desktop Score 42%

Performance Mobile Score 29%

Best Practices Mobile Score 69%

SEO Mobile Score 97%

Progressive Web App Mobile Score 44%

Page Authority Authority 63%

Domain Authority Domain Authority 95%

Moz Rank 6.3/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 57 Characters

FOLHA DE S.PAULO: NOTÍCIAS, IMAGENS, VÍDEOS E ENTREVISTAS

Meta Description 154 Characters

Siga a Folha e fique informado sobre tudo o que acontece no Brasil e no mundo. Notícias sobre política, economia, cultura, esporte, entretenimento e mais.

Effective URL 28 Characters

https://www.folha.uol.com.br

Excerpt Page content

Folha de S.Paulo: Notícias, Imagens, Vídeos e Entrevistas ...

Meta Keywords 1 Detected

folha

Keywords Cloud Density

folha66 ícone42 fechar42 compartilhar41 para27 paulo20 sobre14 melhor11 mais11 governo10

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
folha	66
ícone	42
fechar	42
compartilhar	41
para	27
paulo	20
sobre	14
melhor	11
mais	11
governo	10

Google Preview Your look like this in google search result

FOLHA DE S.PAULO: NOTÍCIAS, IMAGENS, VÍDEOS E ENTREVISTAS

https://www.folha.uol.com.br

Siga a Folha e fique informado sobre tudo o que acontece no Brasil e no mundo. Notícias sobre política, economia, cultura, esporte, entretenimento e m

Robots.txt File Detected

http://folha.uol.com.br/robots.txt

Sitemap.xml File Detected

http://folha.uol.com.br/sitemap.xml

Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system

Updated: 1970-01-01 / 51 years

Create on: 1970-01-01 / 51 years

Expires on: 2023-04-24 / 26 months 7 days

Universo Online S.A. ,BR BR BR BR

Registrar Email: l-registrobr[email protected]

Nameservers

eliot.uol.com.br

200.221.11.98

borges.uol.com.br

200.147.255.105

charles.uol.com.br

200.147.38.8

Page Size Code & Text Ratio

Document Size: ~376.71 KB

Code Size: ~312.13 KB

Text Size: ~64.59 KB Ratio: 17.15%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

PWA - Manifest

Folha de S.Paulo Folha de S.Paulo

The web app manifest is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in areas where they would expect to see apps (for example, a mobile device's home screen)

Param short_name

Folha de S.Paulo

Param name

Folha de S.Paulo

Param description

Siga a Folha e fique informado sobre tudo o que acontece no Brasil e no mundo. Notícias sobre política, economia, cultura, esporte, entretenimento e mais.

Param start_url

https://www.folha.uol.com.br/

Param display

standalone

Param dir

ltr

Param lang

pt-BR

Param orientation

portrait-primary

Param background_color

#ffffff

Param theme_color

#262626

Desktop

Server response times are low (TTFB) Root document took 510 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 330 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 73 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Efficiently encode images Potential savings of 104 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 160 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 620 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 2.2 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Defer offscreen images Potential savings of 615 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Properly size images Potential savings of 1,313 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 3.2 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 4.6 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoid enormous network payloads Total size was 4,157 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 5.5 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 0.7 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 18 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load

Avoid an excessive DOM size 2,986 elements

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

First Meaningful Paint 1.5 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 211 requests • 4,157 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 53 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 320 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 5.3 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 26.4 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 60 ms

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy

Remove unused CSS Potential savings of 79 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Uses deprecated APIs 1 warning found

Deprecated APIs will eventually be removed from the browser

Serve images in next-gen formats Potential savings of 472 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Mobile

Serve static assets with an efficient cache policy 30 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 850 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 21.1 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Page load is not fast enough on mobile networks Interactive at 21.1 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 460 ms

First Contentful Paint (3G) 4860 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Tap targets are not sized appropriately 68% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements

Document uses legible font sizes 100% legible text

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

Remove unused CSS Potential savings of 80 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Serve images in next-gen formats Potential savings of 88 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Server response times are low (TTFB) Root document took 390 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 1,310 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 73 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Efficiently encode images Potential savings of 49 KB

Optimized images load faster and consume less cellular data

Reduce the impact of third-party code Third-party code blocked the main thread for 1,740 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 4,670 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 8.8 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Defer offscreen images Potential savings of 150 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Speed Index 9.7 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 6.4 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoids enormous network payloads Total size was 2,347 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 17.7 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 2.5 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 15 chains found

Avoid an excessive DOM size 2,981 elements

First Meaningful Paint 6.4 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 137 requests • 2,347 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 200 OK
Server: nginx
Date: Tue, 26 Nov 2019 14:12:45 GMT
Content-Type: text/html
Content-Length: 54900
Connection: keep-alive
Cache-Control: max-age=60
Expires: Tue, 26 Nov 2019 14:22:07 GMT
Content-Encoding: gzip
Accept-Ranges: bytes
X-Varnish: 1717913065 1717898064
Age: 37
Via: CacheUOL
X-Cache: HIT
Vary: Host,Accept-Encoding, User-Agent

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	folha.uol.com.br	200.147.36.85	IN	58
NS	folha.uol.com.br	eliot.uol.com.br	IN	3140
NS	folha.uol.com.br	charles.uol.com.br	IN	3140
NS	folha.uol.com.br	borges.uol.com.br	IN	3140
TXT	folha.uol.com.br	google-site-verification=nmY3FR_XkHLuxTHAM6Y1_Bd_VzMhfXsTuvNspSfr_hU	IN	3140
AAAA	folha.uol.com.br	2804:49c:319:430::339	IN	59

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

93 folha.uol.com.br Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Navegg

Nginx

Varnish

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments