2.2 sec in total
52 ms
969 ms
1.1 sec
Welcome to azimi.me homepage info - get ready to check Azimi best content for India right away, or after learning these important things about azimi.me
Mohsen Azimi's personal weblog
Visit azimi.meWe analyzed Azimi.me page load time and found that the first response time was 52 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
azimi.me performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value121.1 s
0/100
25%
Value5.0 s
63/100
10%
Value2,800 ms
3/100
30%
Value0.13
82/100
15%
Value16.7 s
5/100
10%
52 ms
13 ms
25 ms
16 ms
33 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 57% of them (33 requests) were addressed to the original Azimi.me, 17% (10 requests) were made to Fonts.gstatic.com and 10% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (590 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 729.2 kB (26%)
2.8 MB
2.1 MB
In fact, the total size of Azimi.me main page is 2.8 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. 65% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 54.0 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 54.0 kB or 80% of the original size.
Potential reduce by 635.1 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. Obviously, Azimi needs image optimization as it can save up to 635.1 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 32.0 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 32.0 kB or 60% of the original size.
Potential reduce by 8.2 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. Azimi.me needs all CSS files to be minified and compressed as it can save up to 8.2 kB or 83% of the original size.
Number of requests can be reduced by 6 (13%)
45
39
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Azimi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for CSS and as a result speed up the page load time.
azimi.me
52 ms
main.css
13 ms
css
25 ms
index.html
16 ms
index.html
33 ms
index.html
26 ms
angular-timeline.png
41 ms
js-timeline.png
31 ms
slow-parse.png
30 ms
ios-quicklook.png
98 ms
css
140 ms
css
146 ms
css
149 ms
jquery-1.9.1.min.js
21 ms
remark-latest.min.js
170 ms
analytics.js
21 ms
css
131 ms
css
130 ms
collect
44 ms
gDxHeefcXIo-lOuZFCn2xYpDzyv1hRY7H2tyVr4HG0g.ttf
24 ms
LeFlHvsZjXu2c3ZRgBq9nKCWcynf_cDxXwCLxiixG1c.ttf
31 ms
EvPKapBawcLZ3hbihjhqAaCWcynf_cDxXwCLxiixG1c.ttf
43 ms
2koEo4AKFSvK4B52O_MwaonF5uFdDttMLvmWuJdhhgs.ttf
51 ms
leqv3v-yTsJNC7nFznSMqcw1o1eFRj7wYC6JbISqOjY.ttf
51 ms
QQt14e8dY39u-eYBZmppwZ_TkvowlIOtbR7ePgFOpF4.ttf
590 ms
543633
519 ms
ViZhet7Ak-LRXZMXzuAfkZ0EAVxt0G0biEntp43Qt6E.ttf
339 ms
ceqTZGKHipo8pJj4molytp_TkvowlIOtbR7ePgFOpF4.ttf
338 ms
YDAoLskQQ5MOAgvHUQCcLbvy90DtE_Pg_qiF9bHvTzw.ttf
339 ms
define-swagger.png
106 ms
screenshot.png
92 ms
screenshot.png
93 ms
design_tools.jpg
45 ms
yeoman.png
43 ms
pic_angular.jpg
46 ms
js.png
46 ms
swagger.png
41 ms
ace-logo.png
57 ms
grunt.png
56 ms
jshint.png
54 ms
jscs.png
56 ms
github.png
74 ms
code-compile-render.png
68 ms
read-yaml-.png
85 ms
swagger-ui.png
68 ms
pub-sub.png
69 ms
wrong_order.png
65 ms
ast.png
109 ms
sorter.png
82 ms
full-sorter.png
87 ms
error-line.png
91 ms
swagger-error.png
109 ms
ast-walker.png
111 ms
try.png
115 ms
try-form.png
137 ms
EvPKapBawcLZ3hbihjhqAaCWcynf_cDxXwCLxiixG1c.ttf
47 ms
screenshot.png
85 ms
screenshot.png
84 ms
azimi.me 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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
azimi.me best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
azimi.me SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Azimi.me can be misinterpreted by Google and other search engines. Our service has detected that English 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 Azimi.me 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.
azimi.me
Open Graph description is not detected on the main page of Azimi. 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: