Weltauto.Mk - Info weltauto.mk

weltauto.mk receives about 170 unique visitors and 2,545 (15.00 per visitor) page views per day which should earn about $2.70/day from advertising revenue. Estimated site value is $1,201.43. According to Alexa Traffic Rank weltauto.mk is ranked number 1,952,737 in the world and 1.0E-5% of global Internet users visit it. Site is hosted in Bulgaria and links to network IP address 79.124.90.105. This server doesn't support HTTPS and doesn't support HTTP/2.

About - weltauto.mk


Technologies used on Website

Web Servers
Apache
Operating Systems
FreeBSD
Web Server Extensions
OpenSSL
mod_dav
mod_ssl
Programming Languages
PHP
Miscellaneous
SWFObject

weltauto.mk Profile

Title: Користени Возила од Порше Македонија
Last update was 152 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is weltauto.mk?

170 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
170
Monthly Unique Visitors:
4,080
Pages per Visit:
15.00
Daily Pageviews:
2,545
Alexa Rank:
1,952,737 visit alexa
Alexa Reach:
1.0E-5%   (of global internet users)
Avg. visit duration:
04:39
Bounce rate:
12.86%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
39.92%
Referral:
34.33%
Search:
25.74%
Social:
0%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
Macedonia 100.0%100.0%2073

Where do visitors go on this site?

Reach%Pageviews%PerUser
weltauto.mk
100.00%100.00%20

Competitive Data

SEMrush
Domain:
  weltauto.mk
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 weltauto.mk?

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:
weltauto.mk
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:
weltauto.mk
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 weltauto.mk can earn?

Daily Revenue:
$2.70
Monthly Revenue:
$81.00
Yearly Revenue:
$985.50
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Macedonia 2,545$2.70

How much money do weltauto.mk lose due to Adblock?

Daily Revenue Loss:
$0.43
Monthly Revenue Loss:
$12.95
Yearly Revenue Loss:
$157.55
Daily Pageviews Blocked:
407
Monthly Pageviews Blocked:
12,216
Yearly Pageviews Blocked:
148,628
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Macedonia 407$0.43

How much is weltauto.mk worth?

Website Value:
$1,201.43

+ Where is weltauto.mk hosted?

Server IP:
79.124.90.105
ASN:
AS31083 
ISP:
Telepoint Ltd 
Server Location:

Bulgaria, BG
 

Other sites hosted on 79.124.90.105

+ How fast does weltauto.mk load?

Average Load Time:
(295 ms) 99 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE 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.

First Contentful Paint (FCP)1.4s 79% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 79% 16% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 16% 4% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 4%
First Input Delay (FID)3ms 100% of loads for this page have a fast (<50ms) First Input Delay (FID) 100% 0% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an FAST 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.

First Contentful Paint (FCP)688ms 94% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 94% 4% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 4% 0% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 0%
First Input Delay (FID)3ms 99% of loads for this page have a fast (<50ms) First Input Delay (FID) 99% 0% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 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.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
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.
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.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.5 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.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 247 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
247
Maximum DOM Depth
20
Maximum Child Elements
33
Keep request counts low and transfer sizes small - 29 requests • 202 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
29202 KB
Image
21106 KB
Script
366 KB
Stylesheet
214 KB
Document
114 KB
Other
21 KB
Media
00 KB
Font
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 310 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://weltauto.mk/main.css
13 KB110
http://weltauto.mk/js/jquery-1.3.2.min.js
56 KB230
http://weltauto.mk/swfobject.js
7 KB110
http://weltauto.mk/prettyCheckboxes.css
1 KB110
Enable text compression - Potential savings of 64 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://weltauto.mk/js/jquery-1.3.2.min.js
56 KB37 KB
http://weltauto.mk/main.css
13 KB11 KB
http://weltauto.mk/
14 KB10 KB
http://weltauto.mk/swfobject.js
7 KB5 KB
http://weltauto.mk/js/prettyCheckboxes.js
2 KB1 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://weltauto.mk/
0 ms259 ms14 KB14 KB200text/htmlDocument
http://weltauto.mk/main.css
273 ms403 ms13 KB13 KB200text/cssStylesheet
http://weltauto.mk/js/jquery-1.3.2.min.js
273 ms908 ms56 KB56 KB200application/javascriptScript
http://weltauto.mk/swfobject.js
274 ms654 ms7 KB7 KB200application/javascriptScript
http://weltauto.mk/images/logo.jpg
274 ms655 ms9 KB9 KB200image/jpegImage
http://weltauto.mk/images/logo2.jpg
274 ms655 ms8 KB8 KB200image/jpegImage
http://weltauto.mk/images/logo-vw.jpg
656 ms920 ms3 KB3 KB200image/jpegImage
http://weltauto.mk/images/logo-skoda.jpg
787 ms917 ms5 KB5 KB200image/jpegImage
http://weltauto.mk/images/logo-audi.jpg
926 ms1067 ms3 KB3 KB200image/jpegImage
http://weltauto.mk/images/logo-vwn.jpg
926 ms1055 ms5 KB5 KB200image/jpegImage
http://weltauto.mk/js/prettyCheckboxes.js
656 ms786 ms3 KB2 KB200application/javascriptScript
http://weltauto.mk/prettyCheckboxes.css
275 ms529 ms1 KB1 KB200text/cssStylesheet
http://weltauto.mk/images/home-vw.jpg
928 ms1058 ms2 KB2 KB200image/jpegImage
http://weltauto.mk/images/home-skoda.jpg
928 ms1066 ms3 KB3 KB200image/jpegImage
http://weltauto.mk/images/home-audi.jpg
928 ms1059 ms2 KB2 KB200image/jpegImage
http://weltauto.mk/images/home-vwn.jpg
928 ms1058 ms3 KB3 KB200image/jpegImage
http://weltauto.mk/?go=_common&p=banner&bannerId=35&1569173124
928 ms1204 ms10 KB9 KB200text/htmlImage
http://weltauto.mk/?go=_common&p=banner&bannerId=38&1569173124
928 ms1196 ms11 KB10 KB200text/htmlImage
http://weltauto.mk/?go=_common&p=banner&bannerId=39&1569173124
929 ms1201 ms12 KB11 KB200text/htmlImage
http://weltauto.mk/?go=_common&p=banner&bannerId=40&1569173124
929 ms1209 ms12 KB11 KB200text/htmlImage
http://weltauto.mk/?go=_common&p=banner&bannerId=41&1569173124
929 ms1213 ms11 KB11 KB200text/htmlImage
http://weltauto.mk/images/bullet_blue.gif
929 ms1318 ms0 KB0 KB200image/gifImage
http://weltauto.mk/images/home-search-button.jpg
929 ms1325 ms2 KB1 KB200image/jpegImage
http://weltauto.mk/images/header.jpg
931 ms1454 ms1 KB1 KB200image/jpegImage
http://weltauto.mk/images/bullet.gif
931 ms1342 ms0 KB0 KB200image/gifImage
http://weltauto.mk/images/home-search-bg.jpg
952 ms1343 ms1 KB0 KB200image/jpegImage
http://weltauto.mk/?h=homeModels
963 ms1191 ms1 KB0 KB200text/htmlXHR
http://weltauto.mk/images/prettyCheckboxes/checkbox.gif
984 ms1453 ms2 KB1 KB200image/gifImage
http://weltauto.mk/?h=firstResults&brandId=0&modelId=0&priceTo=0&yearTo=0&fuelId=0&cityId=0&check1=false&check2=false
1201 ms1477 ms0 KB0 KB200text/htmlXHR
Serve static assets with an efficient cache policy - 21 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://weltauto.mk/js/jquery-1.3.2.min.js
0 ms56 KB
http://weltauto.mk/main.css
0 ms13 KB
http://weltauto.mk/images/logo.jpg
0 ms9 KB
http://weltauto.mk/images/logo2.jpg
0 ms8 KB
http://weltauto.mk/swfobject.js
0 ms7 KB
http://weltauto.mk/images/logo-vwn.jpg
0 ms5 KB
http://weltauto.mk/images/logo-skoda.jpg
0 ms5 KB
http://weltauto.mk/images/home-vwn.jpg
0 ms3 KB
http://weltauto.mk/images/home-skoda.jpg
0 ms3 KB
http://weltauto.mk/images/logo-vw.jpg
0 ms3 KB
http://weltauto.mk/images/logo-audi.jpg
0 ms3 KB
http://weltauto.mk/js/prettyCheckboxes.js
0 ms3 KB
http://weltauto.mk/images/home-audi.jpg
0 ms2 KB
http://weltauto.mk/images/home-vw.jpg
0 ms2 KB
http://weltauto.mk/images/home-search-button.jpg
0 ms2 KB
http://weltauto.mk/images/prettyCheckboxes/checkbox.gif
0 ms2 KB
http://weltauto.mk/prettyCheckboxes.css
0 ms1 KB
http://weltauto.mk/images/header.jpg
0 ms1 KB
http://weltauto.mk/images/home-search-bg.jpg
0 ms1 KB
http://weltauto.mk/images/bullet_blue.gif
0 ms0 KB
http://weltauto.mk/images/bullet.gif
0 ms0 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
288 ms
8 ms
938 ms
12 ms
956 ms
17 ms
976 ms
9 ms
985 ms
25 ms
1222 ms
6 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
102 ms3 ms1 ms
Remove unused CSS - Potential savings of 11 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.

URL
SizePotential Savings
http://weltauto.mk/main.css
13 KB11 KB
Avoids enormous network payloads - Total size was 202 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://weltauto.mk/js/jquery-1.3.2.min.js
56 KB
http://weltauto.mk/
14 KB
http://weltauto.mk/main.css
13 KB
http://weltauto.mk/?go=_common&p=banner&bannerId=39&1569173124
12 KB
http://weltauto.mk/?go=_common&p=banner&bannerId=40&1569173124
12 KB
http://weltauto.mk/?go=_common&p=banner&bannerId=41&1569173124
11 KB
http://weltauto.mk/?go=_common&p=banner&bannerId=38&1569173124
11 KB
http://weltauto.mk/?go=_common&p=banner&bannerId=35&1569173124
10 KB
http://weltauto.mk/images/logo.jpg
9 KB
http://weltauto.mk/images/logo2.jpg
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
Other
48 ms
Script Evaluation
39 ms
Style & Layout
35 ms
Rendering
15 ms
Parse HTML & CSS
11 ms
Script Parsing & Compilation
4 ms
Minimize Critical Requests Depth - 5 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 260 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. 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.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. 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.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Serve images in next-gen formats
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.


Page Speed (Google PageSpeed Insights) - Mobile

93
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW 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.

First Contentful Paint (FCP)1.3s 79% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 80% 17% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 17% 2% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 2%
First Input Delay (FID)274ms 0% of loads for this page have a fast (<50ms) First Input Delay (FID) 0% 78% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 78% 20% of loads for this page have a slow (>250ms) First Input Delay (FID) 20%

Origin Data

All pages served from this origin have an SLOW 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.

First Contentful Paint (FCP)733ms 95% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 95% 4% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 4% 0% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 0%
First Input Delay (FID)265ms 99% of loads for this page have a fast (<50ms) First Input Delay (FID) 16% 71% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 71% 12% of loads for this page have a slow (>250ms) First Input Delay (FID) 12%

Lab Data

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.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 30 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.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
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.
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.
First Contentful Paint (3G) 3566.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. 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 4.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.8 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.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 247 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
247
Maximum DOM Depth
20
Maximum Child Elements
33
Keep request counts low and transfer sizes small - 29 requests • 202 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
29202 KB
Image
21106 KB
Script
366 KB
Stylesheet
214 KB
Document
114 KB
Other
21 KB
Media
00 KB
Font
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 990 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://weltauto.mk/main.css
13 KB480
http://weltauto.mk/js/jquery-1.3.2.min.js
56 KB930
http://weltauto.mk/swfobject.js
7 KB480
http://weltauto.mk/prettyCheckboxes.css
1 KB330
Enable text compression - Potential savings of 64 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://weltauto.mk/js/jquery-1.3.2.min.js
56 KB37 KB
http://weltauto.mk/main.css
13 KB11 KB
http://weltauto.mk/
14 KB10 KB
http://weltauto.mk/swfobject.js
7 KB5 KB
http://weltauto.mk/js/prettyCheckboxes.js
2 KB1 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://weltauto.mk/
0 ms1012 ms14 KB14 KB200text/htmlDocument
http://weltauto.mk/main.css
1025 ms1905 ms13 KB13 KB200text/cssStylesheet
http://weltauto.mk/js/jquery-1.3.2.min.js
1025 ms2156 ms56 KB56 KB200application/javascriptScript
http://weltauto.mk/swfobject.js
1026 ms1944 ms7 KB7 KB200application/javascriptScript
http://weltauto.mk/images/logo.jpg
1026 ms1405 ms9 KB9 KB200image/jpegImage
http://weltauto.mk/images/logo2.jpg
1026 ms1918 ms8 KB8 KB200image/jpegImage
http://weltauto.mk/images/logo-vw.jpg
1538 ms1667 ms3 KB3 KB200image/jpegImage
http://weltauto.mk/images/logo-skoda.jpg
1668 ms1797 ms5 KB5 KB200image/jpegImage
http://weltauto.mk/images/logo-audi.jpg
1798 ms1928 ms3 KB3 KB200image/jpegImage
http://weltauto.mk/images/logo-vwn.jpg
1919 ms2049 ms5 KB5 KB200image/jpegImage
http://weltauto.mk/js/prettyCheckboxes.js
1407 ms1537 ms3 KB2 KB200application/javascriptScript
http://weltauto.mk/prettyCheckboxes.css
1027 ms1633 ms1 KB1 KB200text/cssStylesheet
http://weltauto.mk/images/home-vw.jpg
1929 ms2058 ms2 KB2 KB200image/jpegImage
http://weltauto.mk/images/home-skoda.jpg
2050 ms2203 ms3 KB3 KB200image/jpegImage
http://weltauto.mk/images/home-audi.jpg
2059 ms2188 ms2 KB2 KB200image/jpegImage
http://weltauto.mk/images/home-vwn.jpg
2174 ms2804 ms3 KB3 KB200image/jpegImage
http://weltauto.mk/?go=_common&p=banner&bannerId=35&1569173117
2174 ms2349 ms10 KB9 KB200text/htmlImage
http://weltauto.mk/?go=_common&p=banner&bannerId=38&1569173117
2174 ms2315 ms11 KB10 KB200text/htmlImage
http://weltauto.mk/?go=_common&p=banner&bannerId=39&1569173117
2174 ms2319 ms12 KB11 KB200text/htmlImage
http://weltauto.mk/?go=_common&p=banner&bannerId=40&1569173117
2175 ms2579 ms12 KB11 KB200text/htmlImage
http://weltauto.mk/?go=_common&p=banner&bannerId=41&1569173117
2175 ms2584 ms11 KB11 KB200text/htmlImage
http://weltauto.mk/images/bullet_blue.gif
2175 ms2447 ms0 KB0 KB200image/gifImage
http://weltauto.mk/images/home-search-button.jpg
2175 ms2498 ms2 KB1 KB200image/jpegImage
http://weltauto.mk/images/header.jpg
2176 ms2700 ms1 KB1 KB200image/jpegImage
http://weltauto.mk/images/bullet.gif
2177 ms2585 ms0 KB0 KB200image/gifImage
http://weltauto.mk/images/home-search-bg.jpg
2196 ms2714 ms1 KB0 KB200image/jpegImage
http://weltauto.mk/?h=homeModels
2206 ms2451 ms1 KB0 KB200text/htmlXHR
http://weltauto.mk/images/prettyCheckboxes/checkbox.gif
2224 ms2714 ms2 KB1 KB200image/gifImage
http://weltauto.mk/?h=firstResults&brandId=0&modelId=0&priceTo=0&yearTo=0&fuelId=0&cityId=0&check1=false&check2=false
2457 ms2639 ms0 KB0 KB200text/htmlXHR
Serve static assets with an efficient cache policy - 21 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://weltauto.mk/js/jquery-1.3.2.min.js
0 ms56 KB
http://weltauto.mk/main.css
0 ms13 KB
http://weltauto.mk/images/logo.jpg
0 ms9 KB
http://weltauto.mk/images/logo2.jpg
0 ms8 KB
http://weltauto.mk/swfobject.js
0 ms7 KB
http://weltauto.mk/images/logo-vwn.jpg
0 ms5 KB
http://weltauto.mk/images/logo-skoda.jpg
0 ms5 KB
http://weltauto.mk/images/home-vwn.jpg
0 ms3 KB
http://weltauto.mk/images/home-skoda.jpg
0 ms3 KB
http://weltauto.mk/images/logo-vw.jpg
0 ms3 KB
http://weltauto.mk/images/logo-audi.jpg
0 ms3 KB
http://weltauto.mk/js/prettyCheckboxes.js
0 ms3 KB
http://weltauto.mk/images/home-audi.jpg
0 ms2 KB
http://weltauto.mk/images/home-vw.jpg
0 ms2 KB
http://weltauto.mk/images/home-search-button.jpg
0 ms2 KB
http://weltauto.mk/images/prettyCheckboxes/checkbox.gif
0 ms2 KB
http://weltauto.mk/prettyCheckboxes.css
0 ms1 KB
http://weltauto.mk/images/header.jpg
0 ms1 KB
http://weltauto.mk/images/home-search-bg.jpg
0 ms1 KB
http://weltauto.mk/images/bullet_blue.gif
0 ms0 KB
http://weltauto.mk/images/bullet.gif
0 ms0 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1034 ms
8 ms
2181 ms
11 ms
2195 ms
14 ms
2214 ms
8 ms
2223 ms
22 ms
JavaScript execution time - 0.1 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
386 ms12 ms3 ms
http://weltauto.mk/js/jquery-1.3.2.min.js
156 ms116 ms8 ms
Remove unused CSS - Potential savings of 11 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.

URL
SizePotential Savings
http://weltauto.mk/main.css
13 KB11 KB
Avoids enormous network payloads - Total size was 202 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://weltauto.mk/js/jquery-1.3.2.min.js
56 KB
http://weltauto.mk/
14 KB
http://weltauto.mk/main.css
13 KB
http://weltauto.mk/?go=_common&p=banner&bannerId=39&1569173117
12 KB
http://weltauto.mk/?go=_common&p=banner&bannerId=40&1569173117
12 KB
http://weltauto.mk/?go=_common&p=banner&bannerId=41&1569173117
11 KB
http://weltauto.mk/?go=_common&p=banner&bannerId=38&1569173117
11 KB
http://weltauto.mk/?go=_common&p=banner&bannerId=35&1569173117
10 KB
http://weltauto.mk/images/logo.jpg
9 KB
http://weltauto.mk/images/logo2.jpg
8 KB
Minimizes main-thread work - 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
191 ms
Script Evaluation
139 ms
Style & Layout
114 ms
Rendering
57 ms
Parse HTML & CSS
41 ms
Script Parsing & Compilation
17 ms
Minimize Critical Requests Depth - 5 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.

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

Efficiently encode images
Optimized images load faster and consume less cellular data. 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.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. 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.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Serve images in next-gen formats
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.

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.

Почетна страница renders only 4 pixels tall (11 CSS pixels) .
Пребарување на дилер and 5 others render only 4 pixels tall (11 CSS pixels) .
КОМЕРЦИЈАЛНИ АВТОМОБИЛИ and 1 others render only 4 pixels tall (11 CSS pixels) .
26 понуди and 3 others render only 4 pixels tall (10 CSS pixels) .
АКЦИСКИ ЦЕНИ З…ОВИ АВТОМОБИЛИ renders only 4 pixels tall (10 CSS pixels) .
СКРАТЕНО ПРЕБАРУВАЊЕ renders only 4 pixels tall (11 CSS pixels) .
Прва регистрација: and 6 others render only 4 pixels tall (10 CSS pixels) .
поврат на ДДВ and 3 others render only 4 pixels tall (10 CSS pixels) .
92 резултати renders only 4 pixels tall (10 CSS pixels) .
Услови на употреба and 3 others render only 4 pixels tall (10 CSS pixels) .

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

Your page has 2 blocking script resources and 1 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://weltauto.mk/js/jquery-1.3.2.min.js
http://weltauto.mk/swfobject.js
Optimize CSS Delivery of the following:

http://weltauto.mk/main.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://weltauto.mk/images/bullet.gif (expiration not specified)
http://weltauto.mk/images/bullet_blue.gif (expiration not specified)
http://weltauto.mk/images/header.jpg (expiration not specified)
http://weltauto.mk/images/home-audi.jpg (expiration not specified)
http://weltauto.mk/images/home-search-bg.jpg (expiration not specified)
http://weltauto.mk/images/home-search-button.jpg (expiration not specified)
http://weltauto.mk/images/home-skoda.jpg (expiration not specified)
http://weltauto.mk/images/home-vw.jpg (expiration not specified)
http://weltauto.mk/images/home-vwn.jpg (expiration not specified)
http://weltauto.mk/images/logo-audi.jpg (expiration not specified)
http://weltauto.mk/images/logo-skoda.jpg (expiration not specified)
http://weltauto.mk/images/logo-vw.jpg (expiration not specified)
http://weltauto.mk/images/logo-vwn.jpg (expiration not specified)
http://weltauto.mk/images/logo.jpg (expiration not specified)
http://weltauto.mk/images/logo2.jpg (expiration not specified)
http://weltauto.mk/images/prettyCheckboxes/checkbox.gif (expiration not specified)
http://weltauto.mk/js/jquery-1.3.2.min.js (expiration not specified)
http://weltauto.mk/js/prettyCheckboxes.js (expiration not specified)
http://weltauto.mk/main.css (expiration not specified)
http://weltauto.mk/prettyCheckboxes.css (expiration not specified)
http://weltauto.mk/swfobject.js (expiration not specified)

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 content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,000 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <img src="images/logo-vwn.jpg"> falls outside the viewport.
The element <td class="header"></td> falls outside the viewport.
The element <b>АКЦИСКИ ЦЕНИ З…ОВИ АВТОМОБИЛИ</b> falls outside the viewport.
The element <img src="?go=_common&amp;p=…=35&amp;15***173111"> falls outside the viewport.
The element <img src="?go=_common&amp;p=…=38&amp;15***173111"> falls outside the viewport.
The element <img src="?go=_common&amp;p=…=39&amp;15***173111"> falls outside the viewport.
The element <img src="?go=_common&amp;p=…=40&amp;15***173111"> falls outside the viewport.
The element <img src="?go=_common&amp;p=…=41&amp;15***173111"> falls outside the viewport.
The element <tr>Скратено пребарување</tr> falls outside the viewport.
The element <tr>Бренд:…92 резултати</tr> falls outside the viewport.
The element <td class="doNotPrint"></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td class="copyright">2009 © Porsche…SP Vision Ltd.</td> falls outside the viewport.
The element <td></td> falls outside the viewport.

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 64.5KiB (***% reduction).

Compressing http://weltauto.mk/js/jquery-1.3.2.min.js could save 36.6KiB (65% reduction).
Compressing http://weltauto.mk/main.css could save 11.1KiB (85% reduction).
Compressing http://weltauto.mk/ could save 10.4KiB (75% reduction).
Compressing http://weltauto.mk/swfobject.js could save 4.5KiB (67% reduction).
Compressing http://weltauto.mk/js/prettyCheckboxes.js could save 1.4KiB (64% reduction).
Compressing http://weltauto.mk/prettyCheckboxes.css could save 438B (59% reduction).

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="?go=home">Почетна страница</a> is close to 2 other tap targets .
The tap target <a href="?go=search">Детално пребарување</a> and 5 others are close to other tap targets .
The tap target <input type="text" name="offerNum" class="textfieldNormal"> is close to 1 other tap targets .
The tap target <input type="image"> is close to 1 other tap targets .

Optimize images

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

Optimize the following images to reduce their size by 26.1KiB (27% reduction).

Compressing http://weltauto.mk/images/logo.jpg could save 3.5KiB (41% reduction).
Compressing http://weltauto.mk/images/logo2.jpg could save 2.8KiB (36% reduction).
Compressing http://weltauto.mk/?go=_common&p=banner&bannerId=39&15***173111 could save 2.4KiB (21% reduction).
Compressing http://weltauto.mk/images/logo-vwn.jpg could save 2.3KiB (46% reduction).
Compressing http://weltauto.mk/?go=_common&p=banner&bannerId=40&15***173111 could save 2.3KiB (21% reduction).
Compressing http://weltauto.mk/images/logo-skoda.jpg could save 2.1KiB (43% reduction).
Compressing http://weltauto.mk/?go=_common&p=banner&bannerId=41&15***173111 could save 1.9KiB (18% reduction).
Compressing http://weltauto.mk/?go=_common&p=banner&bannerId=35&15***173111 could save 1.9KiB (21% reduction).
Compressing http://weltauto.mk/images/home-vwn.jpg could save 1.6KiB (51% reduction).
Compressing http://weltauto.mk/images/home-skoda.jpg could save 1.5KiB (48% reduction).
Compressing http://weltauto.mk/?go=_common&p=banner&bannerId=38&15***173111 could save 1.4KiB (14% reduction).
Compressing http://weltauto.mk/images/logo-vw.jpg could save 662B (24% reduction).
Compressing http://weltauto.mk/images/home-audi.jpg could save 487B (28% reduction).
Compressing http://weltauto.mk/images/logo-audi.jpg could save 461B (18% reduction).
Compressing http://weltauto.mk/images/prettyCheckboxes/checkbox.gif could save 457B (37% reduction).
Compressing http://weltauto.mk/images/home-vw.jpg could save 343B (22% reduction).
Compressing http://weltauto.mk/images/home-search-button.jpg could save 165B (12% reduction).

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 2.4KiB (18% reduction).

Minifying http://weltauto.mk/ could save 2.4KiB (18% reduction).

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.4KiB (11% reduction).

Minifying http://weltauto.mk/main.css could save 1.4KiB (11% reduction).

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 438B (21% reduction).

Minifying http://weltauto.mk/js/prettyCheckboxes.js could save 438B (21% reduction).
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.
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.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does weltauto.mk use compression?

weltauto.mk does not use compression.
Original size: 13.8 KB
Compressed size: n/a
File reduced by: n/a

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

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

+ SSL Checker - SSL Certificate Verify

weltauto.mk does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

weltauto.mk does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Sun, 22 Sep 2019 17:25:04 GMT
Server: Apache/2.2.23 (FreeBSD) DAV/2 PHP/5.2.17 with Suhosin-Patch mod_ssl/2.2.23 OpenSSL/1.0.1c
X-Powered-By: PHP/5.2.17
Set-Cookie: PHPSESSID=2f5316462437c90dc3939e3c39583401; 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
Set-Cookie: visitor=3344576; expires=Tue, 22-Oct-2019 17:25:04 GMT
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8

+ DNS Lookup

Type Ip Target TTL
SOA 3600
Mname ns.mt.net.mk
Rname hostmaster.mt.net.mk
Serial Number 2017122901
Refresh 300
Retry 60
Expire 1209600
Minimum TTL 0
A 79.124.90.105 3575
NS ns.mt.net.mk 3574
NS ns2.mt.net.mk 3574

+ Whois Lookup

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

whois lookup at whois.marnet.mk...
% Domain Information over Whois protocol
%
% Whoisd Server Version: 3.9.0
% Timestamp: Sun Sep 22 19:25:31 2019

domain: weltauto.mk
registrant: NEXT-R60199
admin-c: NEXT-C557117
nsset: NEXT-NS32451
registrar: NEXTEM-REG
registered: 05.02.2010 13:00:00
changed: 09.01.2015 12:14:52
expire: 05.02.2020

contact: NEXT-R60199
org: Друштво за промет и услуги ПОРШЕ МАКЕДОНИЈА ДООЕЛ Скопје
name: ПОРШЕ МАКЕДОНИЈА ДООЕЛ Скопје
address: Босна и Херцеговина 4
address: Скопје
address: 1000
address: MK
phone: +389.22626266
e-mail: email
registrar: NEXTEM-REG
created: 03.04.2014 20:34:42
changed: 06.08.2014 16:04:47

contact: NEXT-C557117
name: Иван Јанкијевиќ
address: -
address: -
address: -
address: MK
phone: +389.70254044
e-mail: email
registrar: NEXTEM-REG
created: 06.08.2014 16:10:24

nsset: NEXT-NS32451
nserver: ns.mt.net.mk
nserver: ns2.mt.net.mk
tech-c: NEXT-C557117
registrar: NEXTEM-REG
created: 06.08.2014 16:10:29
Last update was 152 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with weltauto.mk 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!
weltauto.mk widget