Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

prefixbox.com

AI Search & Discovery | Prefixbox

Page Load Speed

7 sec in total

First Response

99 ms

Resources Loaded

6.4 sec

Page Rendered

541 ms

About Website

Click here to check amazing Prefixbox content for Pakistan. Otherwise, check out these important facts you probably never knew about prefixbox.com

Optimize your online Enterprise store with Prefixbox’s fully managed AI Search, Recommend, and Insights solutions.

Visit prefixbox.com

Key Findings

We analyzed Prefixbox.com page load time and found that the first response time was 99 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

prefixbox.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value2,460 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.294

41/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

Network Requests Diagram

99 ms

api.js

83 ms

webforms.min.js

146 ms

bootstrap.min.css

82 ms

site.css

181 ms

Our browser made a total of 151 requests to load all elements on the main page. We found that 15% of them (23 requests) were addressed to the original Prefixbox.com, 48% (72 requests) were made to Site-content.prefixbox.com and 4% (6 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Site-content.prefixbox.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 425.8 kB (39%)

Content Size

1.1 MB

After Optimization

676.4 kB

In fact, the total size of Prefixbox.com main page is 1.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 746.3 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 157.1 kB

  • Original 173.9 kB
  • After minification 106.8 kB
  • After compression 16.8 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 67.1 kB, which is 39% 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 157.1 kB or 90% of the original size.

Image Optimization

-3%

Potential reduce by 1.4 kB

  • Original 41.9 kB
  • After minification 40.5 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. Prefixbox images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 258.6 kB

  • Original 746.3 kB
  • After minification 746.3 kB
  • After compression 487.7 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 258.6 kB or 35% of the original size.

CSS Optimization

-6%

Potential reduce by 8.7 kB

  • Original 140.1 kB
  • After minification 140.1 kB
  • After compression 131.4 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. Prefixbox.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 70 (49%)

Requests Now

144

After Optimization

74

The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prefixbox. 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 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

prefixbox.com accessibility score

84

Accessibility Issues

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

High

ARIA IDs are not unique

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

prefixbox.com best practices score

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

prefixbox.com SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prefixbox.com 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 Prefixbox.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 data is detected on the main page of Prefixbox. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: