Your Website Score is

Similar Ranking

51
BUE DE MUSICA - KIZOMBA, ZOUK, AFRO HOUSE, SEMBA, MÚSICAS
buedemusica.com
51
DICȚIONAR EXPLICATIV AL LIMBII ROMÂNE | DEXONLINE
dexonline.ro
51
KING.COM
king.com
51
ANUNTURI GRATUITE - PESTE 4 MILIOANE ANUNTURI - OLX.RO
olx.ro
51
INSTAGRAM
instagram.com
51
BOOKING.COM | OFFICIAL SITE | THE BEST HOTELS & ACCOMMODATIONS
booking.com
51
FREE ONLINE FORM BUILDER, CREATE HTML FORMS AND SURVEYS - COGNITO FORMS
cognitoforms.com

Latest Sites

14
OSLOWAY | YOUR BEST LOCAL TOURS AND EXPERIENCES IN OSLO
osloway.no
22
JUST A MOMENT...
hourlyminer.com
33
ピアノ教室ネット｜先生との出会いはここから。全国のピアノ教室から検索！
pnet.kawai.jp
19
ADAGIETTOピアノ教室|飯能|ピアノに興味がある皆さんへ|
adagiettopiano.com
33
ГЛАВНАЯ | UNIEX
uniex.biz
23
AHMADIMADO - TRUSTED DOGECOIN CLOUD MINING
ahmadimado.net
19
DOGESILVA LIMITED - HOME
dogesilva.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

51 granma.cu Last Updated: 7 months

Success 62% of passed verification steps
Warning 15% of total warning
Errors 23% of total errors, require fast action
Share

Desktop

Mobile

Performance Desktop Score 100%
Best Practices Desktop Score 69%
SEO Desktop Score 100%
Progressive Web App Desktop Score 38%
Performance Mobile Score 95%
Best Practices Mobile Score 69%
SEO Mobile Score 99%
Progressive Web App Mobile Score 41%
Page Authority Authority 52%
Domain Authority Domain Authority 77%
Moz Rank 5.2/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 31 Characters
GRANMA - ÓRGANO OFICIAL DEL PCC
Meta Description 63 Characters
Órgano oficial del Comité Central del Partido Comunista de Cuba
Effective URL 20 Characters
http://www.granma.cu
Excerpt Page content
Granma - Órgano oficial del PCC MULTIMEDIA| BLOGS| ...
Keywords Cloud Density
comentarios27 cuba20 este8 cubana8 radio8 mundo7 partido6 habana6 tras5 para5
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
comentarios 27
cuba 20
este 8
cubana 8
radio 8
mundo 7
partido 6
habana 6
tras 5
para 5
Google Preview Your look like this in google search result
GRANMA - ÓRGANO OFICIAL DEL PCC
http://www.granma.cu
Órgano oficial del Comité Central del Partido Comunista de Cuba
Robots.txt File Detected
http://granma.cu/robots.txt
Sitemap.xml File No Found
http://granma.cu/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~57.84 KB
Code Size: ~37.65 KB
Text Size: ~20.19 KB Ratio: 34.91%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Desktop

Desktop Screenshot
Serve static assets with an efficient cache policy 84 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 0.7 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
Estimated Input Latency 10 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 15 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 2,071 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
Does not use HTTPS 86 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Server response times are low (TTFB) Root document took 240 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 290 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 1,622 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 0 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 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.0 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
Properly size images Potential savings of 1,384 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 0.7 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 2,993 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.4 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.5 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 15 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
Avoids an excessive DOM size 658 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 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 91 requests • 2,993 KB
To set budgets for the quantity and size of page resources, add a budget.json file

Mobile

Mobile Screenshot
Avoid enormous network payloads Total size was 2,966 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 1.6 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 14 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
Avoids an excessive DOM size 658 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 2.1 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 86 requests • 2,966 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 79 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 150 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 3.8 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
Estimated Input Latency 10 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
First Contentful Paint (3G) 3120 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 95% 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 86.76% 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 16 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 2,071 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
Does not use HTTPS 81 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Server response times are low (TTFB) Root document took 240 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 880 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 1,622 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 50 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 120 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.3 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 28 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 24 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 2.8 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).

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

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.0 200 OK
Date: Mon, 13 Jan 2020 21:29:16 GMT
Server: Apache
cache-control: no-cache
Set-Cookie: session_payload=9c1636cda75df434351996e9bf78ab76ced6c361%2ByN%2BEdwe9UtaNzDIrIzmUa64bPc5C1v%2BmNQlfT98lCy8%2BRxvBn5f5nbDc6JtSbCAI%2FNY1nUQ6ngbvO7Pn%2FthkAYaE3cT4kvPRq0ijutTyzobJ6R1VL9IdcdWcyvN%2FvsJItEwsWsvYfZn2iChSmV9ED9Zn8fAQt7NsHjf%2BWCm1NyrC2jrNe%2F2Kp4WQXi4z8hGIvKV4WMV9BnisYqUE%2BEDdKvM3B%2FIooBDZF3lwpVPjRfxVjkH40TG9j7dd95DByBqtrTbR1wZbj1N8E4V1ft6Tqk6NlkQf%2Be1QxGjtERYdufLkeIzXdl0IAdSpkcSPOb50zyTtKZ4MsZUFo5vnXInp1Q%3D%3D; expires=Tue, 14-Jan-2020 14:09:16 GMT; path=/; httponly
Set-Cookie: tx_session=3946cf8e8fcdc727e97eadf996a1c192885e993f%2Bxo0sMM8V2NGJPOZrbvgeQp3otQ6OHs27BaZyNtev; path=/; httponly
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Frame-Options: sameorigin
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 20
Connection: close
Content-Type: text/html; charset=UTF-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A granma.cu 190.92.127.13 IN 7199
A granma.cu 190.92.127.12 IN 7199
NS granma.cu ns2.cip.cu IN 51239
NS granma.cu ns1.cip.cu IN 51239
MX granma.cu grai2.granma.cu IN 86400
MX granma.cu mx1.granma.cu IN 86400
MX granma.cu mx2.granma.cu IN 86400

Comments

Copyright © 2019 Check.web.id | Privacy Policy | Terms and Conditions
Languages | Bahasa Deutsch English Español Français Nederlands Português Pусский
Add extension to Chrome