13 sec in total
898 ms
10.9 sec
1.1 sec
Welcome to fgn11.ir homepage info - get ready to check Fgn 11 best content for Iran right away, or after learning these important things about fgn11.ir
اجرای عایق کاری و آب بندی استخر, جکوزی پشت بام فلاورباکس آبنما با فایبرگلاس تضمینی
Visit fgn11.irWe analyzed Fgn11.ir page load time and found that the first response time was 898 ms and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fgn11.ir performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value11.9 s
0/100
25%
Value17.1 s
0/100
10%
Value2,790 ms
3/100
30%
Value0.18
67/100
15%
Value23.3 s
1/100
10%
898 ms
713 ms
4026 ms
168 ms
333 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Fgn11.ir, 82% (93 requests) were made to Frpst.com and 6% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source Frpst.com.
Page size can be reduced by 273.9 kB (15%)
1.8 MB
1.5 MB
In fact, the total size of Fgn11.ir main page is 1.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. 70% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 160.1 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 160.1 kB or 82% of the original size.
Potential reduce by 83.8 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. Fgn 11 images are well optimized though.
Potential reduce by 14.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. This website has mostly compressed JavaScripts.
Potential reduce by 15.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. Fgn11.ir needs all CSS files to be minified and compressed as it can save up to 15.6 kB or 12% of the original size.
Number of requests can be reduced by 79 (91%)
87
8
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fgn 11. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 46 to 1 for CSS and as a result speed up the page load time.
fgn11.ir
898 ms
fgn11.ir
713 ms
frpst.com
4026 ms
mediaelementplayer-legacy.min.css
168 ms
wp-mediaelement.min.css
333 ms
blocks.css
489 ms
v4-shims.min.css
493 ms
all.min.css
497 ms
czicons.css
500 ms
rtl-xtra-front.css
502 ms
styles.css
509 ms
styles-rtl.css
649 ms
plyr.css
656 ms
kk-star-ratings.min.css
661 ms
style.css
664 ms
style.css
665 ms
core.css
853 ms
core.rtl.css
811 ms
css
32 ms
share.css
819 ms
mobile-nav.css
825 ms
codevzplus.css
831 ms
frontend-lite-rtl.min.css
1003 ms
swiper.min.css
973 ms
post-2174.css
982 ms
global.css
989 ms
post-1976.css
996 ms
elementor.css
1021 ms
css
46 ms
plyr.js
1301 ms
jquery.min.js
1313 ms
jquery-migrate.min.js
1153 ms
widget-icon-list-rtl.min.css
1159 ms
post-2011.css
1164 ms
testimonials.css
1188 ms
parallax.css
1417 ms
testimonials.rtl.css
1418 ms
show_more_less.css
1419 ms
post-2012.css
1421 ms
gallery.css
1616 ms
e-202434.js
16 ms
tilt.css
1616 ms
carousel.css
1547 ms
gallery.rtl.css
1382 ms
post-1637.css
1228 ms
animations.min.css
1223 ms
separator.css
1217 ms
title.css
1218 ms
title.rtl.css
1328 ms
hooks.min.js
1475 ms
i18n.min.js
1208 ms
index.js
1203 ms
index.js
1199 ms
kk-star-ratings.min.js
1194 ms
tracker.js
1615 ms
codevz-menu.min.js
1469 ms
custom.js
1462 ms
codevzplus.js
1456 ms
codevzplus.rtl.js
1453 ms
share.js
1431 ms
mobile-nav.js
1471 ms
parallax.js
1463 ms
show_more_less.js
1455 ms
gallery.js
1449 ms
carousel.js
1433 ms
tilt.js
1415 ms
separator.js
1448 ms
title.js
1442 ms
image.js
1432 ms
elementor.js
1410 ms
webpack.runtime.min.js
1300 ms
frontend-modules.min.js
1181 ms
waypoints.min.js
1316 ms
core.min.js
1319 ms
frontend.min.js
1320 ms
%D8%B9%D8%A7%DB%8C%D9%82-%DA%A9%D8%A7%D8%B1%DB%8C-%D8%A7%D8%B3%D8%AA%D8%AE%D8%B1-%D8%A8%D8%A7-%D9%81%D8%A7%DB%8C%D8%A8%D8%B1%DA%AF%D9%84%D8%A7%D8%B3-.webp
1454 ms
IRANSansWebFaNum.woff
1124 ms
test-back.png
349 ms
IRANSansWebFaNum_Medium.woff
1171 ms
IRANSansWebFaNum_Light.woff
1536 ms
IRANSansWebFaNum_UltraLight.woff
1536 ms
IRANSansWebFaNum_Bold.woff
1535 ms
IRANSansWebFaNum_Black.woff
1531 ms
embed
576 ms
Shabnam.woff
1530 ms
zrfl0HLVx-HwTP82Yaf4Jg.ttf
255 ms
Shabnam-Bold.woff
1517 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
255 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
561 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
562 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
563 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
562 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
563 ms
Lalezar-Regular.woff
1575 ms
fa-solid-900.woff
1395 ms
fa-regular-400.woff
1391 ms
fa-brands-400.woff
1571 ms
inactive.svg
1268 ms
active.svg
1269 ms
js
158 ms
geometry.js
26 ms
search.js
61 ms
main.js
60 ms
lazyload-8.15.2.min.js
684 ms
slide-3.jpg
454 ms
logo-fgn11.ir_.webp
176 ms
He75647a6e2e042f6bc4bb9ecfd82f9685-2.jpg
830 ms
glass-wall-pool-design-5ccdd5b806737.9G2I9-850x550-1.png
853 ms
logo-fgn11.ir_.webp
29 ms
core-laptop.css
167 ms
core-tablet.css
168 ms
core-mobile.css
167 ms
codevzplus-tablet.css
167 ms
codevzplus-mobile.css
167 ms
fgn11.ir accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
fgn11.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fgn11.ir SEO score
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 Fgn11.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 Fgn11.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.
fgn11.ir
Open Graph data is detected on the main page of Fgn 11. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: