Kramny.Cz - Info kramny.cz

kramny.cz receives about 34 unique visitors and 34 (1.00 per visitor) page views per day which should earn about $0.14/day from advertising revenue. Estimated site value is $64.21. According to Alexa Traffic Rank kramny.cz is ranked number 9,252,766 in the world and 2.0E-6% of global Internet users visit it. Site is hosted in Nymburk, Nymburk District, 288 02, Czechia and links to network IP address 185.73.160.5. This server doesn't support HTTPS and doesn't support HTTP/2.

About - kramny.cz

Bazar, opravy a servis motorů a stavebních strojů, vibrační desky, válce, elektrocentrály a kalová čerpadla.
Edit Site Info

Technologies used on Website

Currently Not Available

kramny.cz Profile

Title: Vibrační technika, stavební stroje, specializovaný servis | www.kramny.cz
Last update was 180 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is kramny.cz?

34 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
34
Monthly Unique Visitors:
816
Pages per Visit:
1.00
Daily Pageviews:
34
Alexa Rank:
9,252,766 visit alexa
Alexa Reach:
2.0E-6%   (of global internet users)
Avg. visit duration:
02:30
Bounce rate:
50.00%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
0%
Referral:
25.08%
Search:
74.92%
Social:
0%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
Russian Federation 53.7%--
Ukraine 29.6%--
Kazakhstan 6.2%--
Other 5.8%--
Belarus 2.3%--
India 0.7%--
Germany 0.6%--
United States 0.5%--
United Kingdom 0.5%--

Where do visitors go on this site?

Currently Not Available

Competitive Data

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

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is kramny.cz?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

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

Desktop summary

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


Mobile summary

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

+ Abusive Experience Report

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

+ How much kramny.cz can earn?

Daily Revenue:
$0.14
Monthly Revenue:
$4.20
Yearly Revenue:
$51.10
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Russian Federation 18$0.04
Ukraine 10$0.01
United States 0$0.00
Kazakhstan 2$0.00
Belarus 1$0.00
United Kingdom 0$0.00
Germany 0$0.00
India 0$0.00
Other 2$0.00

How much money do kramny.cz lose due to Adblock?

Daily Revenue Loss:
$0.01
Monthly Revenue Loss:
$0.15
Yearly Revenue Loss:
$1.85
Daily Pageviews Blocked:
3
Monthly Pageviews Blocked:
82
Yearly Pageviews Blocked:
996
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Russian Federation 1$0.00
Ukraine 1$0.00
United States 0$0.00
Germany 0$0.00
United Kingdom 0$0.00
India 0$0.00
Belarus 0$0.00
Kazakhstan 0$0.00
Other 0$0.00

How much is kramny.cz worth?

Website Value:
$64.21

+ Where is kramny.cz hosted?

Server IP:
185.73.160.5
ASN:
AS12570 
ISP:
itself s.r.o. 
Server Location:
Nymburk
Nymburk District, 208
288 02
Czechia, CZ
 

Other sites hosted on 185.73.160.5

+ How fast does kramny.cz load?

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

Page Speed (Google PageSpeed Insights) - Desktop

100
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

First Meaningful Paint 0.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 40 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 0.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
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. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 0.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.4 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 0.4 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.

Screenshot Thumbnails

This is what the load of your site looked like.

Keep request counts low and transfer sizes small - 19 requests • 387 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
19387 KB
Image
13346 KB
Script
333 KB
Document
14 KB
Stylesheet
24 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
218 KB
Eliminate render-blocking resources - Potential savings of 290 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.

URL
SizePotential Savings
http://kramny.cz/css/styly.css
3 KB70
http://kramny.cz/css/lytebox.js
8 KB110
http://kramny.cz/css/lytebox2.js
8 KB110
http://kramny.cz/css/lytebox.css
1 KB110
Efficiently encode images - Potential savings of 101 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://kramny.cz/images/podklad.jpg
124 KB74 KB
http://kramny.cz/images/obr222.jpg
34 KB21 KB
http://kramny.cz/images/telefon.jpg
14 KB7 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://kramny.cz/
0 ms122 ms4 KB10 KB200text/htmlDocument
http://kramny.cz/css/styly.css
138 ms357 ms3 KB10 KB200text/cssStylesheet
http://kramny.cz/css/lytebox.js
139 ms252 ms8 KB39 KB200application/javascriptScript
http://kramny.cz/css/lytebox2.js
139 ms359 ms8 KB39 KB200application/javascriptScript
http://kramny.cz/css/lytebox.css
140 ms357 ms1 KB2 KB200text/cssStylesheet
http://kramny.cz/images/cz.gif
140 ms250 ms1 KB1 KB200image/gifImage
http://kramny.cz/images/en.gif
140 ms357 ms1 KB1 KB200image/gifImage
http://kramny.cz/obr.php?oc=542&tabulka=katalog&obr=obr
252 ms797 ms120 KB119 KB200image/pjpgImage
http://kramny.cz/images/sipka_mala.gif
358 ms469 ms0 KB0 KB200image/gifImage
http://kramny.cz/images/amman1.png
369 ms481 ms8 KB8 KB200image/pngImage
http://kramny.cz/images/amman2.png
369 ms481 ms11 KB10 KB200image/pngImage
http://kramny.cz/images/amman4.png
369 ms706 ms15 KB14 KB200image/pngImage
http://kramny.cz/images/amman3.png
369 ms699 ms17 KB17 KB200image/pngImage
http://kramny.cz/images/obr222.jpg
369 ms791 ms35 KB34 KB200image/jpegImage
http://www.google-analytics.com/ga.js
370 ms376 ms17 KB45 KB200text/javascriptScript
http://kramny.cz/images/carka.jpg
372 ms591 ms1 KB0 KB200image/jpegImage
http://kramny.cz/images/podklad.jpg
373 ms910 ms124 KB124 KB200image/jpegImage
http://kramny.cz/images/telefon.jpg
376 ms808 ms14 KB14 KB200image/jpegImage
http://www.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=1837741794&utmhn=kramny.cz&utmcs=windows-1250&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Vibra%C4%8Dn%C3%AD%20technika%2C%20stavebn%C3%AD%20stroje%2C%20specializovan%C3%BD%20servis%20%7C%20www.kramny.cz&utmhid=1993116763&utmr=-&utmp=%2F&utmht=1569844058323&utmac=UA-19165978-2&utmcc=__utma%3D87240386.112987301.1569844058.1569844058.1569844058.1%3B%2B__utmz%3D87240386.1569844058.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=1779323942&utmredir=1&utmu=qAAAAAAAAAAAAAAAAAAAAAAE~
453 ms460 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 17 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://kramny.cz/images/podklad.jpg
0 ms124 KB
http://kramny.cz/obr.php?oc=542&tabulka=katalog&obr=obr
0 ms120 KB
http://kramny.cz/images/obr222.jpg
0 ms35 KB
http://kramny.cz/images/amman3.png
0 ms17 KB
http://kramny.cz/images/amman4.png
0 ms15 KB
http://kramny.cz/images/telefon.jpg
0 ms14 KB
http://kramny.cz/images/amman2.png
0 ms11 KB
http://kramny.cz/images/amman1.png
0 ms8 KB
http://kramny.cz/css/lytebox2.js
0 ms8 KB
http://kramny.cz/css/lytebox.js
0 ms8 KB
http://kramny.cz/css/styly.css
0 ms3 KB
http://kramny.cz/images/en.gif
0 ms1 KB
http://kramny.cz/css/lytebox.css
0 ms1 KB
http://kramny.cz/images/cz.gif
0 ms1 KB
http://kramny.cz/images/carka.jpg
0 ms1 KB
http://kramny.cz/images/sipka_mala.gif
0 ms0 KB
http://www.google-analytics.com/ga.js
7200000 ms17 KB
Third-Party Usage - 1 Third-Party Found
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.

Third-Party
SizeMain Thread Time
18 KB38 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
152 ms
11 ms
391 ms
20 ms
411 ms
29 ms
442 ms
38 ms
939 ms
30 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
106 ms3 ms1 ms
Properly size images - Potential savings of 117 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
http://kramny.cz/obr.php?oc=542&tabulka=katalog&obr=obr
119 KB117 KB
Avoids enormous network payloads - Total size was 387 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://kramny.cz/images/podklad.jpg
124 KB
http://kramny.cz/obr.php?oc=542&tabulka=katalog&obr=obr
120 KB
http://kramny.cz/images/obr222.jpg
35 KB
http://www.google-analytics.com/ga.js
17 KB
http://kramny.cz/images/amman3.png
17 KB
http://kramny.cz/images/amman4.png
15 KB
http://kramny.cz/images/telefon.jpg
14 KB
http://kramny.cz/images/amman2.png
11 KB
http://kramny.cz/images/amman1.png
8 KB
http://kramny.cz/css/lytebox2.js
8 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Script Evaluation
63 ms
Other
42 ms
Style & Layout
39 ms
Rendering
12 ms
Script Parsing & Compilation
11 ms
Parse HTML & CSS
9 ms
Serve images in next-gen formats - Potential savings of 173 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.

URL
SizePotential Savings
http://kramny.cz/images/podklad.jpg
124 KB100 KB
http://kramny.cz/images/obr222.jpg
34 KB27 KB
http://kramny.cz/images/amman3.png
17 KB14 KB
http://kramny.cz/images/amman4.png
14 KB12 KB
http://kramny.cz/images/telefon.jpg
14 KB11 KB
http://kramny.cz/images/amman2.png
10 KB8 KB
Avoids an excessive DOM size - 177 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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). Learn more.

Statistic
ElementValue
Total DOM Elements
177
Maximum DOM Depth
10
Maximum Child Elements
18
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. 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.

Server response times are low (TTFB) - Root document took 120 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.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. 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.

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.

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

Remove unused CSS
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.

Minimize Critical Requests Depth - 4 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.


Page Speed (Google PageSpeed Insights) - Mobile

100
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

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. Learn more.
Total Blocking Time 110 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 2446 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.6 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 1.3 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 1.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 190 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 1.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

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

URL
Total CPU TimeScript EvaluationScript Parse
Other
568 ms14 ms4 ms
http://www.google-analytics.com/ga.js
181 ms159 ms23 ms
http://kramny.cz/css/lytebox2.js
66 ms52 ms12 ms
http://kramny.cz/css/lytebox.js
62 ms49 ms10 ms
Properly size images - Potential savings of 105 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
http://kramny.cz/obr.php?oc=542&tabulka=katalog&obr=obr
119 KB105 KB
Avoids enormous network payloads - Total size was 387 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://kramny.cz/images/podklad.jpg
124 KB
http://kramny.cz/obr.php?oc=542&tabulka=katalog&obr=obr
120 KB
http://kramny.cz/images/obr222.jpg
35 KB
http://www.google-analytics.com/ga.js
17 KB
http://kramny.cz/images/amman3.png
17 KB
http://kramny.cz/images/amman4.png
15 KB
http://kramny.cz/images/telefon.jpg
14 KB
http://kramny.cz/images/amman2.png
11 KB
http://kramny.cz/images/amman1.png
8 KB
http://kramny.cz/css/lytebox2.js
8 KB
Minimizes main-thread work - 0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Script Evaluation
278 ms
Style & Layout
245 ms
Other
229 ms
Script Parsing & Compilation
50 ms
Rendering
46 ms
Parse HTML & CSS
34 ms
Serve images in next-gen formats - Potential savings of 173 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.

URL
SizePotential Savings
http://kramny.cz/images/podklad.jpg
124 KB100 KB
http://kramny.cz/images/obr222.jpg
34 KB27 KB
http://kramny.cz/images/amman3.png
17 KB14 KB
http://kramny.cz/images/amman4.png
14 KB12 KB
http://kramny.cz/images/telefon.jpg
14 KB11 KB
http://kramny.cz/images/amman2.png
10 KB8 KB
Avoids an excessive DOM size - 177 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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). Learn more.

Statistic
ElementValue
Total DOM Elements
177
Maximum DOM Depth
10
Maximum Child Elements
18
Keep request counts low and transfer sizes small - 19 requests • 387 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
19387 KB
Image
13346 KB
Script
333 KB
Document
14 KB
Stylesheet
24 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
218 KB
Eliminate render-blocking resources - Potential savings of 710 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.

URL
SizePotential Savings
http://kramny.cz/css/styly.css
3 KB180
http://kramny.cz/css/lytebox.js
8 KB480
http://kramny.cz/css/lytebox2.js
8 KB480
http://kramny.cz/css/lytebox.css
1 KB330
Efficiently encode images - Potential savings of 101 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://kramny.cz/images/podklad.jpg
124 KB74 KB
http://kramny.cz/images/obr222.jpg
34 KB21 KB
http://kramny.cz/images/telefon.jpg
14 KB7 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://kramny.cz/
0 ms315 ms4 KB10 KB200text/htmlDocument
http://kramny.cz/css/styly.css
345 ms458 ms3 KB10 KB200text/cssStylesheet
http://kramny.cz/css/lytebox.js
345 ms669 ms8 KB39 KB200application/javascriptScript
http://kramny.cz/css/lytebox2.js
346 ms567 ms8 KB39 KB200application/javascriptScript
http://kramny.cz/css/lytebox.css
346 ms459 ms1 KB2 KB200text/cssStylesheet
http://kramny.cz/images/cz.gif
347 ms566 ms1 KB1 KB200image/gifImage
http://kramny.cz/images/en.gif
347 ms569 ms1 KB1 KB200image/gifImage
http://kramny.cz/obr.php?oc=542&tabulka=katalog&obr=obr
567 ms1109 ms120 KB119 KB200image/pjpgImage
http://kramny.cz/images/sipka_mala.gif
570 ms787 ms0 KB0 KB200image/gifImage
http://kramny.cz/images/amman1.png
678 ms792 ms8 KB8 KB200image/pngImage
http://kramny.cz/images/amman2.png
679 ms793 ms11 KB10 KB200image/pngImage
http://kramny.cz/images/amman4.png
679 ms899 ms15 KB14 KB200image/pngImage
http://kramny.cz/images/amman3.png
679 ms902 ms17 KB17 KB200image/pngImage
http://kramny.cz/images/obr222.jpg
679 ms1110 ms35 KB34 KB200image/jpegImage
http://www.google-analytics.com/ga.js
679 ms686 ms17 KB45 KB200text/javascriptScript
http://kramny.cz/images/carka.jpg
682 ms902 ms1 KB0 KB200image/jpegImage
http://kramny.cz/images/podklad.jpg
683 ms1331 ms124 KB124 KB200image/jpegImage
http://kramny.cz/images/telefon.jpg
687 ms1226 ms14 KB14 KB200image/jpegImage
http://www.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=1873730412&utmhn=kramny.cz&utmcs=windows-1250&utmsr=412x660&utmvp=980x1569&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Vibra%C4%8Dn%C3%AD%20technika%2C%20stavebn%C3%AD%20stroje%2C%20specializovan%C3%BD%20servis%20%7C%20www.kramny.cz&utmhid=589162245&utmr=-&utmp=%2F&utmht=1569844052578&utmac=UA-19165978-2&utmcc=__utma%3D87240386.207302561.1569844053.1569844053.1569844053.1%3B%2B__utmz%3D87240386.1569844053.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=2062361267&utmredir=1&utmu=qAAAAAAAAAAAAAAAAAAAAAAE~
794 ms800 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 17 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://kramny.cz/images/podklad.jpg
0 ms124 KB
http://kramny.cz/obr.php?oc=542&tabulka=katalog&obr=obr
0 ms120 KB
http://kramny.cz/images/obr222.jpg
0 ms35 KB
http://kramny.cz/images/amman3.png
0 ms17 KB
http://kramny.cz/images/amman4.png
0 ms15 KB
http://kramny.cz/images/telefon.jpg
0 ms14 KB
http://kramny.cz/images/amman2.png
0 ms11 KB
http://kramny.cz/images/amman1.png
0 ms8 KB
http://kramny.cz/css/lytebox2.js
0 ms8 KB
http://kramny.cz/css/lytebox.js
0 ms8 KB
http://kramny.cz/css/styly.css
0 ms3 KB
http://kramny.cz/images/en.gif
0 ms1 KB
http://kramny.cz/css/lytebox.css
0 ms1 KB
http://kramny.cz/images/cz.gif
0 ms1 KB
http://kramny.cz/images/carka.jpg
0 ms1 KB
http://kramny.cz/images/sipka_mala.gif
0 ms0 KB
http://www.google-analytics.com/ga.js
7200000 ms17 KB
Third-Party Usage - 1 Third-Party Found
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.

Third-Party
SizeMain Thread Time
18 KB181 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
350 ms
23 ms
704 ms
23 ms
727 ms
49 ms
778 ms
48 ms
1363 ms
30 ms
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.

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.

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

Remove unused CSS
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.

Minimize Critical Requests Depth - 4 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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. 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.

Server response times are low (TTFB) - Root document took 320 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.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

úvodní stránka and 2 others render only 5 pixels tall (13 CSS pixels) .
| and 1 others render only 5 pixels tall (13 CSS pixels) .
Vibrační techn…ýroba vysavačů renders only 7 pixels tall (17 CSS pixels) .
Vítejte na str…atz, Farymann. renders only 5 pixels tall (13 CSS pixels) .
Vyvíjíme a vyr…me komunální a and 1 others render only 5 pixels tall (13 CSS pixels) .
průmyslové vysavače renders only 5 pixels tall (13 CSS pixels) .
- komunální vy…novým filtrem. renders only 5 pixels tall (13 CSS pixels) .
Firma Kamil Kr…OPAVA nabízí: and 1 others render only 5 pixels tall (14 CSS pixels) .
Levná profesio…pro řemeslníky and 6 others render only 5 pixels tall (13 CSS pixels) .
Výkup a prodej…ní mechanizace and 4 others render only 5 pixels tall (13 CSS pixels) .
bourací techni…brační latě... and 4 others render only 5 pixels tall (13 CSS pixels) .
Našim nejprodá…rační technika renders only 5 pixels tall (14 CSS pixels) .
V prodeji malé…ojů na světě). and 1 others render only 5 pixels tall (13 CSS pixels) .
Pro obchodní a…mného na tel.: renders only 5 pixels tall (13 CSS pixels) .
Zdroje informací: and 2 others render only 5 pixels tall (13 CSS pixels) .
E-mail: renders only 5 pixels tall (14 CSS pixels) .
kramny@kramny.cz renders only 5 pixels tall (14 CSS pixels) .
Průmyslový vysavač prachu and 9 others render only 5 pixels tall (13 CSS pixels) .
Ocelová svodidla Fracasso and 12 others render only 5 pixels tall (13 CSS pixels) .
Copyright © 20…Kamil Kramný | and 1 others render only 3 pixels tall (9 CSS pixels) .
webREGIONAL and 1 others render only 3 pixels tall (9 CSS pixels) .

Optimize images

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

Optimize the following images to reduce their size by 233.8KiB (79% reduction).

Compressing and resizing http://kramny.cz/obr.php?oc=542&tabulka=katalog&obr=obr could save 115.4KiB (96% reduction).
Compressing http://kramny.cz/images/podklad.jpg could save 86.5KiB (***% reduction).
Compressing http://kramny.cz/images/obr222.jpg could save 23.7KiB (***% reduction).
Compressing http://kramny.cz/images/telefon.jpg could save 7.8KiB (57% reduction).
Compressing http://kramny.cz/images/en.gif could save 240B (22% reduction).
Compressing http://kramny.cz/images/cz.gif could save 131B (23% reduction).

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

Your page has 2 blocking script resources and 2 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:

http://kramny.cz/css/lytebox.js
http://kramny.cz/css/lytebox2.js
Optimize CSS Delivery of the following:

http://kramny.cz/css/styly.css
http://kramny.cz/css/lytebox.css

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:

http://kramny.cz/css/lytebox.css (expiration not specified)
http://kramny.cz/css/lytebox.js (expiration not specified)
http://kramny.cz/css/lytebox2.js (expiration not specified)
http://kramny.cz/css/styly.css (expiration not specified)
http://kramny.cz/images/amman1.png (expiration not specified)
http://kramny.cz/images/amman2.png (expiration not specified)
http://kramny.cz/images/amman3.png (expiration not specified)
http://kramny.cz/images/amman4.png (expiration not specified)
http://kramny.cz/images/carka.jpg (expiration not specified)
http://kramny.cz/images/cz.gif (expiration not specified)
http://kramny.cz/images/en.gif (expiration not specified)
http://kramny.cz/images/obr222.jpg (expiration not specified)
http://kramny.cz/images/podklad.jpg (expiration not specified)
http://kramny.cz/images/sipka_mala.gif (expiration not specified)
http://kramny.cz/images/telefon.jpg (expiration not specified)
http://www.google-***ytics.com/ga.js (2 hours)

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

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="/"></a> and 1 others are close to other tap targets .
The tap target <a href="/" class="link_hlavicka">úvodní stránka</a> and 1 others are close to other tap targets .
The tap target <input type="submit"> is close to 1 other tap targets .
The tap target <a href="/">Hlavní stránka</a> and 9 others are close to other tap targets .
The tap target <a href="http://www.kom…ni-vysavace.cz" class="zdroj">Komunální vysavače</a> and 12 others are close to other tap targets .
The tap target <a href="/asplus/" class="bila">AS++</a> is close to 1 other tap targets .

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 3.6KiB (25% reduction).

Minifying http://kramny.cz/css/lytebox.js could save 1.8KiB (25% reduction) after compression.
Minifying http://kramny.cz/css/lytebox2.js could save 1.8KiB (25% reduction) after compression.

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 289B (13% reduction).

Minifying http://kramny.cz/css/styly.css could save 289B (13% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
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.
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.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
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.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does kramny.cz use compression?

kramny.cz use gzip compression.
Original size: 10.05 KB
Compressed size: 3.46 KB
File reduced by: 6.59 KB (65%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  60
Vendor reliability:
  60
Privacy:
  60
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

kramny.cz does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

kramny.cz does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Průmyslová výroba a služby/Stroje a nástroje

+ Http Header

Date: Mon, 30 Sep 2019 11:47:21 GMT
Server: Apache/2.2.22 (Ubuntu)
X-Powered-By: PHP/5.3.10-1ubuntu3.26
Set-Cookie: PHPSESSID=cvatfmuu4o8cahs6hg2ideebk4; path=/
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
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 3546
Content-Type: text/html

+ DNS Lookup

Type Ip Target TTL
MX email.regional.cz 3600
A 185.73.160.5 3600
SOA 3600
Mname alfa.ns.active24.cz
Rname hostmaster.active24.cz
Serial Number 2018011007
Refresh 10800
Retry 1800
Expire 1209600
Minimum TTL 0
NS gama.ns.active24.sk 3576
NS beta.ns.active24.cz 3576
NS alfa.ns.active24.cz 3576

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.nic.cz...
% (c) 2006-2019 CZ.NIC, z.s.p.o.
%
% Intended use of supplied data and information
%
% Data contained in the domain name register, as well as information
% supplied through public information services of CZ.NIC association,
% are appointed only for purposes connected with Internet network
% administration and operation, or for the purpose of legal or other
% similar proceedings, in process as regards a matter connected
% particularly with holding and using a concrete domain name.
%
% Full text available at:
% http://www.nic.cz/page/306/intended-use-of-supplied-data-and-information/
%
% See also a search service at http://www.nic.cz/whois/
%
%
% Whoisd Server Version: 3.12.0
% Timestamp: Mon Sep 30 13:47:42 2019

domain: kramny.cz
registrant: A24CONTACT-18005143834
admin-c: PESCZ60002851
nsset: NSS:GLOBE-SGLO000001:1
registrar: REG-ACTIVE24
registered: 10.07.2001 14:31:00
changed: 10.01.2018 17:18:52
expire: 10.07.2020

contact: A24CONTACT-18005143834
name: Kamil Kramny
address: Nové domky 222
address: Dolní Životice
address: 747 56
address: CZ
registrar: REG-ACTIVE24
created: 05.01.2018 14:40:48
changed: 15.05.2018 21:32:00

contact: PESCZ60002851
name: Pavel Bilik
address: B.Nemcove 17
address: Opava
address: 746 01
address: CZ
registrar: REG-INTERNET-CZ
created: 10.08.2001 22:13:00
changed: 15.05.2018 21:32:00

nsset: NSS:GLOBE-SGLO000001:1
nserver: beta.ns.active24.cz (81.0.238.27, 2001:1528:151::12)
nserver: gama.ns.active24.sk
nserver: alfa.ns.active24.cz (81.95.96.2, 2a02:4a8:ac24:100::96:2)
tech-c: ACTIVE24
registrar: REG-ACTIVE24
created: 01.10.2007 02:00:00
changed: 19.07.2011 15:27:33

contact: ACTIVE24
org: ACTIVE 24, s.r.o.
name: ACTIVE 24, s.r.o.
address: Sokolovská 394/17
address: Praha 8
address: 186 00
address: CZ
registrar: REG-ACTIVE24
created: 29.04.2008 12:35:02
changed: 15.05.2018 21:32:00
Last update was 180 days ago
loader
This can take up to 60 seconds. Please wait...

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

BrowserExtension

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) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
kramny.cz widget