4.7 sec in total
1.1 sec
3.3 sec
362 ms
Visit citygraph.ir now to see the best up-to-date Citygraph content for Iran and also check out these interesting facts you probably never knew about citygraph.ir
Visit citygraph.irWe analyzed Citygraph.ir page load time and found that the first response time was 1.1 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
citygraph.ir performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value7.1 s
6/100
25%
Value10.7 s
7/100
10%
Value120 ms
97/100
30%
Value0.302
39/100
15%
Value8.6 s
37/100
10%
1075 ms
110 ms
218 ms
806 ms
623 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 74% of them (56 requests) were addressed to the original Citygraph.ir, 9% (7 requests) were made to Apis.google.com and 4% (3 requests) were made to Avazak.ir. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Citygraph.ir.
Page size can be reduced by 97.1 kB (16%)
595.6 kB
498.5 kB
In fact, the total size of Citygraph.ir main page is 595.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 494.5 kB which makes up the majority of the site volume.
Potential reduce by 42.8 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 42.8 kB or 83% of the original size.
Potential reduce by 31.6 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. Citygraph images are well optimized though.
Potential reduce by 8.7 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 8.7 kB or 26% of the original size.
Potential reduce by 13.9 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. Citygraph.ir needs all CSS files to be minified and compressed as it can save up to 13.9 kB or 86% of the original size.
Number of requests can be reduced by 10 (14%)
74
64
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Citygraph. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.citygraph.ir
1075 ms
style.css
110 ms
sourcebaran.com_.js
218 ms
jquery.min.js
806 ms
623 ms
1000Charge2-468.gif
900 ms
a
20 ms
c.aspx
143 ms
plusone.js
103 ms
CityGraph1-sarbazi-150x150.jpg
218 ms
CityGraph4-4-150x150.jpg
218 ms
CityGraph4-3-150x150.jpg
219 ms
CityGraph4-2-150x150.jpg
218 ms
CityGraph4-1-150x150.jpg
223 ms
CityGraph3-100-150x150.jpg
313 ms
CityGraph3-99-150x150.jpg
328 ms
CityGraph3-97-150x150.jpg
323 ms
CityGraph3-98-150x150.jpg
325 ms
CityGraph3-.96-150x150.jpg
325 ms
gallery57-150x150.jpg
335 ms
gallery55-150x150.jpg
421 ms
gallery54-150x150.jpg
432 ms
gallery53-150x150.jpg
433 ms
gallery51-150x150.jpg
434 ms
gallery50-150x150.jpg
440 ms
gallery49-150x150.jpg
446 ms
gallery48-150x150.jpg
529 ms
gallery46-150x150.jpg
538 ms
gallery45-150x150.jpg
542 ms
gallery44-150x150.jpg
543 ms
gallery43-150x150.jpg
553 ms
gallery42-150x150.jpg
557 ms
gallery41-150x150.jpg
636 ms
gallery40-150x150.jpg
646 ms
gallery39-150x150.jpg
650 ms
gallery38-150x150.jpg
651 ms
gallery37-150x150.jpg
666 ms
gallery35-150x150.jpg
669 ms
gallery34-150x150.jpg
744 ms
gallery33-150x150.jpg
754 ms
gallery32-150x150.jpg
758 ms
gallery30-150x150.jpg
759 ms
gallery29-150x150.jpg
778 ms
gallery28-150x150.jpg
688 ms
gallery27-150x150.jpg
651 ms
gallery26-150x150.jpg
658 ms
gallery25-150x150.jpg
658 ms
gallery24-150x150.jpg
669 ms
gallery23-150x150.jpg
681 ms
gallery22-150x150.jpg
675 ms
gallery19-150x150.jpg
654 ms
gallery21-150x150.jpg
650 ms
gallery20-150x150.jpg
654 ms
gallery18-150x150.jpg
656 ms
gallery17-150x150.jpg
689 ms
Avazak.gif
902 ms
akharinnafas.ir_.gif
761 ms
logo.jpg
865 ms
link.png
655 ms
h1.png
285 ms
hederg.png
579 ms
h2.png
392 ms
s.gif
24 ms
stat8.gif
140 ms
xstat.aspx
163 ms
cb=gapi.loaded_0
17 ms
citygraph.png
189 ms
cb=gapi.loaded_1
23 ms
fastbutton
169 ms
postmessageRelay
34 ms
api.js
46 ms
core:rpc:shindig.random:shindig.sha1.js
87 ms
2536007149-postmessagerelay.js
59 ms
cb=gapi.loaded_0
13 ms
cb=gapi.loaded_1
16 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
74 ms
citygraph.ir accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
citygraph.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
citygraph.ir SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document doesn't use legible font sizes
Tap targets are not sized appropriately
FA
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Citygraph.ir can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it does not match the claimed English language. Our system also found out that Citygraph.ir 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.
citygraph.ir
Open Graph description is not detected on the main page of Citygraph. 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: