2 sec in total
143 ms
1.6 sec
272 ms
Click here to check amazing Logscope content. Otherwise, check out these important facts you probably never knew about logscope.net
Harvey Rock Physics is the home of LogScope petrophysical software. HRP also specialises in advanced borehole image inerpretation for Structure, Fractures, Geomechanics and high resolution petrophysic...
Visit logscope.netWe analyzed Logscope.net page load time and found that the first response time was 143 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
logscope.net performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value5.8 s
15/100
25%
Value20.3 s
0/100
10%
Value29,600 ms
0/100
30%
Value0.533
14/100
15%
Value40.9 s
0/100
10%
143 ms
71 ms
67 ms
166 ms
157 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Logscope.net, 38% (16 requests) were made to Static.wixstatic.com and 7% (3 requests) were made to Harveyrockphysics.com. The less responsive or slowest element that took the longest time to load (754 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 492.0 kB (59%)
834.0 kB
342.0 kB
In fact, the total size of Logscope.net main page is 834.0 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. HTML takes 604.1 kB which makes up the majority of the site volume.
Potential reduce by 472.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 472.9 kB or 78% of the original size.
Potential reduce by 19.1 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. Logscope images are well optimized though.
Potential reduce by 48 B
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.
Number of requests can be reduced by 10 (29%)
35
25
The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Logscope. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.harveyrockphysics.com
143 ms
minified.js
71 ms
focus-within-polyfill.js
67 ms
polyfill.min.js
166 ms
bootstrap-features.24d4529b.bundle.min.js
157 ms
main.24eb524d.bundle.min.js
154 ms
lodash.min.js
154 ms
react.production.min.js
287 ms
siteTags.bundle.min.js
151 ms
app.bundle.min.js
283 ms
wix-perf-measure.bundle.min.js
280 ms
react-dom.production.min.js
282 ms
c5022e_c015f99fa24fecb269a41e9bc4246c25.png
415 ms
thunderbolt
281 ms
c5022e_5f12b8fa67ff477babf19d32c9b9fd4d.jpg
454 ms
3b1f25_d88613295c5b40228989d68404f6dff7.png
401 ms
IMG_39D847AEF7F3-1.jpeg
496 ms
3b1f25_3f881a61f8d44bebad6a8610824eecc9.png
401 ms
IMG_826E90AA74D5-1_edited.png
461 ms
IMG_826E90AA74D5-1_edited.png
504 ms
c5022e_0589dfa578ed7f728258c3d809265755.png
468 ms
c5022e_53610a20728049edaf531beaf1d4a6aa~mv2.png
536 ms
c5022e_006ec6d16c43434b998db0f1c38f627c~mv2.png
606 ms
c5022e_5592edefeb6e4245aace4271a735f3fc~mv2.png
626 ms
c5022e_ac1dca0d381644d2aaeac1d89117d400~mv2.png
649 ms
c5022e_3cd7297809cc4abe93de274ea1b143a0~mv2.png
618 ms
c5022e_bf0291974b5b491fa5c9fbc1479cb973~mv2.png
735 ms
c5022e_5d2ea16871f848ce81cac555ef21ac4b~mv2.jpg
754 ms
c5022e_5d2ea16871f848ce81cac555ef21ac4b~mv2.jpg
680 ms
conductAllInScope
142 ms
conductExperiment
144 ms
c5749443-93da-4592-b794-42f28d62ef72.woff
11 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
13 ms
b56b944e-bbe0-4450-a241-de2125d3e682.woff
11 ms
6f8d1983-4d34-4fa4-9110-988f6c495757.woff
40 ms
e56ecb6d-da41-4bd9-982d-2d295bec9ab0.woff
41 ms
ProximaNovaW05-Regular.woff
39 ms
thunderbolt
36 ms
deprecation-en.v5.html
7 ms
bolt-performance
101 ms
deprecation-style.v5.css
20 ms
right-arrow.svg
16 ms
logscope.net 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
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
logscope.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
logscope.net 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Logscope.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 Logscope.net 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.
logscope.net
Open Graph data is detected on the main page of Logscope. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: