Tools & Wizards About Us
1re.info screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

1re.info

Welcome to nginx!

Page Load Speed

3.6 sec in total

First Response

1.4 sec

Resources Loaded

1.9 sec

Page Rendered

247 ms

1re.info screenshot

About Website

Welcome to 1re.info homepage info - get ready to check 1 Re best content right away, or after learning these important things about 1re.info

Pec stands for Punjab Examination Commission will announce the 5th 8th Class Result 2014 in the end of March

Visit 1re.info

Key Findings

We analyzed 1re.info page load time and found that the first response time was 1.4 sec and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

1re.info performance score

0

Network Requests Diagram

1re.info

1441 ms

layout.css

178 ms

custom.css

157 ms

plusone.js

35 ms

gdsr.css.php

284 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 27% of them (14 requests) were addressed to the original 1re.info, 19% (10 requests) were made to Static.xx.fbcdn.net and 15% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain 1re.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 164.4 kB (51%)

Content Size

320.8 kB

After Optimization

156.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 1re.info main page is 320.8 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. 50% of websites need less resources to load. Javascripts take 132.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 18.0 kB

  • Original 23.9 kB
  • After minification 23.4 kB
  • After compression 5.9 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 18.0 kB or 75% of the original size.

Image Optimization

-6%

Potential reduce by 4.7 kB

  • Original 76.3 kB
  • After minification 71.6 kB

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. 1 Re images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 64.4 kB

  • Original 132.2 kB
  • After minification 132.1 kB
  • After compression 67.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 64.4 kB or 49% of the original size.

CSS Optimization

-87%

Potential reduce by 77.3 kB

  • Original 88.5 kB
  • After minification 73.0 kB
  • After compression 11.1 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. 1re.info needs all CSS files to be minified and compressed as it can save up to 77.3 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (45%)

Requests Now

49

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1re.info

1re.info

1441 ms

layout.css

layout.css

178 ms

custom.css

custom.css

157 ms

plusone.js

plusone.js

35 ms

gdsr.css.php

gdsr.css.php

284 ms

rating.css

rating.css

165 ms

jquery.js

jquery.js

312 ms

jquery-migrate.min.js

jquery-migrate.min.js

258 ms

gdsr.js

gdsr.js

310 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

26 ms

transparent.png

transparent.png

633 ms

1RE1.png

1RE1.png

165 ms

thumb.php

thumb.php

241 ms

transparent.png

transparent.png

554 ms

thumb.php

thumb.php

363 ms

thumb.php

thumb.php

263 ms

thumb.php

thumb.php

354 ms

show_ads.js

show_ads.js

7 ms

ca-pub-2975311184338992.js

ca-pub-2975311184338992.js

32 ms

zrt_lookup.html

zrt_lookup.html

49 ms

show_ads_impl.js

show_ads_impl.js

51 ms

bg-ipage-ft.png

bg-ipage-ft.png

139 ms

ga.js

ga.js

13 ms

__utm.gif

__utm.gif

53 ms

1.png

1.png

135 ms

ads

ads

296 ms

likebox.php

likebox.php

124 ms

osd.js

osd.js

10 ms

kyEKgjk51ZE.css

kyEKgjk51ZE.css

19 ms

xgj7bXhJNEH.css

xgj7bXhJNEH.css

22 ms

1kPfZUdGrka.js

1kPfZUdGrka.js

34 ms

Yuj_Y8xNH2C.js

Yuj_Y8xNH2C.js

53 ms

Mpe38fuBVZ2.js

Mpe38fuBVZ2.js

33 ms

n8qIhCw3vMx.js

n8qIhCw3vMx.js

32 ms

389627_380479575337158_1847453700_n.jpg

389627_380479575337158_1847453700_n.jpg

43 ms

1929951_888424151279157_3799070815772834691_n.jpg

1929951_888424151279157_3799070815772834691_n.jpg

20 ms

12742248_857510041037783_9205007472826546306_n.jpg

12742248_857510041037783_9205007472826546306_n.jpg

55 ms

251211_101173566643484_5937417_n.jpg

251211_101173566643484_5937417_n.jpg

100 ms

65569_298120743716730_6600184323679725010_n.jpg

65569_298120743716730_6600184323679725010_n.jpg

57 ms

10354686_10150004552801856_220367501106153455_n.jpg

10354686_10150004552801856_220367501106153455_n.jpg

21 ms

10406360_1483385625268797_2265373496198711552_n.jpg

10406360_1483385625268797_2265373496198711552_n.jpg

24 ms

11220093_1705438169690167_6790814045406566142_n.jpg

11220093_1705438169690167_6790814045406566142_n.jpg

50 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

17 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

16 ms

2205679411648869510

2205679411648869510

50 ms

abg.js

abg.js

54 ms

m_js_controller.js

m_js_controller.js

64 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

33 ms

VXcANLwwL5J.js

VXcANLwwL5J.js

5 ms

AmlxWlqMvlv.js

AmlxWlqMvlv.js

8 ms

x_button_blue2.png

x_button_blue2.png

33 ms

s

s

28 ms

SEO Factors

1re.info SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1re.info 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 English. Our system also found out that 1re.info 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

1re.info

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