Tools & Wizards About Us
petrofac.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

petrofac.com

Petrofac

Page Load Speed

3.6 sec in total

First Response

757 ms

Resources Loaded

2.6 sec

Page Rendered

168 ms

petrofac.com screenshot

About Website

Click here to check amazing Petrofac content for India. Otherwise, check out these important facts you probably never knew about petrofac.com

A leading international service provider to the energy industry

Visit petrofac.com

Key Findings

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

Performance Metrics

petrofac.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value1,370 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

petrofac.com

757 ms

normalize.css

167 ms

foundation-3.css

281 ms

foundation-3-overrides.css

186 ms

foundation-overrides_mega_menu.css

194 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 89% of them (50 requests) were addressed to the original Petrofac.com, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (905 ms) belongs to the original domain Petrofac.com.

Page Optimization Overview & Recommendations

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

Content Size

1.7 MB

After Optimization

866.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Petrofac.com main page is 1.7 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. 40% of websites need less resources to load. Images take 727.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 49.0 kB

  • Original 59.4 kB
  • After minification 56.3 kB
  • After compression 10.4 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 49.0 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 27.2 kB

  • Original 727.6 kB
  • After minification 700.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. Petrofac images are well optimized though.

JavaScript Optimization

-83%

Potential reduce by 597.0 kB

  • Original 723.4 kB
  • After minification 443.8 kB
  • After compression 126.4 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 597.0 kB or 83% of the original size.

CSS Optimization

-86%

Potential reduce by 177.6 kB

  • Original 206.7 kB
  • After minification 157.4 kB
  • After compression 29.1 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. Petrofac.com needs all CSS files to be minified and compressed as it can save up to 177.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (55%)

Requests Now

49

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

petrofac.com

petrofac.com

757 ms

normalize.css

normalize.css

167 ms

foundation-3.css

foundation-3.css

281 ms

foundation-3-overrides.css

foundation-3-overrides.css

186 ms

foundation-overrides_mega_menu.css

foundation-overrides_mega_menu.css

194 ms

app.css

app.css

178 ms

flexslider.css

flexslider.css

194 ms

style.css

style.css

261 ms

prettyPhoto.css

prettyPhoto.css

273 ms

css

css

26 ms

modernizr.foundation.js

modernizr.foundation.js

553 ms

iframeResizer.min.js

iframeResizer.min.js

289 ms

jquery.min.js

jquery.min.js

33 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

288 ms

jquery.flexslider.js

jquery.flexslider.js

352 ms

easy.notification.js

easy.notification.js

353 ms

moment-with-langs.js

moment-with-langs.js

724 ms

momentmin.js

momentmin.js

461 ms

moment-timezone.js

moment-timezone.js

371 ms

moment-timezone-data.js

moment-timezone-data.js

643 ms

foundation.js

foundation.js

439 ms

jquery.foundation.topbar.js

jquery.foundation.topbar.js

455 ms

jquery.foundation.orbit.js

jquery.foundation.orbit.js

537 ms

jquery.foundation.forms.js

jquery.foundation.forms.js

545 ms

ga.js

ga.js

71 ms

sitelogo.gif

sitelogo.gif

191 ms

btn_search_f1.gif

btn_search_f1.gif

188 ms

homepage6.jpg

homepage6.jpg

252 ms

home-slider-pic-3.jpg

home-slider-pic-3.jpg

95 ms

home-slider-pic-1.jpg

home-slider-pic-1.jpg

575 ms

home-slider-pic-2.jpg

home-slider-pic-2.jpg

592 ms

arw_gold.gif

arw_gold.gif

189 ms

final-results-480x234.jpg

final-results-480x234.jpg

484 ms

right-chevron.gif

right-chevron.gif

261 ms

isg-480x234.jpg

isg-480x234.jpg

359 ms

british-ambassador-visit-to-oman-480x234.jpg

british-ambassador-visit-to-oman-480x234.jpg

423 ms

mexico_project_2_480x234-optimised.jpg

mexico_project_2_480x234-optimised.jpg

432 ms

rightbutton.jpg

rightbutton.jpg

461 ms

ico_twitter_f1.gif

ico_twitter_f1.gif

510 ms

ico_facebook_f1.gif

ico_facebook_f1.gif

525 ms

ico_linked_f1.gif

ico_linked_f1.gif

553 ms

ico_google_f1.gif

ico_google_f1.gif

569 ms

prev-arrow.gif

prev-arrow.gif

573 ms

next-arrow.gif

next-arrow.gif

574 ms

BkZwJXYnumPMepfEA344yQ.ttf

BkZwJXYnumPMepfEA344yQ.ttf

32 ms

eFfAHNfFT0YtF77QmRKRj_esZW2xOQ-xsNqO47m55DA.ttf

eFfAHNfFT0YtF77QmRKRj_esZW2xOQ-xsNqO47m55DA.ttf

47 ms

__utm.gif

__utm.gif

16 ms

arw_white_form.gif

arw_white_form.gif

567 ms

btn_share.gif

btn_share.gif

587 ms

btn_email.gif

btn_email.gif

580 ms

btn_rss.gif

btn_rss.gif

602 ms

ico_select.gif

ico_select.gif

517 ms

rotator-black.png

rotator-black.png

905 ms

pause-black.png

pause-black.png

538 ms

right-arrow.png

right-arrow.png

564 ms

left-arrow.png

left-arrow.png

571 ms

Accessibility Review

petrofac.com accessibility score

92

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

petrofac.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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

petrofac.com SEO score

84

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

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Petrofac.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Petrofac.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

petrofac.com

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