Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

nanaz1391.niniweblog.com

نی نی وبلاگ | امیرمهدی کوچولو

Page Load Speed

11.1 sec in total

First Response

1.1 sec

Resources Loaded

7.4 sec

Page Rendered

2.6 sec

nanaz1391.niniweblog.com screenshot

About Website

Click here to check amazing Nanaz 1391 Niniweblog content for Germany. Otherwise, check out these important facts you probably never knew about nanaz1391.niniweblog.com

خداجونم دوستت دارم

Visit nanaz1391.niniweblog.com

Key Findings

We analyzed Nanaz1391.niniweblog.com page load time and found that the first response time was 1.1 sec and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

nanaz1391.niniweblog.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.314

37/100

15%

TTI (Time to Interactive)

Value7.8 s

45/100

10%

Network Requests Diagram

nanaz1391.niniweblog.com

1133 ms

style.css

188 ms

website.css

190 ms

jquery-1.4.2.min.js

282 ms

jquery.tinycircleslider.min.js

193 ms

Our browser made a total of 247 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Nanaz1391.niniweblog.com, 62% (154 requests) were made to Niniweblog.com and 16% (39 requests) were made to M-qaleb.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Sherv.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 359.5 kB (11%)

Content Size

3.4 MB

After Optimization

3.1 MB

In fact, the total size of Nanaz1391.niniweblog.com main page is 3.4 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. 60% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 97.5 kB

  • Original 114.5 kB
  • After minification 111.9 kB
  • After compression 17.0 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 97.5 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 164.4 kB

  • Original 3.1 MB
  • After minification 3.0 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. Nanaz 1391 Niniweblog images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 74.3 kB

  • Original 125.1 kB
  • After minification 119.5 kB
  • After compression 50.8 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 74.3 kB or 59% of the original size.

CSS Optimization

-79%

Potential reduce by 23.4 kB

  • Original 29.6 kB
  • After minification 25.6 kB
  • After compression 6.2 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. Nanaz1391.niniweblog.com needs all CSS files to be minified and compressed as it can save up to 23.4 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (24%)

Requests Now

169

After Optimization

129

The browser has sent 169 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nanaz 1391 Niniweblog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

nanaz1391.niniweblog.com accessibility score

82

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

nanaz1391.niniweblog.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

nanaz1391.niniweblog.com SEO score

71

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    FA

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nanaz1391.niniweblog.com can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it does not match the claimed English language. Our system also found out that Nanaz1391.niniweblog.com 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Nanaz 1391 Niniweblog. 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: