Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

phpico.com

PHPI MineralStar

Page Load Speed

2 sec in total

First Response

156 ms

Resources Loaded

1.6 sec

Page Rendered

169 ms

About Website

Welcome to phpico.com homepage info - get ready to check PHPI Co best content right away, or after learning these important things about phpico.com

Nutritional Products, plant derived products,

Visit phpico.com

Key Findings

We analyzed Phpico.com page load time and found that the first response time was 156 ms and then it took 1.8 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.

Performance Metrics

phpico.com performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

97/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.334

34/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

phpico.com

156 ms

shop.mineralstar.com

638 ms

jquery.min.js

31 ms

jquery-ui.min.js

60 ms

jquery-ui.css

52 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Phpico.com, 75% (47 requests) were made to Shop.mineralstar.com and 13% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (638 ms) relates to the external source Shop.mineralstar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 315.3 kB (50%)

Content Size

632.4 kB

After Optimization

317.1 kB

In fact, the total size of Phpico.com main page is 632.4 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. Images take 229.7 kB which makes up the majority of the site volume.

HTML Optimization

-40%

Potential reduce by 204 B

  • Original 507 B
  • After minification 461 B
  • After compression 303 B

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 204 B or 40% of the original size.

Image Optimization

-7%

Potential reduce by 16.4 kB

  • Original 229.7 kB
  • After minification 213.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. PHPI Co images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 120.5 kB

  • Original 195.0 kB
  • After minification 183.1 kB
  • After compression 74.5 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 120.5 kB or 62% of the original size.

CSS Optimization

-86%

Potential reduce by 178.3 kB

  • Original 207.2 kB
  • After minification 166.0 kB
  • After compression 28.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. Phpico.com needs all CSS files to be minified and compressed as it can save up to 178.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (54%)

Requests Now

54

After Optimization

25

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

Accessibility Review

phpico.com accessibility score

68

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

phpico.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Page has valid source maps

SEO Factors

phpico.com SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phpico.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Phpico.com 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.

Social Sharing Optimization

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