Your Website Score is

Similar Ranking

95
SIGN IN - GOOGLE ACCOUNTS
accounts.google.com
95
MEET GOOGLE DRIVE – ONE PLACE FOR ALL YOUR FILES
drive.google.com
95
GOOGLE SITES
sites.google.com
95
HOME - CONSILIUM
consilium.europa.eu
95
ADD-ONS FOR FIREFOX (EN-US)
addons.mozilla.org
94
UPDATE YOUR BROWSER | FACEBOOK
facebook.com
94
FACEBOOK FOR DEVELOPERS
developers.facebook.com

Latest Sites

67
SCREENCASTIFY | THE #1 SCREEN RECORDER FOR CHROME
screencastify.com
63
DOGECOIN
dogecoin.com
1
50
STRENGTH TRAINING, LIFTING WEIGHTS, AND 5×5 WORKOUTS | STRONGLIFTS
stronglifts.com
5
DOMINO’S PIZZA - ПИЦЦЕРИЯ №1 В КИЕВЕ
dominos.ua

Top Technologies

Google Font API
Font Scripts
Nginx
Web Servers
Apache
Web Servers
WordPress
CMS
CloudFlare
CDN
Font Awesome
Font Scripts
Google Tag Manager
Tag Managers
Twitter Bootstrap
Web Frameworks

95 consilium.europa.eu Last Updated: 4 days

Success 86 % of passed verification steps
Warning 7 % of total warning
Errors 7 % of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 96 %
Best Practices Desktop Score 85 %
SEO Desktop Score 90 %
Progressive Web App Desktop Score 58 %
Performance Mobile Score 93 %
Best Practices Mobile Score 85 %
SEO Mobile Score 92 %
Progressive Web App Mobile Score 59 %
Page Authority Authority 69 %
Domain Authority Domain Authority 97 %
Moz Rank 6.9 /10
Bounce Rate Rate 0 %
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 16Characters
HOME - CONSILIUM
Meta Description 137Characters
The European Council and the Council of the EU are served by a single administration, the General Secretariat of the Council (GSC). 
Effective URL 31Characters
https://www.consilium.europa.eu
Excerpt Page content
Home - Consilium Go to content ...
Keywords Cloud Density
cookies8 council5 website5 european4 about3 union2 used2 data2 improve2 more2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
cookies 8
council 5
website 5
european 4
about 3
union 2
used 2
data 2
improve 2
more 2
Google Preview Your look like this in google search result
HOME - CONSILIUM
https://www.consilium.europa.eu
The European Council and the Council of the EU are served by a single administration, the General Secretariat of the Council (GSC). 
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~17.99 KB
Code Size: ~9.28 KB
Text Size: ~8.72 KB Ratio: 48.44 %

Estimation Traffic and Earnings

163,708
Unique Visits
Daily
302,859
Pages Views
Daily
$293
Income
Daily
4,583,824
Unique Visits
Monthly
8,631,482
Pages Views
Monthly
$7,325
Income
Monthly
53,041,392
Unique Visits
Yearly
101,760,624
Pages Views
Yearly
$77,352
Income
Yearly

Technologies

Only Registered Users

Sign up for see all features and reviews about this site

Login

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Keep request counts low and transfer sizes small 11 requests • 583 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 6 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.9 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 52 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
Reduce server response times (TTFB) Root document took 750 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 110 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.1 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
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 0.9 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 583 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.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 0.9 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 4 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 150 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)
Preload key requests Potential savings of 510 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible

Mobile

Mobile Screenshot
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
Speed Index 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 3.5 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 583 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.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 5 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 150 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 11 requests • 583 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 6 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 240 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 4.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
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) 3169 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 sized appropriately 100% 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 97.16% 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 52 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
Server response times are low (TTFB) Root document took 480 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
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 210 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Congratulations! Your site not have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

642

Global Rank

137

Italy
Traffic
Search

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
date: Thu, 21 May 2020 01:20:47 GMT
content-type: text/html; charset=utf-8
set-cookie: __cfduid=d40f7f6360dead9acea84f71507ca56cf1590024047; expires=Sat, 20-Jun-20 01:20:47 GMT; path=/; domain=.consilium.europa.eu; HttpOnly; SameSite=Lax
cache-control: no-cache
pragma: no-cache
expires: -1
vary: Accept-Encoding
x-content-type-options: nosniff
x-xss-protection: 1; mode=block
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 596a7a171a8a398c-PHX
content-encoding: gzip
cf-request-id: 02d66aa2720000398cc510f200000001
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome