2.3 sec in total
33 ms
1.4 sec
821 ms
Click here to check amazing Phy content. Otherwise, check out these important facts you probably never knew about phy.so
Daily science news on research developments, technological breakthroughs and the latest scientific innovations
Visit phy.soWe analyzed Phy.so page load time and found that the first response time was 33 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
phy.so performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value5.0 s
26/100
25%
Value3.9 s
82/100
10%
Value1,240 ms
19/100
30%
Value0
100/100
15%
Value10.4 s
24/100
10%
33 ms
119 ms
54 ms
94 ms
102 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Phy.so, 35% (17 requests) were made to Phys.b-cdn.net and 27% (13 requests) were made to Scx1.b-cdn.net. The less responsive or slowest element that took the longest time to load (684 ms) relates to the external source Scx1.b-cdn.net.
Page size can be reduced by 313.2 kB (34%)
918.9 kB
605.7 kB
In fact, the total size of Phy.so main page is 918.9 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. 55% of websites need less resources to load. Javascripts take 490.4 kB which makes up the majority of the site volume.
Potential reduce by 184.3 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 57.5 kB, which is 28% 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 184.3 kB or 89% of the original size.
Potential reduce by 2.4 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. Phy images are well optimized though.
Potential reduce by 126.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 126.6 kB or 26% of the original size.
Potential reduce by 0 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. Phy.so has all CSS files already compressed.
Number of requests can be reduced by 9 (23%)
40
31
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
phy.so
33 ms
phys.org
119 ms
libs.424020881.css
54 ms
style.3767063502.css
94 ms
js
102 ms
adsbygoogle.js
155 ms
svgxuse.3767063502.js
87 ms
libs.2038530676.js
147 ms
common.424020881.js
95 ms
css
115 ms
css
126 ms
logo-header.png
125 ms
a-diamond-quantum-memo.jpg
598 ms
comsol-202-70x70.png
236 ms
acs-003.jpg
302 ms
icon_mail.png
143 ms
icon_password.png
220 ms
checked.svg
211 ms
MedicalXpress2.svg
217 ms
techX_w.svg
219 ms
sprite.svg
211 ms
techexploer.svg
292 ms
MedicalXpress.svg
288 ms
ScienceX.svg
287 ms
nasas-final-tally-show.jpg
565 ms
harnessing-light-with.jpg
322 ms
hearing-the-sound-of-q.jpg
367 ms
new-species-of-pirate-2.jpg
564 ms
astronaut-training.jpg
565 ms
5000-atoms-are-all-you.jpg
564 ms
aurora-borealis-dynami-1.jpg
563 ms
bacteria-in-the-arctic.jpg
684 ms
live-fast-die-young-ag.jpg
684 ms
stabilizing-mrna-vacci.jpg
683 ms
measuring-neutrons-to.jpg
683 ms
a-geothermal-powered-c.jpg
683 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
291 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
500 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
613 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
612 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
612 ms
zrt_lookup.html
544 ms
show_ads_impl.js
174 ms
quant.js
405 ms
sprite.svg
0 ms
sprite.svg
22 ms
ads
530 ms
ads
149 ms
phy.so accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
phy.so best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Page has valid source maps
phy.so SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phy.so 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 Phy.so 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.
phy.so
Open Graph data is detected on the main page of Phy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: