Your Website Score is

Similar Ranking

19
REGATTA SZABADIDŐKÖZPONT – REGATTA SZABADIDŐKÖZPONT
hotelregatta.hu
19
HIDRATÁLÓDJ STÍLUSOSAN
horizonpalack.com
19
CAR-GO AUTÓSZERVIZ BUDAPEST | AUTÓSZERELŐ BUDAPEST XI. KERÜLET
car-go.hu
19
HÁZTÁJIT OTTHONRA
haztajitotthonra.hu
19
WEBOLDAL, WEBÁRUHÁZ KÉSZÍTÉS ÉS FELÚJÍTÁS | SOCIAL MEDIA MEGJELENÉS
white-informatics.hu
19
KEZDŐLAP / TRENDI BURKOLATOK ÁRUHÁZA
ecsempe.hu
19
CELLDÖMÖLK TAXI - CELL TAXI, RENDELJ TAXIT EGÉSZ NAP
celltaxi.hu

Latest Sites

2
ESTONE | BEJELENTKEZÉS
bigtorrent.eu
12
TINWILIGHT-SZIKRACSKA
szikracska.hu
30
NYITÓLAP - NŐI VÁLTÓ
noivalto.hu
19
ESKÜVŐSZERVEZÉS MINDENKINEK | ESKÜVŐBRIGÁD
eskuvobrigad.hu
88
GOOGLE
google.hu
14
LASER MIX ARENA – A JÖVŐ JÁTÉKA
lasermixarena.hu
27
WPKURZUS | ONLINE VIDEÓS WORDPRESS TANFOLYAMOK
wpkurzus.hu

Top Technologies

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

19 mercarius.hu Last Updated: 3 months

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

Desktop

Mobile

Performance Desktop Score 83%
Best Practices Desktop Score 71%
SEO Desktop Score 82%
Progressive Web App Desktop Score 52%
Performance Mobile Score 55%
Best Practices Mobile Score 71%
SEO Mobile Score 79%
Progressive Web App Mobile Score 54%
Page Authority Authority 11%
Domain Authority Domain Authority 19%
Moz Rank 1.1/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 37 Characters
MERCARIUS - GEPJARMU-FLOTTAKEZELES.HU
Meta Description 0 Characters
NO DATA
Effective URL 20 Characters
https://mercarius.hu
Excerpt Page content
Mercarius - Gepjarmu-flottakezeles.hu ...
Keywords Cloud Density
bővebben8 mercarius7 rövidtávú5 gépjármű5 autóbérlés4 saját4 akár4 assistance3 nélkül3 rólunk3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
bővebben 8
mercarius 7
rövidtávú 5
gépjármű 5
autóbérlés 4
saját 4
akár 4
assistance 3
nélkül 3
rólunk 3
Google Preview Your look like this in google search result
MERCARIUS - GEPJARMU-FLOTTAKEZELES.HU
https://mercarius.hu
Mercarius - Gepjarmu-flottakezeles.hu ...
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~19 KB
Code Size: ~10.54 KB
Text Size: ~8.47 KB Ratio: 44.55%

Social Data

Delicious Total: 0
Facebook Total: 492
Google Total: 0
Linkedin Total: 0
Pinterest Total: 0
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0

Estimation Traffic and Earnings

8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly

Technologies

PWA - Manifest

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

Desktop

Desktop Screenshot
Speed Index 1.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint 2.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids an excessive DOM size 241 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)
Efficiently encode images Potential savings of 511 KiB
Optimized images load faster and consume less cellular data
Avoid serving legacy JavaScript to modern browsers Potential savings of 12 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
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 CPU Idle 1.3 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/).
Eliminate render-blocking resources Potential savings of 970 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid chaining critical requests 16 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
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
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
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
Properly size images Potential savings of 8 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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 Meaningful Paint 1.3 s
First Meaningful Paint measures when the primary content of a page is visible
Includes front-end JavaScript libraries with known security vulnerabilities 10 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Max Potential First Input Delay 30 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Initial server response time was short Root document took 110 ms
Keep the server response time for the main document short because all other requests depend on it
Keep request counts low and transfer sizes small 40 requests • 1,659 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Remove unused JavaScript Potential savings of 110 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Time to Interactive 1.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoids enormous network payloads Total size was 1,659 KiB
Large network payloads cost users real money and are highly correlated with long load times
Preload key requests Potential savings of 110 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Cumulative Layout Shift 0.061
Cumulative Layout Shift measures the movement of visible elements within the viewport
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Serve static assets with an efficient cache policy 30 resources found
A long cache lifetime can speed up repeat visits to your page
Serve images in next-gen formats Potential savings of 835 KiB
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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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

Mobile

Mobile Screenshot
First CPU Idle 5.0 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/).
Serve images in next-gen formats Potential savings of 618 KiB
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
First Meaningful Paint 4.7 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint (3G) 6990 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 33% 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
Remove unused JavaScript Potential savings of 110 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoids an excessive DOM size 241 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)
Avoid long main-thread tasks 6 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
Minimizes main-thread work 1.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Eliminate render-blocking resources Potential savings of 2,970 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoids enormous network payloads Total size was 1,405 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Max Potential First Input Delay 110 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Cumulative Layout Shift 0.004
Cumulative Layout Shift measures the movement of visible elements within the viewport
Serve static assets with an efficient cache policy 24 resources found
A long cache lifetime can speed up repeat visits to your page
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 12 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
JavaScript execution time 0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index 7.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First Contentful Paint 3.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 10 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Initial server response time was short Root document took 120 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint 9.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Time to Interactive 5.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid chaining critical requests 16 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
Keep request counts low and transfer sizes small 34 requests • 1,405 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
Efficiently encode images Potential savings of 422 KiB
Optimized images load faster and consume less cellular data
Total Blocking Time 40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds

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
Warning! Your description is not 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
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
mercarius.co Available Buy Now!
mercarius.us Available Buy Now!
mercarius.com Available Buy Now!
mercarius.org Available Buy Now!
mercarius.net Available Buy Now!
mrcarius.hu Available Buy Now!
jercarius.hu Available Buy Now!
iercarius.hu Available Buy Now!

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Wed, 13 Jan 2021 13:16:02 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: PHPSESSID=43k18givet816fejsi83qj33t3; path=/
Vary: User-Agent
Content-Type: text/html; charset=UTF-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records