Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

rotter.net

????? | ????? ????.??

Page Load Speed

5.2 sec in total

First Response

671 ms

Resources Loaded

3.8 sec

Page Rendered

634 ms

rotter.net screenshot

About Website

Welcome to rotter.net homepage info - get ready to check Rotter best content for Israel right away, or after learning these important things about rotter.net

??? ?????? ????.?? ???? ????? ??? ?? ??????, ?????, ????? ????? ??????? ?????? ???? ??? ?? ?? ????? ???? ??????

Visit rotter.net

Key Findings

We analyzed Rotter.net page load time and found that the first response time was 671 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

rotter.net performance score

0

Network Requests Diagram

rotter.net

671 ms

style.css

312 ms

wind.js

310 ms

money.css

315 ms

HebDate.js

351 ms

Our browser made a total of 236 requests to load all elements on the main page. We found that 14% of them (32 requests) were addressed to the original Rotter.net, 9% (22 requests) were made to Sport1.maariv.co.il and 8% (18 requests) were made to Rotter.co.il. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Sponser.co.il.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (31%)

Content Size

4.9 MB

After Optimization

3.4 MB

In fact, the total size of Rotter.net main page is 4.9 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 323.6 kB

  • Original 442.5 kB
  • After minification 431.4 kB
  • After compression 118.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 323.6 kB or 73% of the original size.

Image Optimization

-5%

Potential reduce by 127.9 kB

  • Original 2.8 MB
  • After minification 2.6 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. Rotter images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 747.7 kB

  • Original 1.3 MB
  • After minification 1.2 MB
  • After compression 515.3 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 747.7 kB or 59% of the original size.

CSS Optimization

-74%

Potential reduce by 289.0 kB

  • Original 392.9 kB
  • After minification 363.9 kB
  • After compression 103.9 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. Rotter.net needs all CSS files to be minified and compressed as it can save up to 289.0 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 105 (48%)

Requests Now

219

After Optimization

114

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

SEO Factors

rotter.net SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    HE

  • Encoding

    WINDOWS-1255

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

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