34.7 sec in total
4.9 sec
28.3 sec
1.6 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 4.9 sec and then it took 29.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% 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.8 s
5/100
10%
Value24.4 s
0/100
25%
Value19.5 s
0/100
10%
Value450 ms
62/100
30%
Value0
100/100
15%
Value20.2 s
2/100
10%
4864 ms
183 ms
363 ms
513 ms
521 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 97% of them (105 requests) were addressed to the original Phx.ir, 1% (1 request) 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.5 sec) relates to the external source Trustseal.enamad.ir.
Page size can be reduced by 1.7 MB (9%)
18.8 MB
17.1 MB
In fact, the total size of Phx.ir main page is 18.8 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. 65% of websites need less resources to load. Images take 17.8 MB which makes up the majority of the site volume.
Potential reduce by 128.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 128.4 kB or 81% of the original size.
Potential reduce by 1.3 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.
Potential reduce by 189.8 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 189.8 kB or 33% of the original size.
Potential reduce by 66.6 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 66.6 kB or 26% of the original size.
Number of requests can be reduced by 55 (61%)
90
35
The browser has sent 90 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 32 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
phx.ir
4864 ms
bdt-uikit.rtl.css
183 ms
ep-helper.rtl.css
363 ms
fonts.css
513 ms
screen.min.css
521 ms
base.css
693 ms
auxin-icon.css
524 ms
main.css
1067 ms
frontend-lite-rtl.min.css
542 ms
swiper.min.css
682 ms
post-481.css
702 ms
elementor.css
703 ms
elementor-widgets.css
722 ms
mediaelementplayer-legacy.min.css
852 ms
wp-mediaelement.min.css
866 ms
post-514.css
873 ms
custom.css
879 ms
go-pricing.css
902 ms
post-513.css
1022 ms
post-493.css
1040 ms
modern.css
1045 ms
css
33 ms
jquery.min.js
1229 ms
jquery-migrate.min.js
1110 ms
widgets.js
1191 ms
sosApi.js
1214 ms
modernizr-custom.min.js
1219 ms
rtl.css
1302 ms
tippy.rtl.css
1339 ms
ep-font.rtl.css
1444 ms
ep-helpdesk.rtl.css
1444 ms
imagesloaded.min.js
1476 ms
masonry.min.js
1476 ms
plugins.min.js
1611 ms
scripts.min.js
1477 ms
widgets.js
1530 ms
mediaelement-and-player.min.js
1736 ms
mediaelement-migrate.min.js
1566 ms
wp-mediaelement.min.js
1403 ms
plugins.min.js
1282 ms
scripts.js
1196 ms
jquery-numerator.min.js
1240 ms
pro-tools.js
1238 ms
front.min.js
1252 ms
tracker.js
1118 ms
custom.js
1177 ms
bdt-uikit.min.js
1220 ms
webpack.runtime.min.js
1222 ms
frontend-modules.min.js
1219 ms
waypoints.min.js
1127 ms
core.min.js
1112 ms
frontend.min.js
1174 ms
ep-wrapper-link.min.js
1218 ms
popper.min.js
1203 ms
tippy.all.min.js
1096 ms
ep-tooltip.min.js
1115 ms
ep-helpdesk.min.js
1113 ms
helper.min.js
1110 ms
logo.aspx
20459 ms
logo.aspx
868 ms
%D9%82%D9%82%D9%86%D9%88%D8%B3-%D9%84%D9%88%DA%AF%D9%88.png
989 ms
%D8%AA%D8%A7%D9%85%DB%8C%D9%86-%DA%A9%D9%86%D9%86%D8%AF%DA%AF%D8%A7%D9%86.jpg
1863 ms
%D9%BE%DB%8C%D9%85%D8%A7%D9%86%DA%A9%D8%A7%D8%B1%D8%A7%D9%86.jpg
2132 ms
%D8%B3%D8%A7%D9%85%D8%A7%D9%86%D9%87-%D9%BE%DB%8C%D9%85%D8%A7%D9%86.jpg
1401 ms
%D9%BE%DB%8C%D9%85%D8%A7%D9%86.png
1049 ms
Path-19.svg
3650 ms
%D8%AF%D8%B1%D8%A8%D8%A7%D8%B1%D9%87-%D9%82%D9%82%D9%86%D9%88%D8%B3.png
2758 ms
%D8%A7%D8%B1%D8%B2%DB%8C%D8%A7%D8%A8%DB%8C.jpg
1405 ms
%D8%AA%D8%A7%DB%8C%DB%8C%D8%AF-%D8%B5%D9%84%D8%A7%D8%AD%DB%8C%D8%AA.jpg
1589 ms
%D9%85%D9%86%D8%A7%D9%82%D8%B5%D9%87.jpg
1770 ms
iranyekanwebextrablackfanum.woff
1864 ms
iranyekanwebregularfanum.woff
1910 ms
iranyekanwebmediumfanum.woff
1952 ms
iranyekanweblightfanum.woff
2021 ms
iranyekanwebthinfanum.woff
2009 ms
iranyekanwebboldfanum.woff
2074 ms
iranyekanwebextraboldfanum.woff
2055 ms
iranyekanwebblackfanum.woff
2091 ms
auxin-front.woff
2125 ms
element-pack.ttf
2186 ms
%D8%AE%D8%A7%D8%B1%DA%A9.png
2214 ms
%D8%B2%D8%A7%DA%AF%D8%B1%D8%B3.png
2242 ms
%D9%BE%D8%AA%D8%B1%D9%88%D8%B4%DB%8C%D9%85%DB%8C-%D9%85%D8%B3%D8%AC%D8%AF-%D8%B3%D9%84%DB%8C%D9%85%D8%A7%D9%86-1.png
2182 ms
%D9%85%DA%AF%D8%A7-%D9%85%D9%88%D8%AA%D9%88%D8%B1.png
2187 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
2253 ms
%D8%B3%D9%88%D8%AF%DB%8C%DA%A9%D9%88-150x130-1.png
2277 ms
%DA%AF%D8%A7%D8%B2.png
2263 ms
%D9%87%D8%B1%D9%85%D8%B2%DA%AF%D8%A7%D9%86.png
2305 ms
%D8%A8%D8%B1%D9%82-%D8%A7%D8%B5%D9%81%D9%87%D8%A7%D9%86.png
2306 ms
%D8%B4%D9%87%D8%B1%D8%B3%D8%AA%D8%A7%D9%86.png
2294 ms
%DA%A9%D8%B1%D9%85%D8%A7%D9%86.png
2302 ms
%D8%A8%D8%B1%D9%82-%DA%86%D9%87%D8%A7%D8%B1%D9%85%D8%AD%D8%A7%D9%84.png
2303 ms
%D8%AE%D8%B1%D8%A7%D8%B3%D8%A7%D9%86-%D8%B4%D9%85%D8%A7%D9%84%DB%8C.png
2310 ms
%D9%84%D8%B1%D8%B3%D8%AA%D8%A7%D9%86.png
2377 ms
%D9%87%D8%B1%D9%85%D8%B2%DA%AF%D8%A7%D9%86.png
2331 ms
%D8%A2%D9%85%D9%88%D8%B2%D8%B4-%D9%85%D9%86%D8%A7%D9%82%D8%B5%D9%87-%D9%87%D8%A7-%D9%88-%D9%85%D8%B2%D8%A7%DB%8C%D8%AF%D9%87-%D9%87%D8%A7.jpg
2301 ms
%D8%A7%D8%AE%D9%84%D8%A7%D9%82-%D8%AF%D8%B1-%D9%85%D9%86%D8%A7%D9%82%D8%B5%D8%A7%D8%AA-%D9%88-%D9%85%D8%B2%D8%A7%DB%8C%D8%AF%D9%87-%D9%87%D8%A7.jpg
2219 ms
%D8%A7%D8%B1%D8%B2%DB%8C%D8%A7%D8%A8%DB%8C-%D8%B9%D9%85%D9%84%DA%A9%D8%B1%D8%AF-%D9%BE%DB%8C%D9%85%D8%A7%D9%86%DA%A9%D8%A7%D8%B1%D8%A7%D9%86.jpg
1946 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
1831 ms
%D9%85%D8%AD%D8%B1%D9%85.png
2888 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
1598 ms
footer-1-.svg
4289 ms
%D8%AF%D9%85%D9%88-1.jpg
1447 ms
footer-2-2.svg
3925 ms
footer-1-1-2.svg
5432 ms
symbols.svg
1451 ms
yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
5304 ms
%D8%B4%D9%81%D8%A7%D9%81-%D8%B3%D8%A7%D8%B2%DB%8C-150x150.png
178 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
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: