Tools & Wizards About Us
13.epage.ir screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

13.epage.ir

ایجاد و مدیریت وب‌سایت داینامیک epage

Page Load Speed

6.2 sec in total

First Response

249 ms

Resources Loaded

5.8 sec

Page Rendered

194 ms

13.epage.ir screenshot

About Website

Welcome to 13.epage.ir homepage info - get ready to check 13 Epage best content for Iran right away, or after learning these important things about 13.epage.ir

cms سیستمی است برای ایجاد و مدیریت رایگان وب سایت داینامیک با ابزارهای کامل یک سیستم مدیریت محتوا epage

Visit 13.epage.ir

Key Findings

We analyzed 13.epage.ir page load time and found that the first response time was 249 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

13.epage.ir performance score

0

Network Requests Diagram

13.epage.ir

249 ms

www.epage.ir

867 ms

index.css

38 ms

login.css

76 ms

alamoot.js

1599 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original 13.epage.ir, 86% (25 requests) were made to Epage.ir and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Epage.ir.

Page Optimization Overview & Recommendations

Page size can be reduced by 158.9 kB (38%)

Content Size

421.4 kB

After Optimization

262.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 13.epage.ir main page is 421.4 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. 15% of websites need less resources to load. Images take 249.7 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 7.6 kB

  • Original 11.2 kB
  • After minification 10.1 kB
  • After compression 3.6 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 7.6 kB or 68% of the original size.

Image Optimization

-12%

Potential reduce by 30.8 kB

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

JavaScript Optimization

-75%

Potential reduce by 117.3 kB

  • Original 156.0 kB
  • After minification 111.7 kB
  • After compression 38.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 117.3 kB or 75% of the original size.

CSS Optimization

-72%

Potential reduce by 3.2 kB

  • Original 4.5 kB
  • After minification 3.5 kB
  • After compression 1.3 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. 13.epage.ir needs all CSS files to be minified and compressed as it can save up to 3.2 kB or 72% of the original size.

Requests Breakdown

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

Requests Now

27

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

13.epage.ir

13.epage.ir

249 ms

www.epage.ir

www.epage.ir

867 ms

index.css

index.css

38 ms

login.css

login.css

76 ms

alamoot.js

alamoot.js

1599 ms

jquery126.js

jquery126.js

1851 ms

jquery.dimensions.js

jquery.dimensions.js

2004 ms

logo.aspx

logo.aspx

840 ms

image.php

image.php

794 ms

main_bg.gif

main_bg.gif

49 ms

dynamic_site.gif

dynamic_site.gif

75 ms

huge_capacity.gif

huge_capacity.gif

49 ms

fast_site.gif

fast_site.gif

50 ms

build_site.gif

build_site.gif

597 ms

1_sign.png

1_sign.png

73 ms

2_sign.png

2_sign.png

770 ms

3_sign.png

3_sign.png

74 ms

4_sign.png

4_sign.png

75 ms

sup_tel_new.png

sup_tel_new.png

181 ms

intro_7.png

intro_7.png

333 ms

hr_footer.png

hr_footer.png

111 ms

bullet.jpg

bullet.jpg

112 ms

analytics.js

analytics.js

27 ms

content_bg.jpg

content_bg.jpg

143 ms

page2.png

page2.png

178 ms

signup_bg.png

signup_bg.png

217 ms

aca_company.png

aca_company.png

211 ms

server.php

server.php

2642 ms

collect

collect

12 ms

SEO Factors

13.epage.ir SEO score

0

Language and Encoding

  • Language Detected

    FA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 13.epage.ir can be misinterpreted by Google and other search engines. Our service has detected that Persian 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 13.epage.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.

Social Sharing Optimization

13.epage.ir

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