36.6 sec in total
5.1 sec
28.4 sec
3 sec
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.irWe 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.
phx.ir performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value13.1 s
0/100
25%
Value15.8 s
0/100
10%
Value380 ms
70/100
30%
Value0
100/100
15%
Value31.9 s
0/100
10%
5145 ms
166 ms
492 ms
498 ms
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 size can be reduced by 225.3 kB (2%)
9.6 MB
9.4 MB
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.
Potential reduce by 107.5 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.
Potential reduce by 3.6 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. Phx images are well optimized though.
Potential reduce by 18.3 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.
Potential reduce by 95.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. 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.
Number of requests can be reduced by 52 (69%)
75
23
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.
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
fonts.css
510 ms
base.css
695 ms
auxin-icon.css
526 ms
main.css
979 ms
frontend-lite-rtl.min.css
665 ms
post-481.css
680 ms
elementor.css
704 ms
elementor-widgets.css
827 ms
mediaelementplayer-legacy.min.css
830 ms
wp-mediaelement.min.css
850 ms
post-514.css
869 ms
css
27 ms
custom.css
879 ms
go-pricing.css
1018 ms
post-513.css
1019 ms
post-493.css
1021 ms
css
42 ms
jquery.min.js
1214 ms
jquery-migrate.min.js
1053 ms
widgets.js
1141 ms
modernizr-custom.min.js
1158 ms
rtl.css
1169 ms
tippy.rtl.css
1190 ms
ep-font.rtl.css
1388 ms
ep-helpdesk.rtl.css
1388 ms
imagesloaded.min.js
1415 ms
masonry.min.js
1416 ms
plugins.min.js
2026 ms
widgets.js
1452 ms
mediaelement-and-player.min.js
1574 ms
mediaelement-migrate.min.js
1465 ms
wp-mediaelement.min.js
1487 ms
plugins.min.js
1498 ms
scripts.js
1561 ms
scripts.min.js
1473 ms
jquery-numerator.min.js
1164 ms
pro-tools.js
1172 ms
custom.js
1232 ms
bdt-uikit.min.js
1400 ms
webpack.runtime.min.js
1138 ms
frontend-modules.min.js
1156 ms
waypoints.min.js
1154 ms
core.min.js
1217 ms
frontend.min.js
1262 ms
ep-wrapper-link.min.js
1163 ms
popper.min.js
1168 ms
tippy.all.min.js
1253 ms
ep-tooltip.min.js
1235 ms
ep-helpdesk.min.js
1249 ms
helper.min.js
1138 ms
logo.aspx
20332 ms
logo.aspx
1437 ms
%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
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
962 ms
%D9%BE%DB%8C%D9%85%D8%A7%D9%86.png
978 ms
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
3199 ms
%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
1066 ms
%D9%85%D9%86%D8%A7%D9%82%D8%B5%D9%87.jpg
1394 ms
footer-1-.svg
1209 ms
%D9%87%D8%B1%D9%85%D8%B2%DA%AF%D8%A7%D9%86.png
1201 ms
iranyekanwebextrablackfanum.woff
1364 ms
iranyekanwebregularfanum.woff
1347 ms
iranyekanwebmediumfanum.woff
1403 ms
iranyekanweblightfanum.woff
1455 ms
iranyekanwebthinfanum.woff
1493 ms
iranyekanwebboldfanum.woff
1429 ms
iranyekanwebextraboldfanum.woff
1465 ms
iranyekanwebblackfanum.woff
1477 ms
auxin-front.woff
1648 ms
element-pack.ttf
1486 ms
%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
1479 ms
%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
1554 ms
%D8%AF%D9%85%D9%88-1.jpg
1529 ms
footer-2-2.svg
1548 ms
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
1569 ms
symbols.svg
1407 ms
yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
2549 ms
phx.ir accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
phx.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
phx.ir SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
FA
FA
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.
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: