Tools & Wizards About Us
cur.sub.ir screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 69

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

cur.sub.ir

خدمات وبلاگ نويسان جوان

Page Load Speed

2.4 sec in total

First Response

363 ms

Resources Loaded

1.3 sec

Page Rendered

779 ms

cur.sub.ir screenshot

About Website

Visit cur.sub.ir now to see the best up-to-date Cur Sub content for Iran and also check out these interesting facts you probably never knew about cur.sub.ir

Visit cur.sub.ir

Key Findings

We analyzed Cur.sub.ir page load time and found that the first response time was 363 ms and then it took 2 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.

Performance Metrics

cur.sub.ir performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.502

16/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

cur.sub.ir

363 ms

bahar-20.com

112 ms

css.css

52 ms

online

33 ms

nazare.you.js

65 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Cur.sub.ir, 88% (50 requests) were made to Bahar-20.com and 4% (2 requests) were made to Opi.yahoo.com. The less responsive or slowest element that took the longest time to load (748 ms) relates to the external source Pichak.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 36.0 kB (11%)

Content Size

320.4 kB

After Optimization

284.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cur.sub.ir main page is 320.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. 35% of websites need less resources to load. Images take 301.3 kB which makes up the majority of the site volume.

HTML Optimization

-41%

Potential reduce by 261 B

  • Original 639 B
  • After minification 639 B
  • After compression 378 B

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 261 B or 41% of the original size.

Image Optimization

-7%

Potential reduce by 20.1 kB

  • Original 301.3 kB
  • After minification 281.2 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. Cur Sub images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 157 B

  • Original 552 B
  • After minification 513 B
  • After compression 395 B

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 157 B or 28% of the original size.

CSS Optimization

-87%

Potential reduce by 15.6 kB

  • Original 17.9 kB
  • After minification 15.5 kB
  • After compression 2.4 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. Cur.sub.ir needs all CSS files to be minified and compressed as it can save up to 15.6 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (31%)

Requests Now

55

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cur.sub.ir

cur.sub.ir

363 ms

bahar-20.com

bahar-20.com

112 ms

css.css

css.css

52 ms

online

online

33 ms

nazare.you.js

nazare.you.js

65 ms

nvbn61.gif

nvbn61.gif

72 ms

2rwnhpc.gif

2rwnhpc.gif

71 ms

2lm3t35.gif

2lm3t35.gif

72 ms

ffcrgk.gif

ffcrgk.gif

73 ms

hrknbd.gif

hrknbd.gif

72 ms

bahar.js

bahar.js

53 ms

bahar-20.jpg

bahar-20.jpg

104 ms

online

online

32 ms

view-small.jpg

view-small.jpg

501 ms

pichak.gif

pichak.gif

502 ms

dx0g79.jpg

dx0g79.jpg

83 ms

9qyyx1.gif

9qyyx1.gif

32 ms

1z222o8.jpg

1z222o8.jpg

50 ms

10yj828.jpg

10yj828.jpg

39 ms

2cz9fee.jpg

2cz9fee.jpg

41 ms

degree.gif

degree.gif

47 ms

2lsuogy.gif

2lsuogy.gif

59 ms

33ab8eb.gif

33ab8eb.gif

61 ms

alexa.jpg

alexa.jpg

91 ms

2z8p076.gif

2z8p076.gif

84 ms

2vrzwjr.gif

2vrzwjr.gif

86 ms

chat2.jpg

chat2.jpg

183 ms

test.gif

test.gif

180 ms

pic.jpg

pic.jpg

175 ms

07.gif

07.gif

197 ms

2mdl1lf.gif

2mdl1lf.gif

176 ms

02.gif

02.gif

176 ms

307xac7.gif

307xac7.gif

180 ms

sibtheme.gif

sibtheme.gif

71 ms

011.gif

011.gif

77 ms

Weather.jpg

Weather.jpg

173 ms

02.jpg

02.jpg

176 ms

01.gif

01.gif

78 ms

02.gif

02.gif

93 ms

03.gif

03.gif

104 ms

04.gif

04.gif

176 ms

01.gif

01.gif

174 ms

02.gif

02.gif

175 ms

03.gif

03.gif

176 ms

04.gif

04.gif

179 ms

05.gif

05.gif

178 ms

06.gif

06.gif

179 ms

07.gif

07.gif

178 ms

08.gif

08.gif

181 ms

09.gif

09.gif

180 ms

10.gif

10.gif

182 ms

11.gif

11.gif

182 ms

12.gif

12.gif

184 ms

001.gif

001.gif

191 ms

pr3.gif

pr3.gif

183 ms

view-small.jpg

view-small.jpg

745 ms

4.gif

4.gif

748 ms

Accessibility Review

cur.sub.ir accessibility score

33

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

cur.sub.ir best practices score

69

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

cur.sub.ir SEO score

64

Search Engine Optimization Advices

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 Cur.sub.ir 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 Cur.sub.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

cur.sub.ir

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