Lisine.Rs - Info receives about 91 unique visitors and 181 (2.00 per visitor) page views per day which should earn about $0.74/day from advertising revenue. Estimated site value is $540.43. According to Alexa Traffic Rank is ranked number 8,146,020 in the world and 2.0E-6% of global Internet users visit it. Site is hosted in Germany and links to network IP address This server supports HTTPS and HTTP/2.

About -

Technologies used on Website

Web Servers
Google Analytics
Video Players
YouTube Profile

Title: Lisine - kafana sa prenoćištem "Izvor" Lisine - Dobrodošli
Description: Lisine Kafana "Izvor" Vrhunski kvalitet, usluga, ambijent... Kafana sa prenoćištem. Kafana "Izvor" Lisine nalazi se u opštini Despotovac, na obroncima planine Beljanice, u neposrednoj blizini vodopada Veliki Buk i izvora Veliko vrelo.
Last update was 10 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

How popular is

91 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
8,146,020 visit alexa
Alexa Reach:
2.0E-6%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

(Rank based on keywords, cost and organic traffic)
Organic Keywords:
(Number of keywords in top 20 Google SERP)
Organic Traffic:
(Number of visitors coming from top 20 search results)
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Mobile summary

(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Neue Medien Muennich GmbH 
Server Location:

Germany, DE

Other sites hosted on

There are no other sites hosted on this IP

+ How fast does load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

Currently Not Available

Page Speed (Google PageSpeed Insights) - Mobile

0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Speed Index 10.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 3.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 3.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 3.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 290 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 11.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 400 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 5948 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Estimated Input Latency 90 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. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Defer offscreen images - Potential savings of 373 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

SizePotential Savings
191 KB191 KB
90 KB90 KB
25 KB25 KB
24 KB24 KB
19 KB19 KB
16 KB16 KB
8 KB8 KB
Properly size images - Potential savings of 30 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

SizePotential Savings
85 KB30 KB
Remove unused CSS - Potential savings of 42 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. Learn more.

SizePotential Savings
44 KB42 KB
Avoids enormous network payloads - Total size was 1,734 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

402 KB
401 KB
191 KB
105 KB
91 KB
85 KB
59 KB
44 KB
44 KB
40 KB
Minimize main-thread work - 2.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Time Spent
Script Evaluation
1374 ms
Script Parsing & Compilation
323 ms
300 ms
Style & Layout
159 ms
Parse HTML & CSS
136 ms
124 ms
Garbage Collection
30 ms
Serve images in next-gen formats - Potential savings of 124 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. Learn more.

SizePotential Savings
191 KB70 KB
90 KB17 KB
25 KB15 KB
16 KB12 KB
19 KB10 KB
Avoids an excessive DOM size - 111 elements
A large DOM will increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Avoid multiple page redirects - Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
User Timing marks and measures - 6 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

TypeStart TimeDuration
Mark2936 ms0 ms
Mark2943 ms0 ms
Mark3140 ms0 ms
Mark3153 ms0 ms
Mark3249 ms0 ms
Mark3261 ms0 ms
Keep request counts low and transfer sizes small - 45 requests • 1,734 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
451734 KB
12952 KB
12625 KB
898 KB
229 KB
323 KB
86 KB
00 KB
241119 KB
Eliminate render-blocking resources - Potential savings of 1,050 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

SizePotential Savings
2 KB180
33 KB930
3 KB480
1 KB480
1 KB480
Efficiently encode images - Potential savings of 14 KB
Optimized images load faster and consume less cellular data. Learn more.

SizePotential Savings
16 KB9 KB
25 KB5 KB
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms355 ms0 KB0 KB301text/html
356 ms820 ms0 KB0 KB301text/html
820 ms1519 ms4 KB11 KB200text/htmlDocument
1533 ms2011 ms2 KB7 KB200text/cssStylesheet
1534 ms1905 ms33 KB91 KB200application/javascriptScript
1534 ms2133 ms3 KB14 KB200text/cssStylesheet
1534 ms2167 ms1 KB4 KB200text/cssStylesheet
1535 ms2115 ms1 KB3 KB200text/cssStylesheet
1535 ms2332 ms85 KB85 KB200image/jpegImage
1535 ms2340 ms91 KB90 KB200image/jpegImage
2453 ms2921 ms191 KB191 KB200image/jpegImage
2482 ms2716 ms24 KB24 KB200image/jpegImage
2483 ms2611 ms8 KB8 KB200image/pngImage
2483 ms3046 ms20 KB19 KB200image/pngImage
2483 ms2709 ms16 KB16 KB200image/jpegImage
2484 ms3048 ms25 KB25 KB200image/jpegImage
2333 ms2452 ms1 KB0 KB200application/javascriptScript
2341 ms2792 ms1 KB2 KB200application/javascriptScript
2012 ms2131 ms1 KB3 KB200text/cssStylesheet
2012 ms2466 ms1 KB2 KB200text/cssStylesheet
2486 ms2691 ms10 KB26 KB200text/htmlDocument
2487 ms2659 ms10 KB26 KB200text/htmlDocument
2487 ms2713 ms105 KB105 KB200image/jpegImage
2669 ms2693 ms44 KB293 KB200text/cssStylesheet
2669 ms2676 ms40 KB110 KB200text/javascriptScript
2669 ms2700 ms402 KB1219 KB200text/javascriptScript
2728 ms2728 ms44 KB293 KB200text/cssStylesheet
2728 ms2728 ms40 KB110 KB200text/javascriptScript
2728 ms2755 ms401 KB1219 KB200text/javascriptScript
2836 ms2897 ms1 KB0 KB302text/html
2839 ms2842 ms1 KB0 KB200text/javascriptScript
2890 ms2895 ms2 KB0 KB200application/jsonXHR
2892 ms2896 ms1 KB0 KB200text/javascriptScript
2836 ms2897 ms1 KB0 KB302text/htmlXHR
2897 ms2903 ms1 KB0 KB200application/jsonXHR
2913 ms2918 ms18 KB44 KB200text/javascriptScript
2961 ms2964 ms1 KB0 KB200image/gifImage,0.000:ER&cmt=0.000:0.000,0.000:0.000&error=0.000:html5.missingapi:0.000:nocodecs.1&vis=0.000:0&bh=0.000:0.000
3154 ms3316 ms0 KB0 KB-1Other
3224 ms3228 ms7 KB21 KB200text/javascriptScript,0.000:ER&cmt=0.000:0.000,0.000:0.000&error=0.000:html5.missingapi:0.000:nocodecs.1&vis=0.000:0&bh=0.000:0.000
3262 ms3318 ms0 KB0 KB-1Other
3312 ms3324 ms7 KB21 KB200text/javascriptScript
3314 ms3314 ms0 KB0 KB200image/pngImage
3329 ms3344 ms59 KB59 KB200image/pngImage
3331 ms3334 ms15 KB20 KB200font/ttfFont
3345 ms3348 ms15 KB20 KB200font/ttfFont
Serve static assets with an efficient cache policy - 18 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
900000 ms1 KB
900000 ms1 KB
7200000 ms18 KB
691200000 ms402 KB
691200000 ms401 KB
691200000 ms40 KB
691200000 ms40 KB
691200000 ms7 KB
691200000 ms7 KB
2592000000 ms33 KB
2592000000 ms3 KB
2592000000 ms2 KB
2592000000 ms1 KB
2592000000 ms1 KB
2592000000 ms1 KB
2592000000 ms1 KB
2592000000 ms1 KB
2592000000 ms1 KB
Reduce the impact of third-party code - Third-party code blocked the main thread for 860 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. Learn more.

SizeMain-Thread Blocking Time
1064 KB855 ms
19 KB7 ms
7 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1539 ms
7 ms
2483 ms
19 ms
2502 ms
19 ms
2526 ms
12 ms
2709 ms
7 ms
2722 ms
10 ms
2734 ms
10 ms
2744 ms
29 ms
2779 ms
9 ms
2789 ms
71 ms
2861 ms
51 ms
2915 ms
25 ms
2951 ms
7 ms
2961 ms
17 ms
3123 ms
119 ms
3241 ms
88 ms
3337 ms
11 ms
3352 ms
10 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
3 ms
3 ms
Reduce JavaScript execution time - 1.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
965 ms860 ms49 ms
692 ms28 ms10 ms
482 ms242 ms223 ms
93 ms63 ms10 ms
65 ms61 ms4 ms
53 ms50 ms1 ms
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. Learn more.

Avoid chaining critical requests - 9 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. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Reduce server response times (TTFB) - Root document took 700 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

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

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. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 72.6KiB (23% reduction).

Compressing could save 40.2KiB (22% reduction).
Compressing could save 11.3KiB (46% reduction).
Compressing could save 10.6KiB (12% reduction).
Compressing could save 10.5KiB (66% reduction).

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources: (15 minutes)******ytics.js (2 hours)

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 1.7KiB (22% reduction).

Minifying could save 627B (24% reduction) after compression.
Minifying could save 344B (18% reduction) after compression.
Minifying could save 271B (27% reduction) after compression.
Minifying could save 238B (24% reduction) after compression.
Minifying could save 144B (21% reduction) after compression.
Minifying could save 132B (16% reduction) after compression.

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://www.fac…a.izvor.lisine"></a> is close to 1 other tap targets.

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 417B (12% reduction).

Minifying could save 417B (12% reduction) after compression.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 335B (41% reduction).

Minifying could save 335B (41% reduction) after compression.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? use gzip compression.
Original size: 11.32 KB
Compressed size: 3.61 KB
File reduced by: 7.71 KB (68%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify supports HTTPS
Verifying SSL Support. Please wait...
Common Name:
Issuer: Let's Encrypt Authority X3
Valid from: Jan 18 23:47:56 2020 GMT
Valid until: Apr 17 23:47:56 2020 GMT

+ Verify HTTP/2 Support supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Sat, 15 Feb 2020 06:54:05 GMT
Server: Apache
Content-Length: 226
Content-Type: text/html; charset=iso-8859-1

HTTP/2 301 
date: Sat, 15 Feb 2020 06:54:05 GMT
server: Apache
cache-control: max-age=2592000
expires: Mon, 16 Mar 2020 06:54:05 GMT
content-length: 230
content-type: text/html; charset=iso-8859-1

HTTP/2 200 
date: Sat, 15 Feb 2020 06:54:06 GMT
server: Apache
vary: Accept-Encoding
content-encoding: gzip
content-type: text/html; charset=utf-8

+ DNS Lookup

Type Ip Target TTL
MX 3600
SOA 3600
Serial Number 2019120910
Refresh 28800
Retry 7200
Expire 1209600
Minimum TTL 0
A 3564
NS 3562
NS 3562

+ Whois Lookup

Domain Created:
Domain Age:

whois lookup at
%This is the RNIDS Whois server.
% Date Format : DD.MM.YYYY
% Whois Server Version: 1.0.0
% Rights restricted by copyright.
% See
% Ovo je odgovor od RNIDS Whois servera.
% Format datuma : DD.MM.YYYY
% Verzija Whois Servera : 1.0.0
% Sva prava zadržana. Za više informacija.
% pogledajte

Domain name:
Domain status: Active
Registration date: 25.08.2015 15:38:59
Modification date: 31.07.2019 11:09:36
Expiration date: 25.08.2020 15:38:59
Registrar: JP "Pošta Srbije"

DNS: -
DNS: -

Address: Despota Stefana Lazarevića 2, Despotovac, Serbia
ID Number: 17631179
Tax ID: 103909962

Administrative contact: Individual

Technical contact: Individual
Last update was 10 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget