Your Website Score is
SEO Rank : 2 Website URL: imed.ir Last Updated: 7 months
Success
39% of passed verification steps
Warning
23% of total warning
Errors
38% of total errors, require fast action
Share
Estimation Traffic and Earnings
3,923
Unique Visits
Daily
7,257
Pages Views
Daily
$16
Income
Daily
109,844
Unique Visits
Monthly
206,825
Pages Views
Monthly
$400
Income
Monthly
1,271,052
Unique Visits
Yearly
2,438,352
Pages Views
Yearly
$4,224
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 0%
Domain Authority
Domain Authority 0%
Moz Rank
0.0/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
27 Characters
اداره کل تجهيزات پزشکی
Meta Description
22 Characters
اداره کل تجهيزات پزشکی
Effective URL
14 Characters
http://imed.ir
Excerpt
Page content
اداره کل تجهيزات پزشکی
...
Meta Keywords
1 Detected
Google Preview
Your look like this in google search result
اداره کل تجهيزات پزشکی
http://imed.ir
اداره کل تجهيزات پزشکی
Robots.txt
File Detected
Sitemap.xml
File Detected
Page Size
Code & Text Ratio
Document Size: ~218.93 KB
Code Size: ~148.59 KB
Text Size: ~70.34 KB Ratio: 32.13%
Social Data
Desktop
Serve images in next-gen formats
Potential savings of 3,394 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
First CPU Idle
1.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Keep request counts low and transfer sizes small
110 requests • 4,766 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
JavaScript execution time
0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Serve static assets with an efficient cache policy
89 resources found
A long cache lifetime can speed up repeat visits to your page
Does not use HTTPS
97 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
First Contentful Paint
1.6 s
First Contentful Paint marks the time at which the first text or image is painted
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index
3.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Efficiently encode images
Potential savings of 2,791 KiB
Optimized images load faster and consume less cellular data
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Time to Interactive
1.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Minimizes main-thread work
0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Remove unused JavaScript
Potential savings of 42 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Minimize third-party usage
Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Eliminate render-blocking resources
Potential savings of 140 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Cumulative Layout Shift
0.349
Cumulative Layout Shift measures the movement of visible elements within the viewport
Remove unused CSS
Potential savings of 71 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Estimated Input Latency
10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Largest Contentful Paint
4.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Use video formats for animated content
Potential savings of 122 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Avoid enormous network payloads
Total size was 4,766 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minify CSS
Potential savings of 7 KiB
Minifying CSS files can reduce network payload sizes
Properly size images
Potential savings of 2,790 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
First Meaningful Paint
1.8 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid an excessive DOM size
993 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Reduce initial server response time
Root document took 1,740 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid chaining critical requests
37 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 15.4 s
A fast page load over a cellular network ensures a good mobile user experience
Max Potential First Input Delay
40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Mobile
Defer offscreen images
Potential savings of 319 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Serve images in next-gen formats
Potential savings of 3,394 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Cumulative Layout Shift
0.108
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid long main-thread tasks
10 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Reduce the impact of third-party code
Third-party code blocked the main thread for 270 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Tap targets are not sized appropriately
83% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Remove unused JavaScript
Potential savings of 42 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Does not use HTTPS
96 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
First Contentful Paint (3G)
9076 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
37 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Max Potential First Input Delay
220 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Eliminate render-blocking resources
Potential savings of 360 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Speed Index
10.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
JavaScript execution time
1.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Time to Interactive
16.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Efficiently encode images
Potential savings of 2,791 KiB
Optimized images load faster and consume less cellular data
First Contentful Paint
4.9 s
First Contentful Paint marks the time at which the first text or image is painted
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
First CPU Idle
5.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Keep request counts low and transfer sizes small
109 requests • 4,742 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Meaningful Paint
5.4 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid an excessive DOM size
993 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Reduce initial server response time
Root document took 1,510 ms
Keep the server response time for the main document short because all other requests depend on it
Use video formats for animated content
Potential savings of 122 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Minimize main-thread work
3.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Minify CSS
Potential savings of 6 KiB
Minifying CSS files can reduce network payload sizes
Document uses legible font sizes
86.87% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Serve static assets with an efficient cache policy
88 resources found
A long cache lifetime can speed up repeat visits to your page
Page load is not fast enough on mobile networks
Interactive at 16.6 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency
10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Remove unused CSS
Potential savings of 57 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Largest Contentful Paint
17.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Total Blocking Time
190 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Properly size images
Potential savings of 2,569 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid enormous network payloads
Total size was 4,742 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed And Optimization Tips
Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Warning! Your website is not SSL secured (HTTPS).
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Warning! You have broken links
View links
Alexa Rank
593
Local Rank: IR / Users: 89.6% / PageViews: 95.8%22,407
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| imed.co | Already Registered |
| imed.us | Already Registered |
| imed.com | Already Registered |
| imed.org | Already Registered |
| imed.net | Already Registered |
| ied.ir | Already Registered |
| mmed.ir | Already Registered |
| kmed.ir | Already Registered |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 58764
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
Vary: Accept-Encoding
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Set-Cookie: Language=1; path=/
Set-Cookie: Theme=Darya; path=/
Set-Cookie: cookiesession1=384DB1F4NG3DI443LAK7MZDZOBDQ8D87;Path=/;HttpOnly
Date: Fri, 07 Aug 2020 02:52:23 GMT
Click to Add/Show Comments