Tools & Wizards About Us
nashgorod.kz screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nashgorod.kz

НАШ ГОРОД, справочник фирм и организаций, товаров и услуг, телефонный справочник г. Алматы.

Page Load Speed

3.9 sec in total

First Response

1 sec

Resources Loaded

2.7 sec

Page Rendered

209 ms

nashgorod.kz screenshot

About Website

Visit nashgorod.kz now to see the best up-to-date Nashgorod content for Kazakhstan and also check out these interesting facts you probably never knew about nashgorod.kz

НАШ ГОРОД, справочник фирм и организаций, товаров и услуг, телефонный справочник г. Алматы.

Visit nashgorod.kz

Key Findings

We analyzed Nashgorod.kz page load time and found that the first response time was 1 sec and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

nashgorod.kz performance score

0

Network Requests Diagram

nashgorod.kz

1038 ms

style.css

561 ms

MyStyle.css

577 ms

newMainPageMenu.css

395 ms

jquery-1.2.3.pack.js

1115 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 63% of them (36 requests) were addressed to the original Nashgorod.kz, 12% (7 requests) were made to Apis.google.com and 9% (5 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Nashgorod.kz.

Page Optimization Overview & Recommendations

Page size can be reduced by 880.1 kB (73%)

Content Size

1.2 MB

After Optimization

331.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nashgorod.kz main page is 1.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 949.3 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 70.4 kB

  • Original 100.8 kB
  • After minification 90.3 kB
  • After compression 30.3 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 70.4 kB or 70% of the original size.

Image Optimization

-3%

Potential reduce by 2.7 kB

  • Original 81.1 kB
  • After minification 78.4 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Nashgorod images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 740.5 kB

  • Original 949.3 kB
  • After minification 778.5 kB
  • After compression 208.8 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 740.5 kB or 78% of the original size.

CSS Optimization

-83%

Potential reduce by 66.4 kB

  • Original 80.1 kB
  • After minification 63.1 kB
  • After compression 13.7 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Nashgorod.kz needs all CSS files to be minified and compressed as it can save up to 66.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (70%)

Requests Now

53

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nashgorod. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

nashgorod.kz

nashgorod.kz

1038 ms

style.css

style.css

561 ms

MyStyle.css

MyStyle.css

577 ms

newMainPageMenu.css

newMainPageMenu.css

395 ms

jquery-1.2.3.pack.js

jquery-1.2.3.pack.js

1115 ms

js.js

js.js

680 ms

platform.js

platform.js

99 ms

Site.css

Site.css

402 ms

WebResource.axd

WebResource.axd

438 ms

WebResource.axd

WebResource.axd

650 ms

WebResource.axd

WebResource.axd

484 ms

WebResource.axd

WebResource.axd

697 ms

ScriptResource.axd

ScriptResource.axd

788 ms

ScriptResource.axd

ScriptResource.axd

762 ms

ScriptResource.axd

ScriptResource.axd

803 ms

ScriptResource.axd

ScriptResource.axd

1074 ms

ScriptResource.axd

ScriptResource.axd

691 ms

ScriptResource.axd

ScriptResource.axd

886 ms

ScriptResource.axd

ScriptResource.axd

918 ms

ScriptResource.axd

ScriptResource.axd

984 ms

ScriptResource.axd

ScriptResource.axd

984 ms

ScriptResource.axd

ScriptResource.axd

1005 ms

WebResource.axd

WebResource.axd

1109 ms

bg_body.jpg

bg_body.jpg

738 ms

watch.js

watch.js

193 ms

ga.js

ga.js

39 ms

3_0_FFFFFFFF_EFEFEFFF_0_pageviews

3_0_FFFFFFFF_EFEFEFFF_0_pageviews

410 ms

Logo.png

Logo.png

501 ms

__utm.gif

__utm.gif

26 ms

lang_panel.png

lang_panel.png

239 ms

bg_search_block.jpg

bg_search_block.jpg

391 ms

WebResource.axd

WebResource.axd

212 ms

button_search_dis.png

button_search_dis.png

217 ms

arrow_gray.png

arrow_gray.png

211 ms

sitemap.png

sitemap.png

301 ms

no_selected1.png

no_selected1.png

467 ms

last_no_selected1.png

last_no_selected1.png

394 ms

Znach_map_blak.jpg

Znach_map_blak.jpg

469 ms

Znach_popul_zapros_blak.jpg

Znach_popul_zapros_blak.jpg

475 ms

Znach_polez_info_blak.jpg

Znach_polez_info_blak.jpg

486 ms

Znach_rekl_blak.jpg

Znach_rekl_blak.jpg

591 ms

watch.js

watch.js

491 ms

watch.js

watch.js

670 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

19 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

55 ms

sharebutton

sharebutton

159 ms

postmessageRelay

postmessageRelay

46 ms

api.js

api.js

55 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

146 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

141 ms

rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA

rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA

37 ms

rs=AGLTcCOmp8KZ86Ph_j3x8mWLueHeWHKNqw

rs=AGLTcCOmp8KZ86Ph_j3x8mWLueHeWHKNqw

70 ms

IhuqmeHx65TaW6CiR2l0VALUuEpTyoUstqEm5AMlJo4.ttf

IhuqmeHx65TaW6CiR2l0VALUuEpTyoUstqEm5AMlJo4.ttf

139 ms

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

159 ms

hit

hit

129 ms

advert.gif

advert.gif

265 ms

1

1

92 ms

SEO Factors

nashgorod.kz SEO score

0

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nashgorod.kz can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nashgorod.kz main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

nashgorod.kz

Open Graph description is not detected on the main page of Nashgorod. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: