Tools & Wizards About Us
phoronix.net screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

phoronix.net

Linux Hardware Reviews & Performance Benchmarks, Open-Source News - Phoronix

Page Load Speed

6 sec in total

First Response

828 ms

Resources Loaded

4.9 sec

Page Rendered

281 ms

phoronix.net screenshot

About Website

Click here to check amazing Phoronix content. Otherwise, check out these important facts you probably never knew about phoronix.net

Phoronix is the leading technology website for Linux hardware reviews, open-source news, Linux benchmarks, open-source benchmarks, and computer hardware performance tests.

Visit phoronix.net

Key Findings

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

Performance Metrics

phoronix.net performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value5,770 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

Network Requests Diagram

phoronix.net

828 ms

489 ms

674 ms

css.php

330 ms

css.php

772 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Phoronix.net, 20% (16 requests) were made to Phoronix.com and 5% (4 requests) were made to Stat.komoona.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Phoronix.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (69%)

Content Size

1.6 MB

After Optimization

480.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phoronix.net main page is 1.6 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. 45% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 107.0 kB

  • Original 124.0 kB
  • After minification 100.6 kB
  • After compression 16.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. This page needs HTML code to be minified as it can gain 23.4 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 107.0 kB or 86% of the original size.

Image Optimization

-9%

Potential reduce by 1.8 kB

  • Original 19.4 kB
  • After minification 17.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. Phoronix images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 686.1 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 385.9 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 686.1 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 299.3 kB

  • Original 359.3 kB
  • After minification 355.1 kB
  • After compression 60.0 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. Phoronix.net needs all CSS files to be minified and compressed as it can save up to 299.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (78%)

Requests Now

73

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phoronix.net

phoronix.net

828 ms

489 ms

674 ms

css.php

css.php

330 ms

css.php

css.php

772 ms

header-rollup-520.js

header-rollup-520.js

572 ms

css.php

css.php

687 ms

css.php

css.php

704 ms

css.php

css.php

942 ms

css.php

css.php

1171 ms

getads.js

getads.js

66 ms

gpt.js

gpt.js

21 ms

kmn_sa.js

kmn_sa.js

73 ms

jquery.min.js

jquery.min.js

45 ms

footer-rollup-520.js

footer-rollup-520.js

1189 ms

css

css

25 ms

login-form

login-form

166 ms

phoronix.png

phoronix.png

32 ms

default_avatar_thumb.png

default_avatar_thumb.png

137 ms

default_avatar_medium.png

default_avatar_medium.png

136 ms

getad

getad

43 ms

s

s

89 ms

kmn_sa.js

kmn_sa.js

27 ms

analytics.js

analytics.js

84 ms

pubads_impl_82.js

pubads_impl_82.js

36 ms

6a9a69b201e5365128278788f70fe7c5.js

6a9a69b201e5365128278788f70fe7c5.js

63 ms

6a9a69b201e5365128278788f70fe7c5.js

6a9a69b201e5365128278788f70fe7c5.js

69 ms

ads

ads

417 ms

container.html

container.html

29 ms

collect

collect

16 ms

kmn-cs.js

kmn-cs.js

14 ms

css.php

css.php

108 ms

login_md5.js

login_md5.js

93 ms

s

s

4 ms

jstag

jstag

217 ms

acj

acj

982 ms

expansion_embed.js

expansion_embed.js

27 ms

sprite_icons_flat.svg

sprite_icons_flat.svg

97 ms

getad

getad

37 ms

gpt.js

gpt.js

23 ms

ads

ads

63 ms

beacon.js

beacon.js

14 ms

1647406538664748539

1647406538664748539

717 ms

moatad.js

moatad.js

720 ms

p-pCm77VqnYPT42.gif

p-pCm77VqnYPT42.gif

720 ms

osd.js

osd.js

670 ms

s

s

697 ms

05bb75cfc6f2e1cd06684f99cbaa7582.js

05bb75cfc6f2e1cd06684f99cbaa7582.js

695 ms

05bb75cfc6f2e1cd06684f99cbaa7582.js

05bb75cfc6f2e1cd06684f99cbaa7582.js

661 ms

s

s

37 ms

showad.js

showad.js

81 ms

pd

pd

150 ms

getjs.aspx

getjs.aspx

57 ms

ri

ri

76 ms

pixel.gif

pixel.gif

25 ms

quant.js

quant.js

14 ms

showad.js

showad.js

18 ms

getjs.static.js

getjs.static.js

16 ms

pixel.gif

pixel.gif

12 ms

PugMaster

PugMaster

24 ms

pixel.gif

pixel.gif

4 ms

GetAd.aspx

GetAd.aspx

79 ms

pixel;r=675676670;a=p-25K88fxDSEn9Y;fpan=1;fpa=P0-1638735302-1458286004028;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458286004028;tzo=-180;ref=http%3A%2F%2Fwww.phoronix.com%2Fforums%2F;url=about%3Ablank;ogl=

pixel;r=675676670;a=p-25K88fxDSEn9Y;fpan=1;fpa=P0-1638735302-1458286004028;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458286004028;tzo=-180;ref=http%3A%2F%2Fwww.phoronix.com%2Fforums%2F;url=about%3Ablank;ogl=

13 ms

3BCFE41D-8102-4C02-9343-C9F98A54993B

3BCFE41D-8102-4C02-9343-C9F98A54993B

45 ms

pm_match

pm_match

9 ms

pixel

pixel

18 ms

Pug

Pug

18 ms

p-P7x87XHnVfbWr.gif

p-P7x87XHnVfbWr.gif

5 ms

demconf.jpg

demconf.jpg

5 ms

420486.gif

420486.gif

5 ms

Pug

Pug

16 ms

Pug

Pug

20 ms

e582dbcd-797e-a9b1-3156-6f355aa8c56d

e582dbcd-797e-a9b1-3156-6f355aa8c56d

22 ms

pixel

pixel

17 ms

400066.gif

400066.gif

13 ms

sd

sd

7 ms

sd

sd

7 ms

sd

sd

84 ms

sd

sd

5 ms

Accessibility Review

phoronix.net accessibility score

90

Accessibility Issues

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.

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

Best Practices

phoronix.net 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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

phoronix.net SEO score

99

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

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

phoronix.net

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