Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

blog.tanin.net

طنین تکنولوژی - پنجره ای دیگر به دنیای فناوری اطلاعات

Page Load Speed

15.6 sec in total

First Response

5.2 sec

Resources Loaded

9.8 sec

Page Rendered

536 ms

blog.tanin.net screenshot

About Website

Click here to check amazing Blog Tanin content for Iran. Otherwise, check out these important facts you probably never knew about blog.tanin.net

Visit blog.tanin.net

Key Findings

We analyzed Blog.tanin.net page load time and found that the first response time was 5.2 sec and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

blog.tanin.net performance score

0

Network Requests Diagram

blog.tanin.net

5192 ms

style.css

991 ms

css

39 ms

style.css

908 ms

dashicons.min.css

1646 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 89% of them (50 requests) were addressed to the original Blog.tanin.net, 4% (2 requests) were made to Apis.google.com and 4% (2 requests) were made to S10.histats.com. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Blog.tanin.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 371.2 kB (49%)

Content Size

757.6 kB

After Optimization

386.3 kB

In fact, the total size of Blog.tanin.net main page is 757.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. 30% of websites need less resources to load. Images take 319.2 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 148.8 kB

  • Original 161.6 kB
  • After minification 74.2 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 87.4 kB, which is 54% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 148.8 kB or 92% of the original size.

Image Optimization

-13%

Potential reduce by 40.5 kB

  • Original 319.2 kB
  • After minification 278.7 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, Blog Tanin needs image optimization as it can save up to 40.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 144.2 kB

  • Original 206.5 kB
  • After minification 185.3 kB
  • After compression 62.3 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 144.2 kB or 70% of the original size.

CSS Optimization

-54%

Potential reduce by 37.8 kB

  • Original 70.3 kB
  • After minification 61.6 kB
  • After compression 32.5 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. Blog.tanin.net needs all CSS files to be minified and compressed as it can save up to 37.8 kB or 54% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (46%)

Requests Now

54

After Optimization

29

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

SEO Factors

blog.tanin.net SEO score

0

Language and Encoding

  • Language Detected

    FA

  • Language Claimed

    FA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.tanin.net can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it matches the claimed language. Our system also found out that Blog.tanin.net 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

Open Graph description is not detected on the main page of Blog Tanin. 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: