## Making initial queries early with GraphQL startup calls
To improve performance, sometimes we want to make initial GraphQL queries early. In order to do this, we can add them to **startup calls** with the following steps:
- Move all the queries you need initially in your application to `app/graphql/queries`;
- Add `__typename` property to every nested query level:
```javascript
querygetPermissions($projectPath:ID!){
project(fullPath:$projectPath){
__typename
userPermissions{
__typename
pushCode
forkProject
createMergeRequestIn
}
}
}
```
- If queries contain fragments, you need to move fragments to the query file directly instead of importing them:
```javascript
fragmentPageInfoonPageInfo{
__typename
hasNextPage
hasPreviousPage
startCursor
endCursor
}
querygetFiles(
$projectPath:ID!
$path:String
$ref:String!
){
project(fullPath:$projectPath){
__typename
repository{
__typename
tree(path:$path,ref:$ref){
__typename
pageInfo{
...PageInfo
}
}
}
}
}
}
```
- If the fragment is used only once, we can also remove the fragment altogether:
```javascript
querygetFiles(
$projectPath:ID!
$path:String
$ref:String!
){
project(fullPath:$projectPath){
__typename
repository{
__typename
tree(path:$path,ref:$ref){
__typename
pageInfo{
__typename
hasNextPage
hasPreviousPage
startCursor
endCursor
}
}
}
}
}
}
```
- Add startup call(s) with correct variables to the HAML file that serves as a view
for your application. To add GraphQL startup calls, we use
`add_page_startup_graphql_call` helper where the first parameter is a path to the
query, the second one is an object containing query variables. Path to the query is
relative to `app/graphql/queries` folder: for example, if we need a
`app/graphql/queries/repository/files.query.graphql` query, the path will be
