Tools & Wizards About Us
otinet.ir screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

otinet.ir

سیستم شاطل-افق طلایی

Page Load Speed

4.5 sec in total

First Response

1.2 sec

Resources Loaded

3.2 sec

Page Rendered

132 ms

otinet.ir screenshot

About Website

Click here to check amazing Otinet content for Iran. Otherwise, check out these important facts you probably never knew about otinet.ir

سامانه شاطل مکانیزه کردن تمامی امور و فعالیتهای شرکت افق طلایی

Visit otinet.ir

Key Findings

We analyzed Otinet.ir page load time and found that the first response time was 1.2 sec and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

otinet.ir performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.373

28/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

Network Requests Diagram

otinet.ir

1181 ms

MyStyle.css

543 ms

jquery-2.1.0.min.js

706 ms

jquery.min.js

702 ms

PortalLogo2.jpg

182 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that all of those requests were addressed to Otinet.ir and no external sources were called. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Otinet.ir.

Page Optimization Overview & Recommendations

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

Content Size

2.1 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Otinet.ir main page is 2.1 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. 25% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 10.5 kB

  • Original 13.9 kB
  • After minification 12.9 kB
  • After compression 3.4 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 10.5 kB or 76% of the original size.

Image Optimization

-34%

Potential reduce by 647.0 kB

  • Original 1.9 MB
  • After minification 1.2 MB

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, Otinet needs image optimization as it can save up to 647.0 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 117.0 kB

  • Original 180.1 kB
  • After minification 180.1 kB
  • After compression 63.1 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.0 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 30.4 kB

  • Original 36.3 kB
  • After minification 28.3 kB
  • After compression 5.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. Otinet.ir needs all CSS files to be minified and compressed as it can save up to 30.4 kB or 84% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

27

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otinet. According to our analytics all requests are already optimized.

Network Requests Diagram

otinet.ir

otinet.ir

1181 ms

MyStyle.css

MyStyle.css

543 ms

jquery-2.1.0.min.js

jquery-2.1.0.min.js

706 ms

jquery.min.js

jquery.min.js

702 ms

PortalLogo2.jpg

PortalLogo2.jpg

182 ms

HomePageNormal.png

HomePageNormal.png

732 ms

Payam.png

Payam.png

518 ms

keramatshop.png

keramatshop.png

176 ms

Keramatcard.png

Keramatcard.png

350 ms

OtiVila.png

OtiVila.png

346 ms

OfoghGroup.png

OfoghGroup.png

356 ms

Mashregh.png

Mashregh.png

360 ms

Ofta.png

Ofta.png

519 ms

T3.png

T3.png

522 ms

T2.png

T2.png

534 ms

T1.png

T1.png

540 ms

T6.png

T6.png

693 ms

T5.png

T5.png

693 ms

T4.png

T4.png

861 ms

SlidePic.html

SlidePic.html

690 ms

BYekan.woff

BYekan.woff

692 ms

NewBackground.png

NewBackground.png

839 ms

Slide0.png

Slide0.png

359 ms

Slide1.png

Slide1.png

680 ms

Slide2.png

Slide2.png

709 ms

Slide3.png

Slide3.png

546 ms

Slide4.png

Slide4.png

653 ms

Slide5.png

Slide5.png

495 ms

Slide6.png

Slide6.png

545 ms

Accessibility Review

otinet.ir accessibility score

61

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

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

High

Image elements do not have [alt] attributes

High

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

High

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

Best Practices

otinet.ir best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

otinet.ir SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

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 Otinet.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 Otinet.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

otinet.ir

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