Your Website Score is

Similar Ranking

22
MAIL ORDER MARIJUANA, CBD, AND CURRENT LEGISLATION | MARIJUANA DIRECT
marijuana-direct.com
22
ДЖЕРЕЛИЯ - ➦ САЙТ ОФИЦИАЛЬНОГО ПРЕДСТАВИТЕЛЯ КОМПАНИИ ДЖЕРЕЛИЯ - JERELIA.KIEV.UA
jerelia.kiev.ua
22
BEST PILES HOSPITAL | PAINLESS PILES TREATMENT IN JAIPUR - CBLMHFH
cblmhfh.com
22
PARELORENTZ CENTER|--- & PREMIUM ACCESS EXCLUSIVE STOCK IMAGES, PHOTOS, AND VIDEOS FEATURES
parelorentzcenter.net
22
TREE SERVICES NEAR ME - TREE SERVICE FOR EVERYONE | TREECUTPRO
treecutpro.com
22
10 BEST PACKERS AND MOVERS IN JAIPUR - COMPARE 4--- QUOTES
call2shiftjaipur.in
22
::DISHPAL::
dishpal.com

Latest Sites

93
GOOGLE
google.de
19
COME TO ALABAMA | LOLPIX
lolpix.net
31
ᐉ ПОСЛЕДНИЕ И ВАЖНЫЕ АВТОМОБИЛЬНЫЕ НОВОСТИ В РОССИИ И МИРЕ
wiki-auto.com
31
ВЫЗВАТЬ ЭВАКУАТОР В ХАРЬКОВЕ ОТ 700 ГРН - ЗАКАЗАТЬ УСЛУГИ ЭВАКУАЦИИ АВТОМОБИЛЯ ПО ГОРОДУ И ОБЛАСТИ
towtruck.kharkov.ua
23
DIRT BIKE GRAPHICS - MX GRAPHICS - WORLDWIDE 2-3 DAYS--- SHIPPING
decallab.eu
23
SEARCH FLIGHTS - TRAVELMAXI.COM
flights.travelmaxi.com
23
CHEAP HOTEL SEARCH - TRAVELMAXI.COM
hotels.travelmaxi.com

Top Technologies

Google Font API
Font Scripts
WordPress
CMS
Font Awesome
Font Scripts
Apache
Web Servers
Nginx
Web Servers
CloudFlare
CDN
Twitter Bootstrap
Web Frameworks
Yoast SEO
SEO

22 company2business.directory Last Updated: 2 weeks

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

Desktop

Mobile

Performance Desktop Score 56%
Best Practices Desktop Score 71%
SEO Desktop Score 82%
Progressive Web App Desktop Score 11%
Performance Mobile Score 12%
Best Practices Mobile Score 64%
SEO Mobile Score 82%
Progressive Web App Mobile Score 14%
Page Authority Authority 35%
Domain Authority Domain Authority 11%
Moz Rank 3.5/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 79 Characters
COMPANY, NEWS, ARTICLE BUSINESS SERVICE - DIRECTORY
Meta Description 153 Characters
Business Directory help for Companies to find faster on search engines. submit proses easy & simple, see for yourself how quick increase website traffic.
Effective URL 33 Characters
http://company2business.directory
Excerpt Page content
Company, News, Article Business Service - Directory ...
Meta Keywords 4 Detected
Keywords Cloud Density
city17 berlin15 search12 posts6 finance5 family5 education5 shopping5 real5 estate5
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
city 17
berlin 15
search 12
posts 6
finance 5
family 5
education 5
shopping 5
real 5
estate 5
Google Preview Your look like this in google search result
COMPANY, NEWS, ARTICLE BUSINESS SERVICE - DIRE
http://company2business.directory
Business Directory help for Companies to find faster on search engines. submit proses easy & simple, see for yourself how quick increase website traff
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 2020-11-24 / 3 months
Create on: 2019-10-10 / 1 year
Expires on: 2021-10-10 / 7 months 14 days

Cronon AG ,DE
Registrar Name: REDACTED FOR PRIVACY
Registrar Whois Server: www.cronon.net/index.php/whois-abfrage.html
Registrar URL: http://www.cronon.net
Registrar Phone: REDACTED
Registrar Email: Please
Registrar Address: REDACTED FOR PRIVACY , REDACTED FOR PRIVACY

REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Email: Please
Admin Phone: REDACTED
Admin Address: REDACTED FOR PRIVACY, REDACTED FOR PRIVACY

Nameservers
shades18.rzone.de
docks08.rzone.de
Page Size Code & Text Ratio
Document Size: ~106.74 KB
Code Size: ~63.26 KB
Text Size: ~43.48 KB Ratio: 40.73%

Estimation Traffic and Earnings

176
Unique Visits
Daily
325
Pages Views
Daily
$0
Income
Daily
4,928
Unique Visits
Monthly
9,263
Pages Views
Monthly
$0
Income
Monthly
57,024
Unique Visits
Yearly
109,200
Pages Views
Yearly
$0
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
Eliminate render-blocking resources Potential savings of 530 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 320 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
Reduce JavaScript execution time 2.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid chaining critical requests 20 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 238 requests • 4,167 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Max Potential First Input Delay 170 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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 long main-thread tasks 10 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
Total Blocking Time 330 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minify JavaScript Potential savings of 3 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Remove unused JavaScript Potential savings of 130 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Enable text compression Potential savings of 326 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
First Meaningful Paint 1.4 s
First Meaningful Paint measures when the primary content of a page is visible
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
First Contentful Paint 1.1 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce initial server response time Root document took 860 ms
Keep the server response time for the main document short because all other requests depend on it
Efficiently encode images Potential savings of 1,180 KiB
Optimized images load faster and consume less cellular data
Does not use HTTPS 48 insecure requests 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
Estimated Input Latency 60 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 20.1 s
A fast page load over a cellular network ensures a good mobile user experience
Avoid an excessive DOM size 1,684 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)
Time to Interactive 4.7 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
Serve static assets with an efficient cache policy 74 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint 2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Properly size images Potential savings of 981 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Cumulative Layout Shift 0.002
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Minify CSS Potential savings of 48 KiB
Minifying CSS files can reduce network payload sizes
Avoid enormous network payloads Total size was 4,167 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed Index 2.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Avoid serving legacy JavaScript to modern browsers Potential savings of 6 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
First CPU Idle 3.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/).
Serve images in next-gen formats Potential savings of 1,576 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
Remove unused CSS Potential savings of 227 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
Minimize main-thread work 3.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

Mobile

Mobile Screenshot
Document uses legible font sizes 91.29% 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
First CPU Idle 16.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/).
Max Potential First Input Delay 470 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minify JavaScript Potential savings of 3 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Time to Interactive 18.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Serve static assets with an efficient cache policy 78 resources found
A long cache lifetime can speed up repeat visits to your page
Properly size images Potential savings of 183 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid enormous network payloads Total size was 4,108 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed Index 9.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Avoid chaining critical requests 20 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
Enable text compression Potential savings of 326 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Estimated Input Latency 200 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
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
Eliminate render-blocking resources Potential savings of 1,760 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 2,480 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
First Contentful Paint (3G) 10620 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Keep request counts low and transfer sizes small 207 requests • 4,108 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Page load is not fast enough on mobile networks Interactive at 18.9 s
A fast page load over a cellular network ensures a good mobile user experience
Does not use HTTPS 44 insecure requests 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
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
Remove unused CSS Potential savings of 225 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
Minify CSS Potential savings of 48 KiB
Minifying CSS files can reduce network payload sizes
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.
Serve images in next-gen formats Potential savings of 1,533 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
Remove unused JavaScript Potential savings of 146 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Efficiently encode images Potential savings of 1,180 KiB
Optimized images load faster and consume less cellular data
First Contentful Paint 5.0 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce JavaScript execution time 8.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Cumulative Layout Shift 0.026
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint 11.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Meaningful Paint 5.0 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid an excessive DOM size 1,718 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 6 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
Total Blocking Time 2,220 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce initial server response time Root document took 710 ms
Keep the server response time for the main document short because all other requests depend on it
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
Minimize main-thread work 13.3 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
Warning! Your title is not 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
Congratulations! Your website appears to have a favicon.
Broken Links
Warning! You have broken links View links

Alexa Rank

0

Local Rank: / Users: / PageViews:

1,547,988

Global Rank

Domain Available

Only Registered Users

Sign up for see all features and reviews about this site

Login

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Mon, 15 Feb 2021 15:04:27 GMT
Server: Apache/2.4.43 (Unix)
X-Powered-By: PHP/7.4.13
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Vary: User-Agent
Content-Type: text/html; charset=UTF-8
Set-Cookie: ci_session=p2mbs6a9h3h4oqo1u18rluneb3rqbtgh; expires=Mon, 15-Feb-2021 17:04:27 GMT; Max-Age=7200; path=/; HttpOnly
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Add extension to Chrome