Hvg.hu - SEO Checker - Website Review

Your Website Score is

Similar Ranking

QAYNARINFO.AZ

qaynarinfo.az

LONGDO.COM : บริการลองดู พจนานุกรม แผนที่ จราจร บัตรสมาชิก

longdo.com

AMAZON A TO Z LOGIN

amazon.work

DAILY FANTASY CRICKET, FOOTBALL & BASKETBALL LEAGUE GAMES | 11WICKETS

11wickets.com

LIVESTREAM | SECURE LIVE STREAMING SOLUTION

livestream.com

HOME | MORGAN STANLEY

morganstanley.com

WPS OFFICE - FREE OFFICE DOWNLOAD (WORD, SPREADSHEETS,PRESENTATION, PDF, TEMPLATES) FOR PC & MOBILE, ALTERNATIVE TO MS OFFICE

wps.com

Latest Sites

ACUITY FUNDING

acuityfunding.com

sharenow126.com

MASUK

gm066.com

恭喜，站点创建成功！

51278.cc

m.fun8899jk.com

JOBIFY

jobify2u.com

PROLIKE

prolikeid.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

14 hvg.hu Last Updated: 1 year

Success 55% of passed verification steps

Warning 7% of total warning

Errors 38% of total errors, require fast action

Mobile

Performance Desktop Score 67%

Best Practices Desktop Score 54%

SEO Desktop Score 82%

Progressive Web App Desktop Score 27%

Performance Mobile Score 31%

Best Practices Mobile Score 69%

SEO Mobile Score 92%

Progressive Web App Mobile Score 26%

Page Authority Authority 0%

Domain Authority Domain Authority 0%

Moz Rank 0.0/10

Bounce Rate Rate 0%

Charset Encoding

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

Title Tag 14 Characters

HÍREK | HVG.HU

Meta Description 0 Characters

NO DATA

Effective URL 14 Characters

https://hvg.hu

Excerpt Page content

Hírek | hvg.hu Szeretne azonnal értesülni a legfontosabb hírekről? Nem kérem ...

Keywords Cloud Density

tovább10 hogy9 december9 lehet6 lesz5 tech5 világ5 hvg3605 csak4 magazin4

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

Keyword	Freq	Title	Desc	Domain	H1	H2
tovább	10
hogy	9
december	9
lehet	6
lesz	5
tech	5
világ	5
hvg360	5
csak	4
magazin	4

Google Preview Your look like this in google search result

HÍREK | HVG.HU

https://hvg.hu

Hírek | hvg.hu Szeretne azonnal értesülni a legfontosabb hírekről? Nem kérem ...

Robots.txt File Detected

http://hvg.hu/robots.txt

Sitemap.xml File No Found

http://hvg.hu/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~137.32 KB

Code Size: ~100.2 KB

Text Size: ~37.11 KB Ratio: 27.03%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Desktop

Max Potential First Input Delay 100 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.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 20.8 s

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

Estimated Input Latency 20 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 56 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 424 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

Reduce server response times (TTFB) Root document took 840 ms

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

Eliminate render-blocking resources Potential savings of 60 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 2 KB

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

Efficiently encode images Potential savings of 46 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 80 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 110 ms

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

JavaScript execution time 0.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 1,086 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 28 KB

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

Speed Index 2.5 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).

Avoid enormous network payloads Total size was 3,577 KB

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

Minimize main-thread work 2.2 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

Includes front-end JavaScript libraries with known security vulnerabilities 7 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 22 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 1,396 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)

Minify JavaScript Potential savings of 9 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 0.9 s

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

Keep request counts low and transfer sizes small 173 requests • 3,577 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 98 resources found

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

Mobile

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 10.5 s

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

Estimated Input Latency 90 ms

First Contentful Paint (3G) 6996 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 99.23% 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 24 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 65 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 1 insecure request 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

Avoid multiple page redirects Potential savings of 1,410 ms

Redirects introduce additional delays before the page can be loaded

Reduce server response times (TTFB) Root document took 770 ms

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

Eliminate render-blocking resources Potential savings of 580 ms

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

Reduce the impact of third-party code Third-party code blocked the main thread for 610 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 570 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.4 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 601 KB

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

Speed Index 9.4 s

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

First CPU Idle 8.1 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 1,977 KB

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

Minimize main-thread work 4.1 s

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

First Contentful Paint 3.7 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 6 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 8 chains found

Avoid an excessive DOM size 1,374 elements

First Meaningful Paint 3.7 s

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

Keep request counts low and transfer sizes small 147 requests • 1,977 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 89 resources found

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

Max Potential First Input Delay 250 ms

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

Time to Interactive 10.5 s

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

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
Date: Sat, 28 Dec 2019 13:31:56 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Set-Cookie: __cfduid=d5296f4aff0a15a721be8076a8b0c4bfd1577539916; expires=Mon, 27-Jan-20 13:31:56 GMT; path=/; domain=.hvg.hu; HttpOnly; SameSite=Lax
Cache-Control: private
Set-Cookie: _currentVersion=Desktop; domain=.hvg.hu; expires=Fri, 28-Dec-2029 13:31:56 GMT; path=/
X-Kong-Upstream-Latency: 54
X-Kong-Proxy-Latency: 0
Via: kong/1.0.2
Set-Cookie: uid=AAseX14HWUzDGQFpUeOWAg==; expires=Thu, 31-Dec-37 23:55:55 GMT; domain=hvg.hu; path=/
P3P: policyref="/w3c/p3p.xml", CP="CUR ADM OUR NOR STA NID"
Set-Cookie: uid=AAseX14HWUxY1EyhbCEWAg==; expires=Thu, 31-Dec-37 23:55:55 GMT; domain=hvg.hu; path=/
P3P: policyref="/w3c/p3p.xml", CP="CUR ADM OUR NOR STA NID"
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: 54c3e5bb3e2cefe0-EWR
Content-Encoding: gzip

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	hvg.hu	104.20.104.68	IN	278
A	hvg.hu	104.20.105.68	IN	278
NS	hvg.hu	olga.ns.cloudflare.com	IN	83504
NS	hvg.hu	jim.ns.cloudflare.com	IN	83504
MX	hvg.hu	hvg-hu.mail.protection.outlook.com	IN	3455
TXT	hvg.hu	google-site-verification=um-wpJxFN-RPbcGlb4aurs23ozPAAE0GNNXJfRrS748	IN	120
TXT	hvg.hu	Ax3PoA2NCK+9OGY4kyY3Cs0gspYmdm/ArQ96EO8C0h8mgyNsjWzflIr3E41ye5Wo37+o5vT9a+9OHY2Vhnfgkw==	IN	120
TXT	hvg.hu	v=spf1 include:spf.protection.outlook.com ip4:194.88.44.18 ip4:194.88.44.15 ip4:194.88.44.16 ip4:194.88.44.17 ip4:194.88.44.13 ip4:195.70.57.219 -all	IN	120
TXT	hvg.hu	facebook-domain-verification=z6ee4rfpnvgctkez3wqlacdk9kou1s	IN	120
TXT	hvg.hu	MS=ms84553730	IN	120
AAAA	hvg.hu	2606:4700:10::6814:6944	IN	226
AAAA	hvg.hu	2606:4700:10::6814:6844	IN	226

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

14 hvg.hu Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments