Access behinegar.net. سیستم مدیریت پروژه محصول بهینه گر - سیستم کنترل پروژه

name

value

score

weighting

FCP (First Contentful Paint)

Value8.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.1 s

0/100

25%

SI (Speed Index)

Value17.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,980 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.118

85/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

behinegar.net

545 ms

behinegar.net

2915 ms

style-rtl.min.css

514 ms

styles.css

519 ms

styles-rtl.css

526 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 99% of them (109 requests) were addressed to the original Behinegar.net, 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Behinegar.net.

Content Size

2.2 MB

After Optimization

1.8 MB

In fact, the total size of Behinegar.net main page is 2.2 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. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 186.4 kB

Original 215.8 kB
After minification 212.3 kB
After compression 29.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 186.4 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 41.3 kB

Original 1.1 MB
After minification 1.1 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. Behinegar images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 82.7 kB

Original 485.1 kB
After minification 485.1 kB
After compression 402.4 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 82.7 kB or 17% of the original size.

CSS Optimization

-26%

Potential reduce by 98.7 kB

Original 377.4 kB
After minification 374.8 kB
After compression 278.7 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. Behinegar.net needs all CSS files to be minified and compressed as it can save up to 98.7 kB or 26% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

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.

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

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

behinegar.net

Open Graph data is detected on the main page of Behinegar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

سیستم مدیریت پروژه محصول بهینه گر - سیستم کنترل پروژه - محصول بهینه گر

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

behinegar.net

behinegar.net

style-rtl.min.css

styles.css

styles-rtl.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

behinegar.net

behinegar.net

style-rtl.min.css

styles.css

styles-rtl.css

settings.css

js_composer.min.css

css

main.min.css

back-compat.min.css

fontawesome-all.min.css

fontello.min.css

post-type.css

custom.css

media.css

legacy.css

post-type-dynamic.css

style.css

Defaults.css

ultimate.min-rtl.css

rtl-common.min.css

jquery.js

jquery-migrate.min.js

jquery.themepunch.tools.min.js

jquery.themepunch.revolution.min.js

above-the-fold.min.js

core.min.js

ultimate.min.js

rtl.css

fonts.css

animate.min.css

main.min.js

scripts.js

legacy.min.js

post-type.js

js_composer_front.min.js

vhparallax.min.js

waypoints.min.js

gplaypattern.jpg

anim.gif

logo.png

slider.jpg

titr.jpg