Tools & Wizards About Us
r111n.com screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

r111n.com

???? ????? ??? ???????

Page Load Speed

17.1 sec in total

First Response

284 ms

Resources Loaded

15.9 sec

Page Rendered

961 ms

r111n.com screenshot

About Website

Visit r111n.com now to see the best up-to-date R 111 N content for Saudi Arabia and also check out these interesting facts you probably never knew about r111n.com

????? ????? ??? ??????? ,???? ????? ???,???,????? ????? ???,????? ?????,????? ???,????? ??? ???????

Visit r111n.com

Key Findings

We analyzed R111n.com page load time and found that the first response time was 284 ms and then it took 16.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

r111n.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value18.7 s

0/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

Network Requests Diagram

r111n.com

284 ms

r111n.com

14066 ms

vbulletin_important.css

81 ms

yahoo-dom-event.js

21 ms

connection-min.js

25 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 94% of them (59 requests) were addressed to the original R111n.com, 3% (2 requests) were made to Ajax.googleapis.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (14.1 sec) belongs to the original domain R111n.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.1 kB (63%)

Content Size

197.3 kB

After Optimization

72.2 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of R111n.com main page is 197.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. HTML takes 138.0 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 121.3 kB

  • Original 138.0 kB
  • After minification 129.6 kB
  • After compression 16.7 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 121.3 kB or 88% of the original size.

JavaScript Optimization

-6%

Potential reduce by 3.3 kB

  • Original 57.9 kB
  • After minification 57.9 kB
  • After compression 54.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-37%

Potential reduce by 497 B

  • Original 1.3 kB
  • After minification 1.1 kB
  • After compression 842 B

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. R111n.com needs all CSS files to be minified and compressed as it can save up to 497 B or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (32%)

Requests Now

59

After Optimization

40

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

r111n.com

r111n.com

284 ms

r111n.com

r111n.com

14066 ms

vbulletin_important.css

vbulletin_important.css

81 ms

yahoo-dom-event.js

yahoo-dom-event.js

21 ms

connection-min.js

connection-min.js

25 ms

vbulletin_global.js

vbulletin_global.js

161 ms

vbulletin_menu.js

vbulletin_menu.js

236 ms

ncode_imageresizer.js

ncode_imageresizer.js

500 ms

jquery-1.2.6.min.js

jquery-1.2.6.min.js

319 ms

like_share_by_ali.js

like_share_by_ali.js

246 ms

like_share_by_ali.css

like_share_by_ali.css

249 ms

poem.js

poem.js

251 ms

gradient.js

gradient.js

250 ms

vbulletin_md5.js

vbulletin_md5.js

313 ms

vbulletin_read_marker.js

vbulletin_read_marker.js

322 ms

collapse_tcat.gif

collapse_tcat.gif

98 ms

navbits_start.gif

navbits_start.gif

100 ms

forum_old.gif

forum_old.gif

99 ms

icon1.gif

icon1.gif

97 ms

lastpost.gif

lastpost.gif

96 ms

subforum_old.gif

subforum_old.gif

99 ms

06.gif

06.gif

159 ms

new2.gif

new2.gif

161 ms

exll.gif

exll.gif

162 ms

new12.gif

new12.gif

230 ms

bb1.gif

bb1.gif

230 ms

collapse_thead.gif

collapse_thead.gif

231 ms

whos_online.gif

whos_online.gif

276 ms

stats.gif

stats.gif

276 ms

post_old.gif

post_old.gif

277 ms

forum_new.gif

forum_new.gif

277 ms

hd2.gif

hd2.gif

324 ms

hd1.gif

hd1.gif

665 ms

back3.gif

back3.gif

304 ms

back1.gif

back1.gif

389 ms

213.gif

213.gif

546 ms

246.gif

246.gif

567 ms

200.gif

200.gif

629 ms

498.gif

498.gif

575 ms

203.gif

203.gif

703 ms

236.gif

236.gif

706 ms

nav-ht.gif

nav-ht.gif

650 ms

nav-h1.gif

nav-h1.gif

660 ms

nav-h2.gif

nav-h2.gif

708 ms

nav-p1.gif

nav-p1.gif

733 ms

nav-p2.gif

nav-p2.gif

744 ms

nav-ft.gif

nav-ft.gif

677 ms

nav-f1.gif

nav-f1.gif

717 ms

nav-f2.gif

nav-f2.gif

718 ms

491.gif

491.gif

796 ms

DroidKufi-Bold.woff

DroidKufi-Bold.woff

75 ms

DroidKufi-Regular.woff

DroidKufi-Regular.woff

144 ms

221.gif

221.gif

818 ms

248.gif

248.gif

748 ms

223.gif

223.gif

750 ms

217.gif

217.gif

861 ms

229.gif

229.gif

793 ms

243.gif

243.gif

831 ms

476.gif

476.gif

775 ms

502.gif

502.gif

801 ms

235.gif

235.gif

812 ms

fotr2.gif

fotr2.gif

775 ms

fotr1.gif

fotr1.gif

787 ms

Accessibility Review

r111n.com accessibility score

75

Accessibility Issues

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

Form elements do not have associated labels

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

r111n.com best practices score

67

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

r111n.com SEO score

58

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

Content Best Practices

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

Impact

Issue

High

Document uses plugins

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    AR

  • Encoding

    WINDOWS-1256

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise R111n.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Arabic. Our system also found out that R111n.com main page’s claimed encoding is windows-1256. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

r111n.com

Open Graph description is not detected on the main page of R 111 N. 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: