Force Web

Enter domain

← Click to update

faranesh.comآنالیز سئو سایت

 Generated on May 12 2018 18:25 PM

بروزرسانی آنالیز وبسایت قدیمی است؟ !

امتیاز سایت 36 از 100 میباشد

Download PDF Version

محتوای سئو


طول دامنه : 0

Very bad. We haven't found title on your page.

طول دامنه : 0

Very bad. We haven't found meta description on your page. Use this free online meta tags generator to create description.
کلمات کلیدی

Very bad. We haven't found meta keywords on your page. Use this free online meta tags generator to create keywords.
Og Meta Properties This page does not take advantage of Og Properties. This tags allows social crawler's better structurize your page. Use this free og properties generator to create them.
عنوان ها
H1 H2 H3 H4 H5 H6
0 0 0 0 0 0
عکس ها تعداد عکس در این صفحه وبسایت شما پیدا کردیم1

1 alt attributes are empty or missing. Add alternative text so that search engines can better understand the content of your images.
Text/HTML Ratio نسبت : 2%

This page's ratio of text to HTML code is below 15 percent, this means that your website probably needs more text content.
Flash Perfect, no Flash content has been detected on this page.
Iframe Great, there are no Iframes detected on this page.

بازنویسی آدرس سایت Good. Your links looks friendly!
خط زیر(_) در ادرس سایت وجود دارد Perfect! No underscores detected in your URLs.
لینک های صفحه We found a total of 0 links including 0 link(s) to files

Anchor نوع Juice

کلمات کلیدی سئو

کلمات کلیدی ابری
هماهنگی کلمات کلیدی
کلمه کلیدی محتوا عنوان کلمات کلیدی توضیحات عنوان ها

قابلیت استفاده

آدرس وبسایت دامنه :
طول دامنه : 12
نماد وبسایت(Favicon) Great, your website has a favicon.
نسخه قابل چاپ We could not find a Print-Friendly CSS.
زبان You have not specified the language. Use this free meta tags generator to declare the intended language of your website.
Dublin Core This page does not take advantage of Dublin Core.


Doctype HTML 5
Encoding Perfect. Your declared charset is UTF-8.
W3C Validity Errors : 1
Warnings : 8
Email Privacy Warning! At least one email address has been found in the plain text. Use free antispam protector to hide email from spammers.
Deprecated HTML Great! We haven't found deprecated HTML tags in your HTML.
Speed Tips
Excellent, your website doesn't use nested tables.
Too bad, your website is using inline styles.
Great, your website has few CSS files.
Perfect, your website has few JavaScript files.
Too bad, your website does not take advantage of gzip.


Mobile Optimization
Apple Icon
Meta Viewport Tag
Flash content


XML Sitemap Great, your website has an XML sitemap.

Great, your website has a robots.txt file.
Analytics Great, your website has an analytics tool.

   Google Analytics

PageSpeed Insights

43 / 100    Speed
  Should Fix:
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 4 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:


Optimize CSS Delivery of the following:

Show how to fix
Optimize images
Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 839.8KiB (58% reduction).

  • Compressing could save 188.9KiB (81% reduction).
  • Compressing could save 151.1KiB (76% reduction).
  • Compressing could save 67.4KiB (71% reduction).
  • Compressing could save 46.8KiB (69% reduction).
  • Compressing could save 44.7KiB (72% reduction).
  • Compressing could save 41.1KiB (51% reduction).
  • Compressing could save 39.7KiB (59% reduction).
  • Compressing could save 36.8KiB (46% reduction).
  • Compressing could save 36.4KiB (55% reduction).
  • Compressing could save 33.3KiB (80% reduction).
  • Compressing could save 30.9KiB (50% reduction).
  • Compressing could save 27.2KiB (30% reduction).
  • Compressing could save 25.4KiB (53% reduction).
  • Compressing could save 24.8KiB (29% reduction).
  • Compressing could save 18.2KiB (21% reduction).
  • Compressing could save 16.4KiB (41% reduction).
  • Compressing could save 8.6KiB (65% reduction).
  • Compressing could save 906B (13% reduction).
  • Compressing could save 831B (20% reduction).
  • Compressing could save 400B (32% reduction).
Show how to fix
  Consider Fixing:
Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 83.4KiB (81% reduction).

  • Compressing could save 71.4KiB (81% reduction).
  • Compressing could save 7.6KiB (82% reduction).
  • Compressing could save 4.5KiB (78% reduction).
Show how to fix
Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

  • (60 seconds)
  • (2 hours)
  • (3 hours)
Show how to fix
Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 409B (16% reduction).

  • Minifying could save 409B (16% reduction) after compression.
Show how to fix
  5 Passed Rules
Show details
Avoid landing page redirects

Your page has no redirects. Learn more about avoiding landing page redirects.

Reduce server response time

Your server responded quickly. Learn more about server response time optimization.

Minify CSS

Your CSS is minified. Learn more about minifying CSS.

Minify JavaScript

Your JavaScript content is minified. Learn more about minifying JavaScript.

Prioritize visible content

You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.

92 / 100    User Experience
  Consider Fixing:
Size content to viewport
The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 423 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

  • The element <div class="discountBadge…ter jus-center">۱۰% تخفیف</div> falls outside the viewport.
  • The element <div>وبلاگ فرانش…ه‌هاتماس با ما</div> falls outside the viewport.
Show how to fix
Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

  • The tap target <div class="categoryName selected">کسب‌وکار</div> is close to 1 other tap targets.
  • The tap target <div class="categoryName">وب</div> and 4 others are close to other tap targets.
  • The tap target <span>بد</span> and 39 others are close to other tap targets.
Show how to fix
  3 Passed Rules
Show details
Avoid plugins

Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.

Configure the viewport

Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.

Use legible font sizes

The text on your page is legible. Learn more about using legible font sizes.

* The results are cached for 30s. If you have made changes to your page, please wait for 30s before re-running the test.