Tools & Wizards About Us
phx.ir screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

phx.ir

ققنوس - مدیریت پیمانکاران، تامین کنندگان و تولید کنندگان

Page Load Speed

36.6 sec in total

First Response

5.1 sec

Resources Loaded

28.4 sec

Page Rendered

3 sec

phx.ir screenshot

About Website

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

طراحی، تولید و پیاده سازی سامانه های مدیریت مناقصات و مزایدات - مدیریت پیمانکاران و تامین کنندگان - مدیریت فرآیند های HSE - ارزیابی کیفی

Visit phx.ir

Key Findings

We analyzed Phx.ir page load time and found that the first response time was 5.1 sec and then it took 31.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

phx.ir performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value31.9 s

0/100

10%

Network Requests Diagram

phx.ir

5145 ms

wp-emoji-release.min.js

166 ms

bdt-uikit.rtl.css

492 ms

ep-helper.rtl.css

498 ms

style-rtl.min.css

662 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 95% of them (84 requests) were addressed to the original Phx.ir, 2% (2 requests) were made to Fonts.googleapis.com and 1% (1 request) were made to Trustseal.enamad.ir. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Trustseal.enamad.ir.

Page Optimization Overview & Recommendations

Page size can be reduced by 225.3 kB (2%)

Content Size

9.6 MB

After Optimization

9.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 107.5 kB

  • Original 132.8 kB
  • After minification 125.1 kB
  • After compression 25.3 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 107.5 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 3.6 kB

  • Original 9.1 MB
  • After minification 9.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. Phx images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 18.3 kB

  • Original 131.8 kB
  • After minification 131.7 kB
  • After compression 113.5 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 18.3 kB or 14% of the original size.

CSS Optimization

-33%

Potential reduce by 95.9 kB

  • Original 287.3 kB
  • After minification 282.8 kB
  • After compression 191.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. Phx.ir needs all CSS files to be minified and compressed as it can save up to 95.9 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (69%)

Requests Now

75

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phx.ir

phx.ir

5145 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

166 ms

bdt-uikit.rtl.css

bdt-uikit.rtl.css

492 ms

ep-helper.rtl.css

ep-helper.rtl.css

498 ms

style-rtl.min.css

style-rtl.min.css

662 ms

fonts.css

fonts.css

510 ms

base.css

base.css

695 ms

auxin-icon.css

auxin-icon.css

526 ms

main.css

main.css

979 ms

frontend-lite-rtl.min.css

frontend-lite-rtl.min.css

665 ms

post-481.css

post-481.css

680 ms

elementor.css

elementor.css

704 ms

elementor-widgets.css

elementor-widgets.css

827 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

830 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

850 ms

post-514.css

post-514.css

869 ms

css

css

27 ms

custom.css

custom.css

879 ms

go-pricing.css

go-pricing.css

1018 ms

post-513.css

post-513.css

1019 ms

post-493.css

post-493.css

1021 ms

css

css

42 ms

jquery.min.js

jquery.min.js

1214 ms

jquery-migrate.min.js

jquery-migrate.min.js

1053 ms

widgets.js

widgets.js

1141 ms

modernizr-custom.min.js

modernizr-custom.min.js

1158 ms

rtl.css

rtl.css

1169 ms

tippy.rtl.css

tippy.rtl.css

1190 ms

ep-font.rtl.css

ep-font.rtl.css

1388 ms

ep-helpdesk.rtl.css

ep-helpdesk.rtl.css

1388 ms

imagesloaded.min.js

imagesloaded.min.js

1415 ms

masonry.min.js

masonry.min.js

1416 ms

plugins.min.js

plugins.min.js

2026 ms

widgets.js

widgets.js

1452 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

1574 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

1465 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

1487 ms

plugins.min.js

plugins.min.js

1498 ms

scripts.js

scripts.js

1561 ms

scripts.min.js

scripts.min.js

1473 ms

jquery-numerator.min.js

jquery-numerator.min.js

1164 ms

pro-tools.js

pro-tools.js

1172 ms

custom.js

custom.js

1232 ms

bdt-uikit.min.js

bdt-uikit.min.js

1400 ms

webpack.runtime.min.js

webpack.runtime.min.js

1138 ms

frontend-modules.min.js

frontend-modules.min.js

1156 ms

waypoints.min.js

waypoints.min.js

1154 ms

core.min.js

core.min.js

1217 ms

frontend.min.js

frontend.min.js

1262 ms

ep-wrapper-link.min.js

ep-wrapper-link.min.js

1163 ms

popper.min.js

popper.min.js

1168 ms

tippy.all.min.js

tippy.all.min.js

1253 ms

ep-tooltip.min.js

ep-tooltip.min.js

1235 ms

ep-helpdesk.min.js

ep-helpdesk.min.js

1249 ms

helper.min.js

helper.min.js

1138 ms

logo.aspx

logo.aspx

20332 ms

logo.aspx

logo.aspx

1437 ms

%D9%82%D9%82%D9%86%D9%88%D8%B3-%D9%84%D9%88%DA%AF%D9%88.png

%D9%82%D9%82%D9%86%D9%88%D8%B3-%D9%84%D9%88%DA%AF%D9%88.png

891 ms

%D9%82%D9%82%D9%86%D9%88%D8%B3-3.png

%D9%82%D9%82%D9%86%D9%88%D8%B3-3.png

1388 ms

%D8%A7%D8%B7%D9%84%D8%A7%D8%B9-%D8%B1%D8%B3%D8%A7%D9%86%DB%8C-%D9%88-%D9%81%D9%86%D8%A7%D9%88%D8%B1%DB%8C-%D8%A7%D8%B7%D9%84%D8%A7%D8%B9%D8%A7%D8%AA-%D9%82%D9%82%D9%86%D9%88%D8%B3-2.png

%D8%A7%D8%B7%D9%84%D8%A7%D8%B9-%D8%B1%D8%B3%D8%A7%D9%86%DB%8C-%D9%88-%D9%81%D9%86%D8%A7%D9%88%D8%B1%DB%8C-%D8%A7%D8%B7%D9%84%D8%A7%D8%B9%D8%A7%D8%AA-%D9%82%D9%82%D9%86%D9%88%D8%B3-2.png

962 ms

%D9%BE%DB%8C%D9%85%D8%A7%D9%86.png

%D9%BE%DB%8C%D9%85%D8%A7%D9%86.png

978 ms

Path-19.svg

Path-19.svg

1006 ms

%D8%AF%D8%B1%D8%A8%D8%A7%D8%B1%D9%87-%D9%82%D9%82%D9%86%D9%88%D8%B3.png

%D8%AF%D8%B1%D8%A8%D8%A7%D8%B1%D9%87-%D9%82%D9%82%D9%86%D9%88%D8%B3.png

3199 ms

%D8%A7%D8%B1%D8%B2%DB%8C%D8%A7%D8%A8%DB%8C.jpg

%D8%A7%D8%B1%D8%B2%DB%8C%D8%A7%D8%A8%DB%8C.jpg

1138 ms

%D8%AA%D8%A7%DB%8C%DB%8C%D8%AF-%D8%B5%D9%84%D8%A7%D8%AD%DB%8C%D8%AA.jpg

%D8%AA%D8%A7%DB%8C%DB%8C%D8%AF-%D8%B5%D9%84%D8%A7%D8%AD%DB%8C%D8%AA.jpg

1066 ms

%D9%85%D9%86%D8%A7%D9%82%D8%B5%D9%87.jpg

%D9%85%D9%86%D8%A7%D9%82%D8%B5%D9%87.jpg

1394 ms

footer-1-.svg

footer-1-.svg

1209 ms

%D9%87%D8%B1%D9%85%D8%B2%DA%AF%D8%A7%D9%86.png

%D9%87%D8%B1%D9%85%D8%B2%DA%AF%D8%A7%D9%86.png

1201 ms

iranyekanwebextrablackfanum.woff

iranyekanwebextrablackfanum.woff

1364 ms

iranyekanwebregularfanum.woff

iranyekanwebregularfanum.woff

1347 ms

iranyekanwebmediumfanum.woff

iranyekanwebmediumfanum.woff

1403 ms

iranyekanweblightfanum.woff

iranyekanweblightfanum.woff

1455 ms

iranyekanwebthinfanum.woff

iranyekanwebthinfanum.woff

1493 ms

iranyekanwebboldfanum.woff

iranyekanwebboldfanum.woff

1429 ms

iranyekanwebextraboldfanum.woff

iranyekanwebextraboldfanum.woff

1465 ms

iranyekanwebblackfanum.woff

iranyekanwebblackfanum.woff

1477 ms

auxin-front.woff

auxin-front.woff

1648 ms

element-pack.ttf

element-pack.ttf

1486 ms

%DA%AF%D8%A7%D8%B2-%D8%A7%D8%B5%D9%81%D9%87%D8%A7%D9%86.jpg

%DA%AF%D8%A7%D8%B2-%D8%A7%D8%B5%D9%81%D9%87%D8%A7%D9%86.jpg

1475 ms

%D8%B3%D9%88%D8%AF%DB%8C%DA%A9%D9%88-150x130-1.png

%D8%B3%D9%88%D8%AF%DB%8C%DA%A9%D9%88-150x130-1.png

1479 ms

%D8%A8%D8%B1%D9%82-%D8%A7%D8%B5%D9%81%D9%87%D8%A7%D9%86.png

%D8%A8%D8%B1%D9%82-%D8%A7%D8%B5%D9%81%D9%87%D8%A7%D9%86.png

1508 ms

%D9%86%D9%81%D8%AA-%D9%88-%DA%AF%D8%A7%D8%B2-%D8%A2%D8%BA%D8%A7%D8%AC%D8%A7%D8%B1%DB%8C-2.png

%D9%86%D9%81%D8%AA-%D9%88-%DA%AF%D8%A7%D8%B2-%D8%A2%D8%BA%D8%A7%D8%AC%D8%A7%D8%B1%DB%8C-2.png

1554 ms

%D8%AF%D9%85%D9%88-1.jpg

%D8%AF%D9%85%D9%88-1.jpg

1529 ms

footer-2-2.svg

footer-2-2.svg

1548 ms

footer-1-1-2.svg

footer-1-1-2.svg

1536 ms

%D9%85%D8%AC%D9%88%D8%B2-%D9%86%D8%B8%D8%A7%D9%85-%D8%B5%D9%86%D9%81%DB%8C-1.png

%D9%85%D8%AC%D9%88%D8%B2-%D9%86%D8%B8%D8%A7%D9%85-%D8%B5%D9%86%D9%81%DB%8C-1.png

1569 ms

symbols.svg

symbols.svg

1407 ms

yH5BAEAAAAALAAAAAABAAEAAAIBRAA7

yH5BAEAAAAALAAAAAABAAEAAAIBRAA7

2549 ms

Accessibility Review

phx.ir accessibility score

88

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

phx.ir best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

phx.ir SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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

phx.ir

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