Your Website Score is

Similar Ranking

23
GREENIQ
greeniq.eu
23
HOMEPAGE - SEOBASE
seobase.com
23
TINYPHANT | ANIMAL FACTS AND STORIES
thetinyphant.com
23
UNANUNCIO.ES: COMPRA, VENDE, ENCUENTRA EMPLEO, PUBLICA ANUNCIOS GRATIS!
unanuncio.es
23
BEST EDUCATION CONSULTANT IN DELHI - TOP MIGRATION AGENTS IN INDIA
giecglobal.com
23
ГЕНЕРАТОР ПАРОЛЕЙ ОНЛАЙН – НАДЁЖНАЯ ЗАЩИТА ЛИЧНЫХ ДАННЫХ / GENERATOR PASSWORD
generator-password.ru
23
ГДЗ: ГОТОВЫЕ ДОМАШНИЕ ЗАДАНИЯ | ГДЗ ОНЛАЙН
gdz-online.ru

Latest Sites

47
SHOP E STORE - SHOP E STORE
shopestore.co.uk
23
ВЫКУП АВТОМОБИЛЯ В ПЕРМИ | АВТОВЫКУП
avtomix59.ru
31
KOKAIN KAUFEN ONLINE
kokainkaufen.ru
14
FREE ONLINE SEO TOOLS
freetoolsweb.com
19
ONLYVID - LATEST ONLYFANS VIDEOS --- LEAKS
onlyvid.net
31
LIDOCAIN KAUFEN BEI LIDOBASE:| ANONYM LIDOCAINPULVER BESTELLEN
lidobase.ru

23 greeniq.eu Last Updated: 3 years

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

Desktop

Mobile

Performance Desktop Score 47%
Best Practices Desktop Score 85%
SEO Desktop Score 82%
PWA Desktop Score 22%
Performance Mobile Score 24%
Best Practices Mobile Score 92%
SEO Mobile Score 83%
PWA Mobile Score 30%
Page Authority Authority 24%
Domain Authority Domain Authority 16%
Moz Rank 2.4/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 7 Characters
GREENIQ
Meta Description 36 Characters
Together we can keep the ocean clean
Effective URL 25 Characters
https://greeniq.eu/?_l=en
Excerpt Page content
GreenIQ ...
Meta Keywords 1 Detected
Keywords Cloud Density
read more6 water4 references4 harbour4 greenarc4 nightmare3 about3 worst3 manager3 technical3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
read more 6
water 4
references 4
harbour 4
greenarc 4
nightmare 3
about 3
worst 3
manager 3
technical 3
Google Preview Your look like this in google search result
GREENIQ
https://greeniq.eu/?_l=en
Together we can keep the ocean clean
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~34.64 KB
Code Size: ~28.5 KB
Text Size: ~6.14 KB Ratio: 17.73%

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

Desktop

Desktop Screenshot
Reduce unused JavaScript Potential savings of 34 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid chaining critical requests 55 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 serving legacy JavaScript to modern browsers Potential savings of 0 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
Keep request counts low and transfer sizes small 80 requests • 2,835 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Minify CSS Potential savings of 9 KiB
Minifying CSS files can reduce network payload sizes
Speed Index 3.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid enormous network payloads Total size was 2,835 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve static assets with an efficient cache policy 3 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Efficiently encode images Potential savings of 859 KiB
Optimized images load faster and consume less cellular data
Reduce unused CSS Potential savings of 46 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Defer offscreen images Potential savings of 728 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Reduce initial server response time Root document took 750 ms
Keep the server response time for the main document short because all other requests depend on it
Minimizes main-thread work 0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift 0.407
Cumulative Layout Shift measures the movement of visible elements within the viewport
Serve images in next-gen formats Potential savings of 1,489 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid long main-thread tasks 3 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 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
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
Time to Interactive 3.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Total Blocking Time 30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids an excessive DOM size 454 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.4 s
First Meaningful Paint measures when the primary content of a page is visible
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minify JavaScript Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
First Contentful Paint 2.4 s
First Contentful Paint marks the time at which the first text or image is painted
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
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
Eliminate render-blocking resources Potential savings of 3,460 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Properly size images Potential savings of 601 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint 4.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the 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

Mobile

Mobile Screenshot
Tap targets are not sized appropriately 94% 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
Avoids an excessive DOM size 408 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 serving legacy JavaScript to modern browsers Potential savings of 0 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
Keep request counts low and transfer sizes small 80 requests • 2,835 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
Largest Contentful Paint 17.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce JavaScript execution time 1.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Properly size images Potential savings of 245 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Cumulative Layout Shift 0.135
Cumulative Layout Shift measures the movement of visible elements within the viewport
Time to Interactive 14.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Reduce unused JavaScript Potential savings of 32 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid enormous network payloads Total size was 2,835 KiB
Large network payloads cost users real money and are highly correlated with long load times
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 820 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Initial server response time was short Root document took 350 ms
Keep the server response time for the main document short because all other requests depend on it
Defer offscreen images Potential savings of 334 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Document uses legible font sizes 99.83% 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
Avoid long main-thread tasks 15 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid large layout shifts 2 elements found
These DOM elements contribute most to the CLS of the page.
Reduce unused CSS Potential savings of 45 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid chaining critical requests 55 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
First Meaningful Paint 7.9 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint (3G) 13096 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Max Potential First Input Delay 290 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Serve images in next-gen formats Potential savings of 1,489 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Eliminate render-blocking resources Potential savings of 9,150 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Contentful Paint 6.9 s
First Contentful Paint marks the time at which the first text or image is painted
Speed Index 11.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Minify JavaScript Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Serve static assets with an efficient cache policy 3 resources found
A long cache lifetime can speed up repeat visits to your page
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
Efficiently encode images Potential savings of 859 KiB
Optimized images load faster and consume less cellular data
Minimize main-thread work 4.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Minify CSS Potential savings of 9 KiB
Minifying CSS files can reduce network payload sizes

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
Warning! Your title is not 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
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
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
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
greeniq.co Already Registered
greeniq.us Already Registered
greeniq.com Already Registered
greeniq.org Already Registered
greeniq.net Already Registered
geeniq.eu Already Registered
treeniq.eu Already Registered
breeniq.eu Already Registered

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
server: nginx/1.10.3 (Ubuntu)
date: Wed, 08 Dec 2021 18:16:30 GMT
content-type: text/html; charset=UTF-8
set-cookie: PHPSESSID=l04pueekjgbc171ma94ck9tgced3fkp68jk4niqp1g7eesgnfvimp19j6vscihrohgmfq1o8ulgb326jmqo26i8phdpmbk4unm3u271; path=/
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
strict-transport-security: max-age=63072000; includeSubdomains; preload
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
content-encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records