5.9 sec in total
615 ms
5 sec
227 ms
Visit lidobin.ir now to see the best up-to-date Lidobin content for Iran and also check out these interesting facts you probably never knew about lidobin.ir
بانک اطلاعات ساختمانهای درحال ساخت لیدوبین به معرفی پروژه های ساختمانی در حال ساخت تهران، شماره تلفن سازندگان ساختمان تهران، بازاریابی محصولات ساختمانی و بانک اطلاعات ساختمان های درحال ساخت تهران می پ...
Visit lidobin.irWe analyzed Lidobin.ir page load time and found that the first response time was 615 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
lidobin.ir performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value11.8 s
0/100
25%
Value9.3 s
12/100
10%
Value830 ms
35/100
30%
Value0.129
82/100
15%
Value11.7 s
17/100
10%
615 ms
1031 ms
662 ms
810 ms
678 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 80% of them (85 requests) were addressed to the original Lidobin.ir, 8% (9 requests) were made to Cdn.datatables.net and 3% (3 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Lidobin.ir.
Page size can be reduced by 2.3 MB (44%)
5.3 MB
3.0 MB
In fact, the total size of Lidobin.ir main page is 5.3 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. 55% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 79.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. This page needs HTML code to be minified as it can gain 21.1 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 79.3 kB or 84% of the original size.
Potential reduce by 1.7 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. Obviously, Lidobin needs image optimization as it can save up to 1.7 MB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 217.2 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 217.2 kB or 62% of the original size.
Potential reduce by 304.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. Lidobin.ir needs all CSS files to be minified and compressed as it can save up to 304.4 kB or 89% of the original size.
Number of requests can be reduced by 43 (44%)
98
55
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lidobin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
lidobin.ir
615 ms
lidobin.ir
1031 ms
jquery-3.5.1.min.js
662 ms
jquery.nivo.slider.js
810 ms
jquery.pnotify.min.js
678 ms
Message.js
676 ms
MyScript.js
678 ms
Function.js
705 ms
multiple-select.css
830 ms
jquery.multiple.select.js
1014 ms
MyStyle.css
846 ms
default.css
846 ms
nivo-slider.css
881 ms
jquery.pnotify.default.css
973 ms
jquery.pnotify.default.icons.css
995 ms
icons.css
1352 ms
styleTest.css
1025 ms
basic.css
1057 ms
galleriffic-1.css
1135 ms
style.css
1164 ms
bootstrap.min.css
62 ms
font-awesome.min.css
76 ms
icon
46 ms
popper.min.js
58 ms
bootstrap.min.js
82 ms
rd-navbar.css
1350 ms
jquery.rd-navbar.min.js
1186 ms
jquery.dataTables.min.css
52 ms
responsive.dataTables.min.css
71 ms
buttons.dataTables.min.css
71 ms
jquery.dataTables.min.js
79 ms
dataTables.buttons.min.js
72 ms
dataTables.responsive.min.js
100 ms
buttons.flash.min.js
107 ms
pdfmake.min.js
118 ms
buttons.html5.min.js
87 ms
buttons.print.min.js
83 ms
jszip.min.js
68 ms
dataTableCustomeStyle.css
1232 ms
Font.css
1297 ms
pdfmake.min.js
87 ms
WebResource.axd
1174 ms
ScriptResource.axd
1204 ms
ScriptResource.axd
1504 ms
ScriptResource.axd
1314 ms
fontiran.css
340 ms
1303 ms
loading.gif
200 ms
payment_user_icon.jpg
203 ms
payment_username_icon.jpg
227 ms
payment_tell_icon.jpg
222 ms
payment_payment_icon.jpg
217 ms
payment_desc_icon.jpg
244 ms
logo_mobile.png
365 ms
logo.png
537 ms
icon2.jpg
393 ms
icon3.jpg
390 ms
BSlid.png
387 ms
L20198044141150287232019804414115028723S_slide-(1).jpg
413 ms
L20198044142322163082019804414232216308S_slide-(3).jpg
531 ms
L20198044144872237812019804414487223781S1.jpg
549 ms
search_icon.jpg
559 ms
L_free-dl.jpg
570 ms
city.jpg
582 ms
newlater-text.png
696 ms
L2021301015305898002420213010153058980024s_DSCF1572.jpg
706 ms
L2021301015305882486820213010153058824868l_DSCF1572.jpg
1030 ms
L2021301015248705512820213010152487055128s_DSCF1359.jpg
727 ms
L2021301015248689924820213010152486899248l_DSCF1359.jpg
1093 ms
L2021301015230827033520213010152308270335s_DSCF1333.jpg
750 ms
L2021301015230827033520213010152308270335l_DSCF1333.jpg
1026 ms
L2021301015209212897120213010152092128971s_DSCF1303.jpg
875 ms
L2021301015209197258320213010152091972583l_DSCF1303.jpg
1397 ms
L2021301014926226415520213010149262264155s_DSCF1263.jpg
918 ms
L2021301014926210790320213010149262107903l_DSCF1263.jpg
1214 ms
L2021301014907782248620213010149077822486s_DSCF1128.jpg
1088 ms
L2021301014907766649020213010149077666490l_DSCF1128.jpg
1198 ms
L2021301014850842380720213010148508423807s_DSCF1125.jpg
1195 ms
L2021301014850826767620213010148508267676l_DSCF1125.jpg
1593 ms
L2021301014832335303520213010148323353035s_DSCF1120.jpg
1269 ms
L2021301014832304020320213010148323040203l_DSCF1120.jpg
1361 ms
S2018611103217download.jpg
1365 ms
S201831122817download.jpg
1359 ms
analytics.js
71 ms
collect
12 ms
iranyekanwebregular(fanum).woff
1258 ms
js
61 ms
iranyekanweblight(fanum).woff
1324 ms
iranyekanwebbold(fanum).woff
1320 ms
S201831122440images.jpg
1341 ms
fix_support.png
1343 ms
fix_Payement.jpg
1389 ms
header_bg.jpg
1327 ms
header_image.png
1315 ms
left_Content.png
1334 ms
sliderBg.png
1346 ms
bg_cap_pro.jpg
1352 ms
news-ticker_bg.jpg
1279 ms
bg_footer_main.jpg
1317 ms
txtBox_bg.png
1319 ms
bg_projectitems.png
1334 ms
project-popup.png
1338 ms
footer_bg.png
1352 ms
bg_contentMain.jpg
1292 ms
user.png
1308 ms
L20198044141151849112019804414115184911S_slide-(1).jpg
1307 ms
lidobin.ir accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
lidobin.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
lidobin.ir SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lidobin.ir can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lidobin.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.
lidobin.ir
Open Graph description is not detected on the main page of Lidobin. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: