Your Website Score is
SEO Rank : 2 Website URL: upga.ir Last Updated: 8 months
Success
24% of passed verification steps
Warning
23% of total warning
Errors
53% of total errors, require fast action
Share
Estimation Traffic and Earnings
121
Unique Visits
Daily
223
Pages Views
Daily
$0
Income
Daily
3,388
Unique Visits
Monthly
6,356
Pages Views
Monthly
$0
Income
Monthly
39,204
Unique Visits
Yearly
74,928
Pages Views
Yearly
$0
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
11 Characters
اروم کشاورز
Meta Description
0 Characters
NO DATA
Effective URL
14 Characters
http://upga.ir
Excerpt
Page content
اروم کشاورز
صفحه نخست
درباره ما
...
Google Preview
Your look like this in google search result
اروم کشاورز
http://upga.ir
اروم کشاورز
صفحه نخست
درباره ما
...
Robots.txt
File Detected
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~28.61 KB
Code Size: ~18.89 KB
Text Size: ~9.72 KB Ratio: 33.99%
Social Data
Desktop
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid long main-thread tasks
3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve images in next-gen formats
Potential savings of 593 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
Avoids an excessive DOM size
322 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)
First Meaningful Paint
0.8 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid chaining critical requests
11 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
Remove unused JavaScript
Potential savings of 42 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Properly size images
Potential savings of 4 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Eliminate render-blocking resources
Potential savings of 580 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Remove unused CSS
Potential savings of 18 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
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
JavaScript execution time
0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint
1.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Cumulative Layout Shift
0.009
Cumulative Layout Shift measures the movement of visible elements within the viewport
Defer offscreen images
Potential savings of 478 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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
Efficiently encode images
Potential savings of 267 KiB
Optimized images load faster and consume less cellular data
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
Reduce initial server response time
Root document took 940 ms
Keep the server response time for the main document short because all other requests depend on it
Keep request counts low and transfer sizes small
60 requests • 1,144 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
First Contentful Paint
0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Time to Interactive
0.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Serve static assets with an efficient cache policy
37 resources found
A long cache lifetime can speed up repeat visits to your page
Does not use HTTPS
53 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 CPU Idle
0.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/).
Avoids enormous network payloads
Total size was 1,144 KiB
Large network payloads cost users real money and are highly correlated with long load times
Max Potential First Input Delay
50 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Speed Index
2.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
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
Total Blocking Time
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Mobile
Avoid chaining critical requests
6 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
Keep request counts low and transfer sizes small
20 requests • 339 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Meaningful Paint
2.0 s
First Meaningful Paint measures when the primary content of a page is visible
JavaScript execution time
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images
Potential savings of 5 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Includes front-end JavaScript libraries with known security vulnerabilities
7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Serve static assets with an efficient cache policy
13 resources found
A long cache lifetime can speed up repeat visits to your page
Eliminate render-blocking resources
Potential savings of 1,150 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Does not use HTTPS
20 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
Minimizes main-thread work
1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First CPU Idle
2.0 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/).
Avoids enormous network payloads
Total size was 339 KiB
Large network payloads cost users real money and are highly correlated with long load times
Efficiently encode images
Potential savings of 28 KiB
Optimized images load faster and consume less cellular data
Avoids an excessive DOM size
588 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,710 ms
Keep the server response time for the main document short because all other requests depend on it
Serve images in next-gen formats
Potential savings of 125 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
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
Largest Contentful Paint
2.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Document uses legible font sizes
98.12% 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
First Contentful Paint (3G)
3906 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Avoid long main-thread tasks
3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Total Blocking Time
60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index
5.4 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
Remove unused JavaScript
Potential savings of 42 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Tap targets are not sized appropriately
81% 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
Time to Interactive
2.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
First Contentful Paint
2.0 s
First Contentful Paint marks the time at which the first text or image is painted
Max Potential First Input Delay
170 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Warning! Not 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
| First 20 Links | Relationship | HTTP Status |
| صفحه نخست | Internal Link | 200 |
| درباره ما | Internal Link | 404 |
| فروشگاه اینترنتی | Internal Link | 200 |
| مقالات | Internal Link | 404 |
| گالری عکس | Internal Link | 404 |
| گواهینامه ها | Internal Link | 404 |
| تماس با ما | Internal Link | 404 |
| قوانین | Internal Link | 404 |
| http://shop.upga.ir | Internal Link | 200 |
| http://shop.upga.ir/product-category/%D8%AC%D9%88%D8%AC%D9%87-%DA%A9%D8%B4%DB%8C-%D9%88-%D9%84%D9%88%D8%A7%D8%B2%D9%85-%D9%85%D8%B1%D8%BA%D8%AF%D8%A7%D8%B1%DB%8C | Internal Link | 404 |
| فروشگاه اروم کشاورز | Internal Link | 404 |
| آشنایی با خواص و مضرات قارچ | Internal Link | 404 |
| اصول ضدعفونی خاک پوششی | Internal Link | 404 |
| روش بسته بندی قارچ | Internal Link | 404 |
| پرورش قارچ(مقاله) | Internal Link | 404 |
| آموزش قارچ خوراکی و کمپوست | Internal Link | 404 |
| http://upga.ir/products/81-آیس-بانک-و-آیس-سیلوها.html | Internal Link | 404 |
| http://upga.ir/products/72-ایرواشر-مدل-NT.html | Internal Link | 404 |
| http://upga.ir/products/71-ایرکولر-مدل-NTA_24.html | Internal Link | 404 |
| http://upga.ir/products/70-ایرواشر.html | Internal Link | 404 |
Alexa Rank
96,120
Local Rank: IR / Users: 100.0% / PageViews: 100.0%2,573,501
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| upga.co | Available Buy Now! |
| upga.us | Available Buy Now! |
| upga.com | Already Registered |
| upga.org | Already Registered |
| upga.net | Already Registered |
| uga.ir | Available Buy Now! |
| npga.ir | Available Buy Now! |
| jpga.ir | Available Buy Now! |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Server: nginx
Date: Fri, 14 Aug 2020 22:39:22 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Set-Cookie: PHPSESSID=de49b2049a409f21d3f5615c2fb8cc34; path=/; domain=.upga.ir; HttpOnly
Set-Cookie: dle_user_id=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.upga.ir; HttpOnly
Set-Cookie: dle_password=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.upga.ir; HttpOnly
Set-Cookie: dle_hash=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=.upga.ir; HttpOnly
Vary: User-Agent
Content-Encoding: gzip
Click to Add/Show Comments