Your Website Score is

Similar Ranking

22
DROGERICA | SZÉPSÉG & EGÉSZSÉG – LR DROGÉRIA WEBÁRUHÁZ
drogerica.hu
22
TRADE MAGAZIN | FMCG HÍREK
trademagazin.hu
22
FŐTAXI.HU-MAIN PAGE
fotaxi.hu
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
CITY FUTI FUTÁRSZOLGÁLAT
cityfuti.hu

Latest Sites

16
❶ SEO ---YSIS TOOL • FREE WEBSITE TOOLS • WEBSITE CHECKER 2021
directorylib.com
26
K-HEALTHCARE GROUP | K-HEALTHCARE GROUP
koreahg.hu
19
HAVSZI SPORTELEMZŐ - SPORT TIPPEK, HÍREK, ELEMZÉSEK
havszi.hu
19
DENTIUM IMPLANT CENTER
dentiumimplantcenter.hu
26
MEDIPAC HUNGARY |
medipac.hu
2
KOCI MÉDIAÜGYNÖKSÉG
koci.hu
14
KEZDŐLAP - GUBINYI - GG:DESIGN
gubinyi.hu

Top Technologies

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

22 fotaxi.hu Last Updated: 2 months

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

Desktop

Mobile

Performance Desktop Score 57%
Best Practices Desktop Score 62%
SEO Desktop Score 83%
Progressive Web App Desktop Score 15%
Performance Mobile Score 21%
Best Practices Mobile Score 62%
SEO Mobile Score 83%
Progressive Web App Mobile Score 18%
Page Authority Authority 37%
Domain Authority Domain Authority 45%
Moz Rank 3.7/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 19 Characters
FŐTAXI.HU-MAIN PAGE
Meta Description 0 Characters
NO DATA
Effective URL 16 Characters
http://fotaxi.hu
Excerpt Page content
Főtaxi.hu-Main page Main page | Főtaxi ...
Keywords Cloud Density
főtaxi11 taxi5 more4 budapest4 taxis3 company3 oldalon2 leszek2 partnere2 hírek2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
főtaxi 11
taxi 5
more 4
budapest 4
taxis 3
company 3
oldalon 2
leszek 2
partnere 2
hírek 2
Google Preview Your look like this in google search result
FŐTAXI.HU-MAIN PAGE
http://fotaxi.hu
Főtaxi.hu-Main page Main page | Főtaxi ...
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~69.49 KB
Code Size: ~33.24 KB
Text Size: ~36.25 KB Ratio: 52.17%

Social Data

Delicious Total: 0
Facebook Total: 2,714
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
Total Blocking Time 40 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
Eliminate render-blocking resources Potential savings of 610 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Does not use HTTPS 1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. 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 190 ms
Redirects introduce additional delays before the page can be loaded
Avoid long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
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
Cumulative Layout Shift 0.191
Cumulative Layout Shift measures the movement of visible elements within the viewport
Speed Index 2.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Minimizes main-thread work 1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 18.8 s
A fast page load over a cellular network ensures a good mobile user experience
Remove unused JavaScript Potential savings of 306 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First CPU Idle 2.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/).
Avoid enormous network payloads Total size was 3,317 KiB
Large network payloads cost users real money and are highly correlated with long load times
Efficiently encode images Potential savings of 1,056 KiB
Optimized images load faster and consume less cellular data
Avoid chaining critical requests 30 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
Serve static assets with an efficient cache policy 58 resources found
A long cache lifetime can speed up repeat visits to your page
Time to Interactive 4.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint 4.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve images in next-gen formats Potential savings of 1,696 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
Keep request counts low and transfer sizes small 112 requests • 3,317 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Initial server response time was short Root document took 260 ms
Keep the server response time for the main document short because all other requests depend on it
Includes front-end JavaScript libraries with known security vulnerabilities 9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
JavaScript execution time 0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Remove unused CSS Potential savings of 35 KiB
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
First Meaningful Paint 1.6 s
First Meaningful Paint measures when the primary content of a page is visible
Avoids an excessive DOM size 330 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)
Properly size images Potential savings of 968 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport

Mobile

Mobile Screenshot
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 18.7 s
A fast page load over a cellular network ensures a good mobile user experience
Reduce the impact of third-party code Third-party code blocked the main thread for 470 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
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
Initial server response time was short Root document took 210 ms
Keep the server response time for the main document short because all other requests depend on it
Max Potential First Input Delay 310 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids an excessive DOM size 330 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)
Tap targets are not sized appropriately 77% 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
Estimated Input Latency 100 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
Total Blocking Time 800 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Document uses legible font sizes 95.02% 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
Serve images in next-gen formats Potential savings of 1,696 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
Defer offscreen images Potential savings of 569 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Efficiently encode images Potential savings of 1,056 KiB
Optimized images load faster and consume less cellular data
First CPU Idle 10.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/).
Does not use HTTPS 1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. 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
Largest Contentful Paint 18.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Keep request counts low and transfer sizes small 108 requests • 3,310 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Eliminate render-blocking resources Potential savings of 2,160 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid long main-thread tasks 16 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Meaningful Paint 6.0 s
First Meaningful Paint measures when the primary content of a page is visible
Minimize main-thread work 4.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid multiple page redirects Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded
Remove unused JavaScript Potential savings of 307 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Reduce JavaScript execution time 2.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid enormous network payloads Total size was 3,310 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid chaining critical requests 30 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
Speed Index 10.1 s
Speed Index shows how quickly the contents of a page are visibly populated
First Contentful Paint 4.5 s
First Contentful Paint marks the time at which the first text or image is painted
Remove unused CSS Potential savings of 35 KiB
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
Time to Interactive 18.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint (3G) 8651.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Properly size images Potential savings of 294 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Includes front-end JavaScript libraries with known security vulnerabilities 9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Serve static assets with an efficient cache policy 56 resources found
A long cache lifetime can speed up repeat visits to your page

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
Warning! Your website is not SSL secured (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
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

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
fotaxi.co Available Buy Now!
fotaxi.us Available Buy Now!
fotaxi.com Already Registered
fotaxi.org Already Registered
fotaxi.net Available Buy Now!
ftaxi.hu Available Buy Now!
rotaxi.hu Available Buy Now!
votaxi.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: Tue, 18 Aug 2020 13:15:07 GMT
Server: Apache
Set-Cookie: qtrans_cookie_test=qTranslate+Cookie+Test; path=/; domain=fotaxi.hu
Link: ; rel="https://api.w.org/"
Link: ; rel=shortlink
Content-Type: text/html; charset=UTF-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records