1.4 sec in total
28 ms
683 ms
663 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 28 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
phy.so performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value4.0 s
48/100
25%
Value4.9 s
65/100
10%
Value3,790 ms
1/100
30%
Value0
100/100
15%
Value16.0 s
6/100
10%
28 ms
87 ms
68 ms
106 ms
81 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Phy.so, 39% (17 requests) were made to Phys.b-cdn.net and 30% (13 requests) were made to Scx1.b-cdn.net. The less responsive or slowest element that took the longest time to load (242 ms) relates to the external source Scx1.b-cdn.net.
Page size can be reduced by 219.6 kB (26%)
845.2 kB
625.5 kB
In fact, the total size of Phy.so main page is 845.2 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. Javascripts take 385.3 kB which makes up the majority of the site volume.
Potential reduce by 205.5 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.4 kB, which is 24% 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 205.5 kB or 85% of the original size.
Potential reduce by 81 B
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 14.1 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.
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 (24%)
37
28
The browser has sent 37 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
28 ms
phys.org
87 ms
libs.3275013628.css
68 ms
style.989488547.css
106 ms
js
81 ms
adsbygoogle.js
73 ms
svgxuse.989488547.js
106 ms
libs.989488547.js
72 ms
common.3275013628.js
49 ms
css
38 ms
css
51 ms
logo-header.png
178 ms
millions-in-the-us-may-2.jpg
242 ms
acs-003.jpg
168 ms
quant.js
139 ms
icon_mail.png
114 ms
icon_password.png
113 ms
checked.svg
112 ms
MedicalXpress2.svg
228 ms
techX_w.svg
171 ms
sprite.svg
128 ms
techexploer.svg
230 ms
MedicalXpress.svg
226 ms
ScienceX.svg
136 ms
no-significant-pfas-em.jpg
121 ms
ion-pairing-a-new-appr.jpg
230 ms
news.jpg
118 ms
researchers-establish-6.jpg
126 ms
researchers-leverage-c.jpg
118 ms
human-actions-cause-in.jpg
123 ms
harnessing-plant-odors-1.jpg
123 ms
crustacean-with-panda.jpg
126 ms
pythons-can-eat-bigger.jpg
229 ms
utep-researchers-devel.jpg
229 ms
mouse-model-reveals-li.jpg
131 ms
study-increases-unders.jpg
130 ms
show_ads_impl.js
239 ms
sprite.svg
60 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
33 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
66 ms
KFOmCnqEu92Fr1Mu4mxM.woff
120 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
175 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
175 ms
sprite.svg
125 ms
phy.so accessibility score
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
Form elements do not have associated labels
Links do not have a discernible name
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
robots.txt is not valid
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: